Problems using 2002 Assemblies on 2003

[Marius Storm-Olsen]

Hi all,

I'm creating an addin for the .NET IDE, and have the following problem.

It's using C#, and is packaged into a installer with the .NET 2002
version. Obviously, this results in the 7.0 version of
Microsoft.VisualStudio.VCProjectEngine.dll being packaged.

Now, I need the addin to work with both the 2002 & 2003 version of .NET.
For people who have both versions installed (which is my case), there's
no problem. But people who only have the 2003 version installed, they
get the error message:
"The located assembly's manifest definition with name
'Microsoft.VisualStudio.VCProjectEngine' does not match the assembly
reference".

My question is, what would be the cleanest way to resolve this issue?
Will my installer have to dynamically change the manifest, package both
7.0 & 7.1 version of the DLL, or ..?


Thanks for any help!

Sincerely,
Marius

 

[Cowboy \(Gregory A. Beamer\)]

You have a couple of options.

1. Have the installer dynamically install the proper version
2. Use reflection.emit to have the code generated (by a custom installer) on
the client

I think 1 would be the easier solution, but 2 could work, as well.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****