Referencing Visio library 2003 with VS2008

[Michel LAPLANE \(MVP\)]

I'm using Visual Studio 2008 on a vista computer where Visio 2003 and Visio
2007 are installed
I am creating an add-in that must work with Visio 2003.
When i am adding Visio 11 type library reference, in my project, the Visio
12 Interop.visio.dll assembly is added
I dont find any way to force visual stuidio to really get the Visio 11
assembly without desinstalling Visio 2007.
Does anyone can help ?

 

[Al Edlund]

Michel,
Are the v2003 libraries in the GAC? Are they viewable as references? I
believe that they may both have the same name which leads to the confusion
issue (might have to de-reference the v2007 library to build with the
v2003).
al

 

[Michel LAPLANE \(MVP\)]

Hi al,
Yes they are in the gac. i have try to delete just the Interop.visio 12.0
assembly without deinstalling visio 2007. Vista cannot do it.
Do you think there is a way with .config file (used for .NET assembly) to
tell to VS2008 to load only the 11.0 version ?
Best regards

 

[Al Edlund]

Michel,
I think either Chris or David showed how to do a conditional assembly based
on libraries. I'll send a note off-line.
al

 

[David Parker]

Michel,

Unfortunately I think that you need to set up a VPC with VS2008 and Visio
2003 - DO NOT install any Visio 2007 compenents on it ... ever ... oherwise
you will need to start again with another clean VPC. You can then use the
same source code on both PCs, and you can add a conditional parameter to the
project to enable you to have conditional sections in your code. This is
what I do with VS 2005, but of course, I need to change the reference to
Visio 11 Object Library on the Visio 2003 VPC.

Senaj first alerted to me the problem of VS with Visio 2003 when you also
have Visio 2007 on the same PC.

 

[Michel LAPLANE \(MVP\)]

Thanks David

Michel,

Unfortunately I think that you need to set up a VPC with VS2008 and Visio
2003 - DO NOT install any Visio 2007 compenents on it ... ever ...
oherwise you will need to start again with another clean VPC. You can
then use the same source code on both PCs, and you can add a conditional
parameter to the project to enable you to have conditional sections in
your code. This is what I do with VS 2005, but of course, I need to
change the reference to Visio 11 Object Library on the Visio 2003 VPC.

Senaj first alerted to me the problem of VS with Visio 2003 when you also
have Visio 2007 on the same PC.



--
David Parker
Microsoft MVP (Visio)
http://bvisual.spaces.live.com
http://www.visualizinginformation.com