Geek Answers Handbook

Cannot resolve project link due to indirect dependency on current target structure

Can someone translate this into English?

The primary reference
"Microsoft.SQLServer.ManagedDTS, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=MSIL"
could not be resolved because it has an indirect dependency on the .NET Framework assembly
"mscorlib, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
which has a higher version "2.0.3600.0"
than the version "2.0.0.0" in the current target framework.

Is this a problem with the target version of MY PROJECT or a problem between .Net and the SQL Server library I'm trying to use?

I need to target .Net 2.0, but I don’t care what sub-level (2.0.3600). Can this be changed? I looked at the project properties and in any case did not see sub-level changes (only between .Net 2, 3.5, 4, etc.)

What do I need to do to get around this?

+5
source share
2 answers

I solved the problem (for SQL Server 2005) by building my project on .Net version 4 instead of 2.

+4

, , .

, .

, mscorlib 2.0.3600, - 2.NET 2.0. , , - 2 . Ooopppss...

, , . , Visual Studio line: msbuild {projectname}/v: d /t: rebuild/fl

msbuild.log. , .

, app.config . , , , DLL.

SpecificVersion = true . , . , , , , .

, .NET v2.0 2, , -Beta2.

,

Visual Studio Chuck England - MSBuild

. - Microsoft.SQLServer.msxml6_interop.dll GAC , . , dll, .

- .config.

.config, , , . , .

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1" appliesTo="v1.0.3705">
     <dependentAssembly>
        <assemblyIdentity name="mscorlib" publicKeyToken="b77a5c561934e089" culture="neutral"/>
        <bindingRedirect oldVersion="2.0.3600.0" newVersion="2.0.0.0"/>
     </dependentAssembly>
    </assemblyBinding>
</runtime>
+5

More articles:


All Articles