Supporting multiple office versions

Question

0.00/5 (No votes)

See more:

I am working on a project in .Net which is an addin to office. The issue is that the solution needs to compile addins for Office 2003, 2007 and 2010 while sharing the same business logic between these.
What is the best way to accomplish this and still have a maintainable solution? Ideally I would like to NOT use different development machines for the various office versions, and use only one version of Visual Studio (2010).

Posted 1-Jun-10 17:48pm

The Man

Updated 1-Jun-10 18:11pm

Abhinav S

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

V. · Answer 1 · 2010-06-04T00:03:00

A long, long time ago, in a galaxy far, far away I think we solved that by looking into the registry which office was installed, bind the corresponding object and call the methods that way. You'll need to test this thouroughly though, because not all methods and objects will be the same between versions.

I propose to start testing with different versions by writing quick and dirty test applications and then move on to a good design for the real application.

hope this helps.