question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Assembly version is missing build and revision numbers

See original GitHub issue

Version 0.0.43 is missing assembly version. When this assembly is references in csproj, it shows as

<Reference Include="Ben.Demystifier, Version=0.0.0.0, Culture=neutral, PublicKeyToken=a6d206e05440431a, processorArchitecture=MSIL">
  <HintPath>..\packages\Ben.Demystifier.0.0.43\lib\net45\Ben.Demystifier.dll</HintPath>
</Reference>

Version 0.0.8 shows as

<Reference Include="Ben.Demystifier, Version=0.0.8.0, Culture=neutral, processorArchitecture=MSIL">
  <HintPath>..\packages\Ben.Demystifier.0.0.8\lib\net45\Ben.Demystifier.dll</HintPath>
</Reference>

While this is not a problem by itself. It does cause breakage in any libraries that depend on Ben.Demystifier.

For example, if codeessentials.Extensions.Logging.Demystifier is installed, it works fine with 0.0.8 ,but loading exception is thrown for 0.0.43 :

Could not load file or assembly 'Ben.Demystifier, Version=0.0.4.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:14 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
clairernovotnycommented, Feb 8, 2018

Strong naming is a breaking change, so you’d need to recompile once with the latest version. Before it wasn’t strong named.

Sent from a mobile device, please excuse brevity and typos


From: Oren Novotny Sent: Thursday, February 8, 2018 10:38:59 AM To: benaadams/Ben.Demystifier; benaadams/Ben.Demystifier Cc: Mention Subject: Re: [benaadams/Ben.Demystifier] Assembly version is missing build and revision numbers (#53)

That’s because it wasn’t strong named.

Sent from a mobile device, please excuse brevity and typos


From: Euphoric notifications@github.com Sent: Thursday, February 8, 2018 10:33:55 AM To: benaadams/Ben.Demystifier Cc: Oren Novotny; Mention Subject: Re: [benaadams/Ben.Demystifier] Assembly version is missing build and revision numbers (#53)

@onovotnyhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fonovotny&data=02|01|oren%40novotny.org|d069bab2d70e4c9aef2e08d56f095da4|d1c4ebc6828f4a898786cfbe1f4e8c94|0|0|636537008421376549&sdata=gjaqXyY0h%2F304%2Fq4k2s%2BJmFYhpYwu8VkF%2FcfMDkaOgU%3D&reserved=0 That is not true. Here is sample project BenDemystifyTest.ziphttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbenaadams%2FBen.Demystifier%2Ffiles%2F1707658%2FBenDemystifyTest.zip&data=02|01|oren%40novotny.org|d069bab2d70e4c9aef2e08d56f095da4|d1c4ebc6828f4a898786cfbe1f4e8c94|0|0|636537008421376549&sdata=HyhGbYpPvmRfD1MULAQZ9vcYcnDFT9KBAvWXhC6rF58%3D&reserved=0

It has codeessentials.Extensions.Logging.Demystifier installed. This is built against 0.0.4.0 , but 0.0.8.0 is installed and it works. But after upgrading to 0.0.43 , the above exception is thrown. So it is not exact match and no redirect is needed. But only if Assembly version is greater than 0.0.4.0, which it isn’t for 0.0.43 NuGet package.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbenaadams%2FBen.Demystifier%2Fissues%2F53%23issuecomment-364148873&data=02|01|oren%40novotny.org|d069bab2d70e4c9aef2e08d56f095da4|d1c4ebc6828f4a898786cfbe1f4e8c94|0|0|636537008421376549&sdata=AX9s23uVVqzzFQdwZhlC41LFHNS6DhCzeScqMyaAXlk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABXHVJ87HBebi3ZEzNiXWU_LqiWg2Wp8ks5tSxPjgaJpZM4R9_QR&data=02|01|oren%40novotny.org|d069bab2d70e4c9aef2e08d56f095da4|d1c4ebc6828f4a898786cfbe1f4e8c94|0|0|636537008421376549&sdata=%2BKuwdXEHHL9xUHXLbi8y1h7fCZeE9IHQfrz3S%2FzJMnc%3D&reserved=0.

0reactions
dhazelcommented, Jul 19, 2019

My issue #87 may be related.

Read more comments on GitHub >

github_iconTop Results From Across the Web

c# - AssemblyInfo build number not updated
A version number such as [assembly:AssemblyVersion("1.2. ... 2 as the minor version, and accepts the default build and revision numbers.
Read more >
Use AssemblyVersion and AssemblyFileVersion attributes
Gets or sets the major, minor, build, and revision numbers of the assembly. This error occurs during a build when more than one...
Read more >
Assemblyversion revision build not set using
I'm on VS2017 Community 15.5.2 and notices my assemblyversion is not set using genertaed buld and revision anymore. File\New project: ASP.
Read more >
Making Sense of AssemblyVersion Numbers
A Guide to AssemblyVersion and FileVersion. The components of a Microsoft DLL or EXE version number are Major, Minor, Build, and Revision.
Read more >
Updating the version number in your .NET build pipeline
The built assembly that the command has created in the bin folder will correctly have the version number set as per the command....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found