pbrand -
There are several issue wrapped up in this thread:
Why you might be getting an assembly not found error even though the assembly is in the GAC
We have separate copies of Common for targeting Framework 2.0 and Framework 3.5. We encode the version number of the Framework that we target in the third segment of the version number. For example,
NationalInstruments.Common with a version number of 8.6.35.131 supports .NET Framework 3.5
NationalInstruments.Common with a version number of 8.6.20.131 supports .NET Framework 2.0
We also give the 2.0 and 3.5 assemblies different public keys, to allow us to support this scheme and use policy files. In your case, your project might be referencing the 3.5 version of Common, which can't be loaded on a machine without .NET Framework 3.5.
CLR version 2.0.50727
Both .NET Framework 2.0 and .NET Framework 3.5 use this same version of the Common Language Runtime. That is, .NET Framework 3.5 uses the same underlying Runtime as 2.0. It just has some new and revised libraries. MStudio uses these new and revised libraries, so we need to have different versions of our product to support each version of the .NET Framework (even though the underlying CLR is the same).
Using MStudio in VS2008 projects that target Framework 2.0
To use MStudio in a VS2008 project that targets Framework 2.0, you need to install MStudio for VS2005 and manually reference those assemblies instead of the assemblies installed with MStudio for VS2008. Please see my posts on 7/29 and 7/30, in this thread - http://forums.ni.com/ni/board/message?board.id=232&message.id=8912#M8912 - for more information.
David Rohacek
National Instruments
Message Edited by drohacek on 08-17-2009 09:00 AM
