c# - Can't resolve project reference because of indirect dependency on current target framework -

Text after "

Can someone translate this into English?

  primary reference "Microsoft.SQLServer. ManagedDTS, Version = 9.0.242.0, Culture = neutral, PublicKeyToken = 89845dcd8080cc91, processorArchitecture = MSIL, Version = 2.0.3600.0, Culture = neutral, PublicKeyToken mscorlib" because it can not be solved in an indirect dependency on the .NET framework assembly "= B77a5c561934e089" which aim to present "2.0.0.0" version later version "2.0.3600.0" in the structure.   
 Is this trying to use the problem between the target version of my project or the .NET and SQL Server libraries?  
 I need this .NET 2.0 target, but I do not care whether sub-level (2.0.3600) can it be changed? I looked under the project property and sub-level (only net 2, 3.5, did not change in the middle of 4, etc.)  
 I need to do to get around it ?   
 
 
 I found the problem and at least it has been explained.  
 
 Thanks for taking the time to send us this problem  
 It appears that the reference is 2.0.3600 mscorlib, which is the beta 2 of .NET 2.0. Normally it only will work themselves, with the hit version number of shipping the product itself, but, in this case, beta-2 number is actually more Ooopps ...  
 determine reference For that where really is coming from, we really need to start with a detailed log. You can obtain this by executing the following from a visual studio command line: MSBuild {ProjectName} / v: d / t: rebuilding / fl  
 This will create an msbuild.log file. Please attach it to the bug so that we take a look.  
 As told in the thread, you can change an app. For redirecting the configuration, however, it will work only with and executable, and this is only the band support is the real issue, which is that you are using DLL from our date.  
 You can also use SpecificVersion = True on the reference. However, it defeats multi-targeting, and is an unsupported advanced scenario. This is basically because once you do this, you can get other errors, and you have to know what you are doing to do this work.  
 We need to determine the actual assembly that is referred to .net v2.0 beta 2 so we can determine how you can get the latest version of non beta2 assembly  
 Thanks,  
 Chuck England Visual Studio Forum Program Manager -. MSBuild   
 There are also two possible fixing options for posting here. One has to update the version of Microsoft.SQLServer.msxml6_interop.dll to GAC with the version that is the right manifest. I'm not sure where you'll get Dell, but it is readable through posts on other sites.  
 The second option is the .config file revision.  
 Here's what they put for a .config change, but the poster said that it works in executable, but not in the class library. I hope it helps.  
  & lt; Runtime & gt; & Lt; Apply assembly xmlns = "urn: Skima-microsoft-com: asm.v1" to = "v1.0.3705" & gt; & Lt; DependentAssembly & gt; & Lt; Assembly name = "mscorlib" publicKeyToken = "b77a5c561934e089" culture = "neutral" /> & Lt; Compulsive Redirect Old Version = "2.0.3600.0" Newverson = "2.0.0.0" /> & Lt; / DependentAssembly & gt; & Lt; / AssemblyBinding & gt; & Lt; / Order & gt;