You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 8, 2024. It is now read-only.
Hi is there any reason to fix AssemblyFileVersion in the AssemblyInfo file?
I know a fixed AssemblyVersion is useful to support dll replacement and avoid the assembly binding requirement. But is there any need you have come by that requires the AssemblyFileVersion to be fixed?
This is problematic in one scenario I have, which is the analysis an installer like Install Shield performs to determine if the file should be patched. AssemblyFileVersion is used for that verification and if the version is not augmented from one upgrade to another, It simply isn't replaced (not a great behaviour, but one we do verify).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi is there any reason to fix AssemblyFileVersion in the AssemblyInfo file?
I know a fixed AssemblyVersion is useful to support dll replacement and avoid the assembly binding requirement. But is there any need you have come by that requires the AssemblyFileVersion to be fixed?
This is problematic in one scenario I have, which is the analysis an installer like Install Shield performs to determine if the file should be patched. AssemblyFileVersion is used for that verification and if the version is not augmented from one upgrade to another, It simply isn't replaced (not a great behaviour, but one we do verify).
The text was updated successfully, but these errors were encountered: