VB.NET 2008 different versions of same dependant assembly

[walter-donovan]

Hi all. I have a few programs I worked on using 2 different computers and got this warning at build. When I look at references I see 2 possibilities. One is NET framework. Some things want v3.5, some want v2.0. Is this a conflict? Examples are system and system.drawing which only show choices for v2.0.0.0.

Second is DAQmx. I have v9.3.0 but the refs say 9.3.35.###. Is this a conflict? v9.3.0 doesn't show up as a choice. Any thoughts?

[D-Cubed]

Hi walter-donovan,

Have you seen our KnowledgeBase article on this issue?  The problem is happening because you cannot reference two versions of the same assembly within one application domain.  This discussion, found in the Microsoft Developer Network discussion forums, might be helpful in understanding this issue.

As far as DAQmx goes, 9.3 refers to the larger release of the driver software.  The points thereafter refer to patches released on top of the main release.  This should not be causing any issues.  I checked the readme file for NI-DAQmx 9.3, and it appears to indicate LabVIEW 8.5 and Measurement Studio 2008 are compatible.

Please let me know if you have any questions.

Warm Regards,

[walter-donovan]

Thanks Daniel. When I read your post I got excited that there was a solution I could understand and implement. I read both the knowledge base and the discussion. They said to change output verbosity and I would see the offending assemblis. I did this, built, debugged and rebuilt. I can't find the info on the asemblies anywhere. Not in the error box, not in any directory within my project. Any ideas?

[D-Cubed]

Hi walter-donovan,

Can you post a screenshot of the error message you are getting?  I would like to see what you are seeing.

Additionally, you mentioned earlier that some of your components want .NET 3.5 and some want 2.0.  Is there any way you can avoid this conflict?

Warm Regards,

[walter-donovan]

I had to abandon this project because I got swamped with other things but now I made a few changes to a different VB.NET program and get the same warning. This time there is an entry in the column "FIle" (never showed up before). Entry is "C:\WINDOWS\Framework\Microsoft.NET\v3.5\Microsoft.Common.targets". So it finally points to Framework. I took a screen shot with Properties/References open. This shows what I was talking about previously that some refs are for Framework. NET v2 and some v3.5. Is this the problem? If so how do I fix it. These programs were probably started long ago while I ran v2.0 but then update Framework as time went by.

[walter-donovan]

Anyone???

[D-Cubed]

Hi Walter,

I apologize for not seeing your last post.  I have been searching around on the internet for similar issue, and I found this forum post which discusses the exact warning.  

When you build the project, does it fail?  Does it give any errors, or just warnings?

It might be useful to check the output of the build to find more clues as to where these assemblies are being referenced so you can correct it. 

Let us know what the result of trying the steps in the previously linked forum is, and we can continue to work through this warning.

Warm Regards,

[walter-donovan]

Thanks Daniel. You're confusing me a little. Doesn't the screen shot in my last post show the warning and also the different references, including different version numbers for the .NET parts?

I read the article in the link and it mentioned that there may be different .NET versions for different projects (I assume within a single solution). I have only one project in this solution although it is possible that at one time, there was also a Setup project in the solution.

If I recall I think that (possibly) all my programs ran without warnings until I tried to make Setup projects to deploy them. In most, I dumped the Setup project because I could never make them work correctly.

So are the different version number that show up in my screen shot the mismatch that's wrecking everything? If so how do I fix it?

As far as your suggestion to check the build output, I don't know how to do that. I followed an article from mS on setting switches for build verbosity to normal and detailed but never could find the information in the manifest file or whatever they pointed me to.

[D-Cubed]

Hi Walter,

The screenshot you posted shows that you are referencing System.Data from .NET 2.0, and System.Data.DataSetExtensions from .NET 3.5.  These might be causing the warning.  

In order to show the build output, you can use the keyboard gesture <Ctrl-W-O> or select View»Output.  When you rebuild or try to debug your program, this Output window will display any compiler messages.

Please try to run the program, and show us the output.

Thank you,

[walter-donovan]

Hi Daniel,

Here's the output from the build.