I would like to know how I can determine the source of this build error;
Warning 4 The primary reference "MyNamespace.MyProject" could not be resolved because
it has an indirect dependency on the .NET Framework assembly "System.Xml, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089" which has a higher version "4.0.0.0" than
the version "2.0.0.0" in the current target framework. MyNamespace.MyOtherProject
I understand the meaning of this error (and the 5 others like it for this same project), but I cannot work out how to resolve it in my case. The ‘primary reference’ in this case (MyNamespace.MyProject) has no direct dependencies on .NET 4.0.x.
The primary reference depends on only one other project of mine (MyNamespace.MyCoreProject), which the source project for the build (MyNamespace.MyOtherProject) also depends directly on. And the build is not complaining about that project having indirect references to .NET 4.0.x, so I assume I can rule that out.
The primary reference has a direct dependency on three (3) 3rd party DLLs, all of which also Target .NET 2.0.
I have employed dotPeek to examine the built libraries, and cannot see any reference to anything using .NET 4.0.
The only other potential spanner in the works is the use of PostSharp, which is directly referenced by ‘MyNamespace.MyCoreProject’ (referenced by the primary reference project), which may be causing the problem, as I believe there is a related VS2010 bug when referencing PostSharp.dll (http://www.sharpcrafters.com/forum/Topic4444-4-1.aspx#bm4462), however I also removed that from the build chain and still see this error, so I assume I can also rule that out.
If someone can tell me why this is happening, fantastic! If not, some direction on how to work out what the unnamaed ‘indirect reference’ is would be just as helpful!
Incidentally, I have tried all of the following tools to get some info, but they’re not telling me much I didn’t already know (which is the direct dependencies of the DLL in question);
– .NET Reflector
– dotPeek
– IldAsm
– Depends (Dependency Walker)
Whilst I have not actually worked out a good way to actually solve the problem of determining how MsBuild determines the references it uses (why it does not just tell me how it comes up with these indirect references, instead of making me guess I don’t know…) I have solved my problem.
In the end, I basically removed all references in the ‘primary reference’ project, (which required excluding all code piece by piece – a somewhat painful process) to determine that the source of the supposed indirect reference to .NET 4.0 libs was caused by a 3rd party DLL that was referenced.
However, I do believe there is a bug in MsBuild behind this problem, as;
Now, another curiosity is that I’ve not touched or changed the relevant libs in some time, so this has just started happening for some other unrelated reason – what that may be, I don’t know.
In the end, the only way I found to solve this issue was to run gacutil /u for each of the relevant libs to remove previously installed/used versions of the 4.0 libs. (There were about 40 in the package, so that was also painful! as the package’s uninstaller did not remove the libs in the GAC)
This seems to have let msbuild start using the references I told it to, rather than coming up with its own idea of what ‘use this file’ and ‘use this specific version means.
Solved, but I would have loved a cleaner way to do this!