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.

v1.2.0 loads from NuGet as version `0.0.0.0`

See original GitHub issue

This causes the Visual Studio compiler warning of Found conflicts between different versions of "FastMember.Signed" that could not be resolved. because ClosedXML expects >=1.1.0

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

DmytroHubernatorovcommented, Feb 25, 2018

I’ve changed in web.config to this:

<dependentAssembly>
        <assemblyIdentity name="FastMember.Signed" publicKeyToken="9e8f22703bef9a29" culture="neutral" />
        <bindingRedirect oldVersion="1.0.0.9" newVersion="0.0.0.0" />
      </dependentAssembly>

and it started to work.

0reactions

mgravellcommented, Mar 6, 2018

Sorry, this is fixed in 1.3.0

Top Results From Across the Web

Nuget keeps reverting redirects to incorrect version ...

I have a solution where two different versions of a package are in use, call them "PackageA v1" and "PackageA v2". One project...

How to resolve .NET reference and NuGet package version ...

Here's an example: project A might use log4net V1.1 and project B uses ... Use a single reference versions or load versions side-by-side....

NuGet Package Version Reference

The package's own version is SemVer v2.0.0 compliant but not SemVer v1.0.0 compliant, as defined above. Any of the package's dependency version ......

System.Net.Http v4.2.0.0 being copied/loaded from ...

Net.Http.dll. In short, for some reason after adding nuget package for System.Collections.Immutable v1.4.0, the MSBuild version of System.

How to resolve “Could not load file or assembly … or one of its ...

When we use multiple versions of same assembly, it is more likely to encounter this runtime exception. It is easy to resolve provided...