Geek Answers Handbook

Version-specific assembly references when a particular version is False

I recently had problems with my projects requiring specific versions of their link assemblers, even though in my Visual Studio project these links are marked as Specific Version = False. For example, I replaced MyAssembly.dll version 1.0.0.0 with MyAssembly 1.0.1.0, and applications that link to MyAssembly.dll will receive an error saying that version 1.0.0.0 cannot be found. The property of the specific version does not seem to work. This is a huge pain because I need to rebuild and redistribute every application that references the assembly, even if there are no changes in the new version. I know that in the past, when it was false, he would use any version, and if more than one were found, then the latest version would be used. Does anyone know what the problem is?

Edit: this was open without any answers. The question is not clear? I want to know if there is a way to update assemblies that my .NET application depends on the new version without rebuilding my .NET application.

+5
source share
1 answer

Hi, I had the same issue with the Sharepoint project, and I fixed it by editing the app.config file and adding the following configuration tag. It did the trick.

The specific version is a compile-time issue. I did not know that.

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.SharePoint.Dsp" publicKeyToken="71e9bce111e9429c" culture="neutral" />
        <bindingRedirect oldVersion="11.0.0.0" newVersion="14.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  <runtime>
0
source

More articles:


All Articles