Develop for lower version of Office, than installed

[Peter Baranyi]

Hi All,

I have Office 2007 installed on my machine, however I want to develop for
Office 2003. The application would be in c# (if this counts at all), with
VisualStudio 2005.
I remember something I read,but I cannot remember what it was: not even that
it was possible or it was not....
Can you guide me, please?

Thanks:

Peter

 

[Jonathan West]

Hi All,

I have Office 2007 installed on my machine, however I want to develop for
Office 2003. The application would be in c# (if this counts at all), with
VisualStudio 2005.
I remember something I read,but I cannot remember what it was: not even
that
it was possible or it was not....
Can you guide me, please?

I rather think you asked much the same question in this group under the name
"Jon Kruger" just a few days ago.

If you want to develop for Office 2003, you had better install Office 2003.
No way round that if you want to develop and test your application under
reasonably realistic conditions, such that it has a decent chance of working
on a customer's PC. As I said in my answer before, you can do this on a
virtual machine if you don't want to uninstall Office 2007.


--
Regards
Jonathan West - Word MVP
www.intelligentdocuments.co.uk
Please reply to the newsgroup
Keep your VBA code safe, sign the ClassicVB petition www.classicvb.org

 

[Peter Baranyi]

Dear Jonathan,

thanks for the answer, I found your reply. However I have no problem with
the testing, I have a testbed computer, where I can test the application
itself. My concern is only the development. Let's suppose I will not use
anything what is not available in the v11.0 Office, and I put the v12.0
references into my project. Will this work at all on a machine, where only
v11.0 available? Did MS changed the syntax, member names, parameter types,
etc. from v11.0 to v12.0, what makes absolutely impossible to develop? Do you
have any experience about this?

Thanks:

Peter

 

[Jonathan West]

Dear Jonathan,

thanks for the answer, I found your reply. However I have no problem with
the testing, I have a testbed computer, where I can test the application
itself. My concern is only the development. Let's suppose I will not use
anything what is not available in the v11.0 Office, and I put the v12.0
references into my project. Will this work at all on a machine, where only
v11.0 available? Did MS changed the syntax, member names, parameter types,
etc. from v11.0 to v12.0, what makes absolutely impossible to develop? Do
you
have any experience about this?

Ultimately the only way to know is to test with both versions. You should
develop using the oldest version, and compile your app using those
references.

This has two benefits

1. For the most part, newer versions are a superset of theolder versions, so
you are less likely to hit a feature that will be unsupported in the newer
version.

2. When you install onto a computer with a newer version, the references
should update automatically.

With the installation onto the newer version, you can then test to make sure
it all works right there as well.