There seem to be three distinct questions here:
1 – External trigger to generate a document
2 – Make eaDocX TFS aware
3 – pull-in different versions of a package to put in a document.
Suggestions
1 – There’s currently no support in eaDocX to have the Generator triggered by an external program. This would be harder than you might think, as, if you are using eaDocX Document Management, the UI will prompt for information about any new version, so that would have to be passed as parameters. But other than that, this might be possible. What would be the trigger ?
2 – TFS-aware. We’ve been asked about this a couple of times before, but we’ve always lacked any in-house TFS knowledge. And access to a TFS installation. But if you’re prepared to help us with these, all things are possible!
3 – Multiple versions. This might be the killer. eaDocX works only on the current contents of a single EA Repository. So, we’d have to load v1.0 into the package, generate that section, stop, reload the next version of the same package, then generate the next section.
This sounds hard! So we’d have to be convinced that there is demand for this facility.
.
