Many Versions In One .NET SLN
My .net code base is now being asked to ship two different products and thus two different versions from the same sln. I would like to have two different AssemblyResource.cs files. One linked to half the projects in the sln and another linked to the other half and use the 'assembly_info' appveyor tag to patch the two files. The versions should share the same build number but have different major, minor, patch numbers. Is this possible or should I seek a different path?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Ilya Finkelshte... on 21 Jul, 2018 01:30 AM
AssemblyInfo patching happens only once during build job. That's why I would recommend to implement build matrix to split build to 2 separate jobs. You can create 2 configurations in VS, and tune them so each configuration builds only specific part of the projects. Set those 2 configurations in YAML or on
Buildtab (if you use UI).Then then you can specialize settings for AssemblyInfo patching for different matrix jobs.
Build will contain 2 jobs, but it should not take significantly more time as each job will build only part of projects. And if you have spare concurrent job, it will be actually faster.
Another advantage of this is clear separation of artifacts, especially indeed they are different products.
Let us know if this works for you.
Ilya Finkelshteyn closed this discussion on 27 Aug, 2018 08:33 PM.