To generate release notes, users have to pass in “Stating ChangeSet” and “Ending ChangeSet” as a rangeto TFS ChangeLog application . We use “TFSChangeLogConfig.xml” configuration file as a parameter to “TFSChangeLogCL.exe” application. Above configuration
file contains “Stating ChangeSet” and “Ending ChangeSet” details that are used for generating release notes.
Now if it’s okay for you to update “Stating ChangeSet” and “Ending ChangeSet” information manually then InvokeProcess from a Build workflow shall work without any problems. But if you would like it to be dynamic and you should be able to pass in this information
via InvokeProcess parameter then it’s an issue.
Please note that by setting “Ending ChangeSet” to Zero, TFS ChangeLog shall automatically pick-up latest changeset as “Ending ChangeSet” for defining changeset range.
It will be nice if you can share your experience of using TFS ChangeLog Command Line version via InvokeProcess build activity. Also, if you want to see any other changes to this application then please file new Issue that we can then prioritize for future development
at http://tfschangelog.codeplex.com site.
I hope this answers your question.