Hi,
We are using a Azure DevOps build pipeline to build the control and generate the solution file. The ControlManifest.Input.xml has a version attribute for the control. Is there a way to auto update this?
I would like to do the following:
<control namespace="MyComponent" constructor="MyComponent" version="1.0.$(BuildID)" display-name-key="Mycomponent" description-key="My Fancy Component" control-type="standard">
And have $(BuildID) to re placed with the current buildid.
Any thoughts on this?
Solved! Go to Solution.
Hi Pieter,
One way to do this is via an msbuild target in your .cdfproj file with an XmlPoke msbuild task: https://docs.microsoft.com/en-us/visualstudio/msbuild/xmlpoke-task?view=vs-2019 and pass in $(BuildId) when you build the solution as part of the pipeline
There’s also a builtin VSTS task “File Transform” https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/file-transform?view=azure-devo...
Happy to setup a call to talk/walk through this with you if you'd like?
Hi Pieter,
One way to do this is via an msbuild target in your .cdfproj file with an XmlPoke msbuild task: https://docs.microsoft.com/en-us/visualstudio/msbuild/xmlpoke-task?view=vs-2019 and pass in $(BuildId) when you build the solution as part of the pipeline
There’s also a builtin VSTS task “File Transform” https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/file-transform?view=azure-devo...
Happy to setup a call to talk/walk through this with you if you'd like?
We made it work with XML Poke. Didn't see an easy way to do it with the file transform.
thanks @HansG Hans for testing the solution provided by @Mikkelsen2000 . It works nicely.
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
User | Count |
---|---|
4 | |
4 | |
3 | |
2 | |
2 |