Solved

dll reference in vb 2005

Posted on 2006-07-12
3
240 Views
Last Modified: 2010-04-23
Hi Guys

I have created a solution which is converted from a vb 6 project. This solution consists of several projects.

For some of my forms located in a specific project I get the following exception, this happens when I try to look at the form in the designer:

"Could not load file or assembly 'NodeLib, Version=1.0.2329.20641, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. "

It is accompanied with the exception that pinpoints the code, which is in the part generated by the designer

The project has a reference to another/newer version of the nodelib, namely 1.0.2329.29903.

The nodelib is another project in the solution that we have created.

So it is quite clear what is wrong, namely: that some code references to another version of a dll that the one we have actually built. The things that puzzles me is how/where the reference to the "wrong" dll are created. I wont to track that down. Does anybody have a suggestion to this?

Or better. Have anybody experienced the same problem and the possible solution.

Thanks, Niels



0
Comment
Question by:nielsboldt
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 96

Accepted Solution

by:
Bob Learned earned 500 total points
ID: 17090241
1) In the AssemblyInfo.vb, there is a version element.  By default it uses 1.0.*.  You should change this to a specific number, like 1.0.0.0

2) I believe that this might be a problem because the solution has been fully built yet.

Bob
0
 

Author Comment

by:nielsboldt
ID: 17097967
Hi Bob

That surely helped a lot - just for fun, are there a deeper explanation to this?

Thanks, Niels
0
 
LVL 96

Expert Comment

by:Bob Learned
ID: 17099010
When assemblies are resolved, the entire version comes into play.  This allows multiple assemblies to have the same name, but different versions, and the application can decide which assembly to load.  An automatic updater application that has a current version, and a new version of a DLL to install is a good example.  When you don't specify the full version, there is an algorithm for generating the rest, and it depends on the time of day.

Bob
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A while ago, I was working on a Windows Forms application and I needed a special label control with reflection (glass) effect to show some titles in a stylish way. I've always enjoyed working with graphics, but it's never too clever to re-invent …
It’s quite interesting for me as I worked with Excel using vb.net for some time. Here are some topics which I know want to share with others whom this might help. First of all if you are working with Excel then you need to Download the Following …
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…

634 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question