Assembly information download

Asked 11 years, 11 months ago. Active 11 years, 11 months ago. Viewed 9k times. Arlen Beiler Arlen Beiler Add a comment. Active Oldest Votes. Jon Palmer Jon Palmer 7 7 bronze badges.

Charlie Salts Charlie Salts Joel Etherton Joel Etherton Josh Josh Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. If you release new version of assembly frequently, say once every day, and if assemblies are strong named, Developers will have to change the reference every time you release new assembly. It can be cumbersome and may lead to wrong references also. A better option in such closed group and volatile scenarios would be to fix the AssemblyVersion and change only the AssemblyFileVersion.

Use the assembly file version number to communicate the latest release of assembly. In this case, developers won't have to change the references and they can overwrite the assembly in reference path. In central or final release builds it makes more sense to change the AssemblyVersion and most keep the AssemblyFileVersion same as assembly version.

Skip to main content. This browser is no longer supported. Corresponds to ComVisibleAttribute. For more information on setting these properties when generating a NuGet package in a. NET Framework class library, see Configure project properties for the package. And for more information about Licensing and Expressions as they relate to a NuGet package, see licenses. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note For more information on setting these properties when generating a NuGet package in a.

Submit and view feedback for This product This page. View all page feedback. In this article.