I hope I am posting this in the right news group. If not I apologize.

I need to write a C# application that supports multiple versions of Excel;
2000 and up. I have written code to support a single version of Excel
before, but have never had to support multiple versions. Based on what I
have found online to this point, I believe these are my options.

- Write code for each version by branching the code. Microsoft apparently
does no support writing code to handle multiple applications and strongy
recommends coding/building for each version individually.

- Write code to the lowest supported version and test against other
supported versions. This may work as long as versy basic functionality is
used and nothing specific to newer versions or dropped in newer versions is
used.

- Use Assembly Binding Redirect. I have never used this before and don't
know if it is possible. In my research I found the Office 2007 apparanently
allows for redirection to Office 2003. Is this a viable solution? Is it
possible to allow for multiple redirections not knowing which version a user
will have?

I know the first option should work, but it is something I would like to
avoid. Is the third option viable. Do I have any other options?

At this point I don't know if I coding against framework 1.1 or 2.0. Are
there any limitations supporting multiple versions working with either
framework?

Thanks.

You may get an answer here, but I would
Look down the left side of the communities web page (where it appears you
are posting) and see the Office Developer groups.

Post in those groups. This group is aimed primarily at using VBA as a macro
language in Excel.

--
Regards,
Tom Ogilvy


"John Mercure" wrote:

I hope I am posting this in the right news group. If not I apologize.

I need to write a C# application that supports multiple versions of Excel;
2000 and up. I have written code to support a single version of Excel
before, but have never had to support multiple versions. Based on what I
have found online to this point, I believe these are my options.

- Write code for each version by branching the code. Microsoft apparently
does no support writing code to handle multiple applications and strongy
recommends coding/building for each version individually.

- Write code to the lowest supported version and test against other
supported versions. This may work as long as versy basic functionality is
used and nothing specific to newer versions or dropped in newer versions is
used.

- Use Assembly Binding Redirect. I have never used this before and don't
know if it is possible. In my research I found the Office 2007 apparanently
allows for redirection to Office 2003. Is this a viable solution? Is it
possible to allow for multiple redirections not knowing which version a user
will have?

I know the first option should work, but it is something I would like to
avoid. Is the third option viable. Do I have any other options?

At this point I don't know if I coding against framework 1.1 or 2.0. Are
there any limitations supporting multiple versions working with either
framework?

Thanks.