Multiple versions of MSProject

[sfong]

Hi,

I am developing an addin for the MSProject and I would like to
support 2002 and 2003. Microsoft recommends to build a version of the
add-in for each version of Office that I intend to support.
http://support.microsoft.com/?id=840585
Is it possible to make it into one setup file and support both
versions of MSProject?

Thanks,
Jonathan

 

[Fredrik Wahlgren]

Hi,

I am developing an addin for the MSProject and I would like to
support 2002 and 2003. Microsoft recommends to build a version of the
add-in for each version of Office that I intend to support.
http://support.microsoft.com/?id=840585
Is it possible to make it into one setup file and support both
versions of MSProject?

Thanks,
Jonathan

I'm not sure what you mean. A simple way to do support both versions, create
one project with two solutions. I guess the installer can figure out what
version it should install by querying the msproject version. Am I missing
something?

Besides, you only need two versions if you create a .NET project. Using VB6,
you don't.

/ Fredrik

 

[sfong]

Hi Fredrink,

I am using .Net. I am looking for a single deployment solution for
both versions of MSProject. I don't want to create two different
verions of setup.exe for each version of MSProject. I guess I need two
VS solutions for each version of MSProject because they are referring
different interop assembly. Is that right?

Jonathan

 

[Fredrik Wahlgren]

Hi Fredrink,

I am using .Net. I am looking for a single deployment solution for
both versions of MSProject. I don't want to create two different
verions of setup.exe for each version of MSProject. I guess I need two
VS solutions for each version of MSProject because they are referring
different interop assembly. Is that right?

Jonathan

Why should you create two different versions of setup? Do you use something
like InstallShield? It should be possible to include both files in setup.exe
and have internal IS logic decide which version to install.

I guess I need twoVS solutions for each version of MSProject because they are referring
different interop assembly. Is that right?

Right. One project with two solutions.

/Fredrik

 

[sfong]

I got another question, can I install both MSProject in a single
machine without affecting each other?

Thanks,
Jonathan

 

[Fredrik Wahlgren]

I got another question, can I install both MSProject in a single
machine without affecting each other?

Thanks,
Jonathan

I have no idea.

/ fredrik

 

[Tom Winter]

I don't know about MS Project, but for (most) other MS Office applications,
like Word, Excel, etc., you can install multiple versions, just make sure
you change the installation folder during install so each gets its own
folder. If you switch between different versions of the apps, Windows
Installer might pop up real quick when the app starts, but it will go away
and the app will start OK. (This happens for example if you use Word 2000,
then start up Word 2003.)

Not that you can only have ONE version of Outlook on your system, no matter
what.

-Tom

 

[sfong]

Fredrik,

Do you compile the solutions in one machine or two machines to
against different versions of MSProject?

Jonathan

 

[Fredrik Wahlgren]

Fredrik,

Do you compile the solutions in one machine or two machines to
against different versions of MSProject?

Jonathan

You compile on one machine. Just make sure you have the necessary PIA's on
that machine. You should test your code on a different machine without VS
..NET once it seems to work OK on your development machine. You may want to
use VmWare on your test machine. Actually, with vmware on your dev pc, you
could switch to a different environment to test your code.

/Fredrik

 

[Bill Bordiuk]

Well, I thought I posted this yesterday but it disappeared, so here goes:

You can have multiple versions of MSP on one machine. I have 2000, 2002, and
2003 running together. You just have to make sure to install them in
separate folders and to not let the installer update previous global files.

Why do you need to refer to different object models for 2002 and 2003? If
you're not using any functionality particular to 2003 only, just compile
with the 2000 file or the 2002 file and you shouldn't have any compatibility
problems with 2003. I make my (VB6-based) add-ins with the 2000 library and
they work on versions 2000 and above.

Bill B

 

[sfong]

Yes, I knew that compiles with the earily version should work fine with
the later verion. I just want to make sure that the compiled code is
full compatible with the target version and enables to access the new
functionalities.

Jonathan