Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Commit AssemblyVersion changes in AssemblyInfo.cs to source control
-
Buildmaster contains a .Net action to Write Assembly Versions (Updates AssemblyVersion, AssemblyFileVersion, and AssemblyInformationalVersion Attributes (in Assembly Info source files). These actions are made on the build server but are not saved back to the source control system.
Is there anyway to save the modified AssemblyInfo.cs back to source control system? This would need to be done without the check-in leading to an infinite loop of BuildMaster. For example the check-in triggers a new build which leads to an update in the AsemblyInfo.cs, which on save to source control triggers a new build, etc etc.
Product: BuildMaster
Version: 4.6.4 -
It's not recommended to check-in the modified assemblyinfo.cs file. For a few reasons, including the one you identified: it causes issues with source control related to the build. But moreover, attributes in AssemblyInfo.cs are metadata more than code; in other platforms (like Java) these are always added as part of the build process.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login