-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] /updateassemblyinfo filename does not work anymore #2270
Comments
well the path of the assemblyInfo you want to update should be relative to the root folder that contains the you can use the Glob pattern (also relative to the directory the tool runs) |
Sorry, the $(SolutionDir) is a Visual studio variable which is replaced at build time with the complete solution path. |
Fixed by e92db5e |
🎉 This issue has been resolved in version 5.3.3 🎉 Your GitReleaseManager bot 📦🚀 |
@arturcic I'm still facing this issue. I'm doing /updateassemblyinfo CommonAssemblyInfo.cs. However, this seems to be updating all the AssemblyInfo.cs files in my repository which is not what I want. I need to update only CommonAssemblyInfo.cs in one of the projects from the entire repository. How do I provide the path to that? When I did /updateassemblyinfo /projectname/CommonAssemblyInfo.cs, it gave me this error: "Unhandled exception. GitVersion.WarningException: Could not parse command line parameter '/projectname/CommonAssemblyInfo.cs'" |
^nvm, I was able to solve it by doing /updateassemblyinfo \projectname\CommonAssemblyInfo.cs Turns out it was updating all the AssemblyInfo.cs files if it couldn't find the file you specified or something wrong with the path. |
In a MSVS 2019 project I've configured a prebuild step execution with this command
gitversion /updateassemblyinfo $(SolutionDir)GlobalAssemblyInfo.cs /ensureassemblyinfo
This worked well with previous versions of GitVersion and the GlobalAssemblyInfo.cs file was generated with the info expected
With version 5.3.2, the GlobalAssemblyInfo.cs file specified in the command line is not created and the AssemblyInfo.cs files in the solution are updated.
Is this the expected behavior?
The text was updated successfully, but these errors were encountered: