Open
Conversation
…ps build time constant until Visual Studio Solution is reloaded)
…sep>:<ref>} added
…itory contains modified (dirty)
…nsensitive Regex match for <ref>
…o avoid error message "Revision ID cannot be truncated to dotted-numeric"
…ecuting NetRevisionTask targets
Owner
|
This PR has two merge conflicts, distributed over multiple places:
I'm sorry to have caused these conflicts. I first needed to fix another issue. And before publishing it as a new version, I figured I could try to address these PRs now, too. |
Contributor
Author
|
The merge conflicts have been resolved, however patch-03 branch needed to be merged because Interactive API needs functionality implemented there. Regarding |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello Yves,
I have added an Interactive API as extension to the already present static methods, so I can use NetRevisionTask.dll be called and queried by other assemlies, e.g. to integrate it with an external build flow for embedded devices.
Please let me know what you think.
Best regards,
Mark