I indicated very clearly that my last post was a hack. I want to take a bit of time to explain exactly why it was a hack. I’ll also point out things that were not a hack.
Assuming I could properly emulate Job Processor
In theory, the hosting app and the plug-in are decoupled. But the reality is that they often are not. Unless an API provides specific support for this decoupling, you should assume a tight coupling. The Vault API makes no claims that you can load and run Job Handlers outside the context of Job Processor.
Using JobProcessor.exe.config to figure out the DLL and class for DWF creation
Verdict: Not a hack
If you’ve implemented a custom Job handler, you know that you have to edit JobProcessor.exe.config and add your own <jobHandler>. So the <jobHandler> syntax is spelled out right in the API documentation.
Figuring out the parameters on Autodesk.Vault.DWF.Create.ipt
Just because one job showed a single parameter, FileVersionId, doesn’t mean that all jobs of that type have the same single parameter. There may be optional parameters not shown. There may also be cases where certain files require additional parameters. Again, there is no way of knowing what those cases are. Without any official documentation, the best one can do is guess.