-
Notifications
You must be signed in to change notification settings - Fork 652
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
GitVersionInformation in SDK-style projects #1242
Comments
Looking over those issues and some of the TODOs in the code, here's what I'm thinking of as a plan of attack for this:
With that in place, it should be easier to also fix some of the other issues you linked to as well. How does that sound? |
@bording: Fantastic! Whole-heartedly supported! 😄 👍 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 4.0,
UpdateAssemblyInfo
is false for the new SDK-style projects, which makes sense since the appropriate values can be injected viaUpdateVersionProperties
.However, this means that the static
GitVersionInformation
class is also no longer generated by default, which means SDK-style projects lose the ability to inspect version properties at run-time.Setting
UpdateAssemblyInfo
to true works, but it's a pain because you then end up with assembly attribute conflicts, which means you have to add something like this to your project file also:I'd like to see the generation of
GitVersionInformation
be controlled separately and be enabled by default even for SDK-style projects.Is this something that sounds reasonable? I'd be willing to work on this if it sounds like something you'd accept.
The text was updated successfully, but these errors were encountered: