Bad reference issue in VS .NET 2003

  • Thread starter Thread starter Neil Cowburn [MVP]
  • Start date Start date
N

Neil Cowburn [MVP]

Today, I openned a solution I've been using just fine for
the last few months and ran a build. The build failed and
my investigations found that the one of the references in
one of the projects had become corrupted.

Essentially, while the name of the referenced assembly was
correct in the treeview, the property grid showed that an
entirely different assembly had been added (see image at
URL below). Removing the offending reference and re-adding
had no effect. Restarting VS had no effect.

Image URL:
http://blog.opennetcf.org/ncowburn/content/binary/badrefere
nce.png

--Neil
 
In the past I have had to edit the device project file in notepad. In
particular the elements under <References> under <Build>. Have you had a
play with that?

Alternative solution (and I am running out of ideas here:-) is to remove all
references, delete all referenced dlls under your bin folders (noticed you
have Copy Local to true), restart VS and re-add the references.

Cheers
Daniel
 
Is/was the reference to a project within the same solution? What does the
project file actually contain e.g.
<snip>
<Reference
Platform = "Windows CE"
Name = "OpenNETCF"
Project = "{EEE28D3C-9C36-4968-8AD1-0DE97C42B6B6}"
Package = "{20D4826A-C6FA-45DB-90F4-C717570B9F32}"
/>
<Reference
Platform = "Windows CE"
Name = "OpenNETCF.Drawing"
Project = "{FA15C437-D0AA-4C99-A1F2-5581CAB8F7B8}"
Package = "{20D4826A-C6FA-45DB-90F4-C717570B9F32}"
/>
<Reference
Platform = "Windows CE"
Name = "System.XML"
AssemblyName = "System.Xml"
/>
</snip>

Do the Project guids match up (if applicable), what about the Name /
AssemblyName properties?

Peter
 
I fixed the problem by crafting a new project for
referencing. I'm still not sure what caused this issue.
Will investigate further.

--Neil
 
Back
Top