-
Notifications
You must be signed in to change notification settings - Fork 4k
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
EnC: Add asterisk based assembly version docs #73364
Conversation
@AArnott please review if Nerdbank.GitVersioning info is accurate. |
@davidwengier PTAL |
It is thus highly recommended to use alternative versioning methods, such as [Nerdbank.GitVersioning](https://github.com/dotnet/Nerdbank.GitVersioning), that derive the assembly version | ||
from the HEAD commit SHA (for git repositories). | ||
|
||
> To enable generating commit SHA based assembly versions using `Nerdbank.GitVersioning` package, specify `{ "assemblyVersion" : {"precision": "revision"} }` setting in `version.json`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is accurate, although I wonder if it's common for users to use wildcards with AssemblyVersion
as opposed to AssemblyFileVersion
. Having AssemblyVersion
change with every single has at least historically been problematic (for strong named assemblies) so I would expect wildcards to be used for the file version instead. And in that case, this JSON isn't necessary, because AssemblyFileVersion
by default includes a commit SHA component.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have seen customers using wildcard in assembly version, which is causing Hot Reload issues.
Document workaround for projects containing
*
in assembly version.