What does this build error mean?

  • Thread starter Thread starter Tommy Malone
  • Start date Start date
T

Tommy Malone

Error: The dependency 'mscorlib, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=969db8053d3322ac' in project 'MohawkProfit' cannot be copied
to the run directory because it would conflict with dependency 'mscorlib,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

And how can I fix it?
 
Check the project's mscorlib reference properties. I'd bet that you have
that set to copy local. Change the CopyLocal property to false and it
should fix it.
 
Before this error, mscorlib was not listed in the references section. I have
added it and ensured that the "Copy Local" property is set to false. The
errors referenced below have disappeared from the Task List, however, now
when I build I get the "Build Errors" dialog but with no errors in the Task
List to resolve. The is frustrating because I don't know what has changed
since today and last Friday to suddenly cause these errors.

I'd appreciate any assistance in resolving this.
 
It looks like you have referenced something that is built for the desktop -
the conflicting mscorlib is the one from the full framework
 
Hi,
try this as suggested by Neil Cowburn...
"The problem lies with the reference order within the .vbdproj file. Open
the .vbdproj file in Notepad, scroll down the the References and manually
move the mscorlib reference so that it is position ABOVE any OpenNETCF
references. Save the project file and open in VS .NET. It will build fine. "

HTH

Pete
 
I just picked up exactly the same error having included OpenNETCF in a
project to access the Registry functions.

Adding a reference to mscorlib and then manually editing the .vbdproj file
as suggested to make mscorlib the first entry seems to have fixed the
problem.

But why should adding a reference to the OpenNETCF (for OpenNETCF.Win32
Registry functions) which I obtained by installing the
"smartDeviceFramework" on top of several of the earlier OpenNETCF libraries
(projects using these still compile without error) cause so much problem.
 
I just picked up exactly the same error having included OpenNETCF in a
project to access the Registry functions.

Adding a reference to mscorlib and then manually editing the .vbdproj file
as suggested to make mscorlib the first entry seems to have fixed the
problem.

But why should adding a reference to the OpenNETCF (for OpenNETCF.Win32
Registry functions) which I obtained by installing the
"smartDeviceFramework" on top of several of the earlier OpenNETCF libraries
(projects using these still compile without error) cause so much problem.

~A
 
The VB project build process doesn't allow us to explicitly place the
reference properly. It works fine under C#, which is what was tested more
heavily. We're investigating how to fix this with the 1.1 deployment.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net
 
Back
Top