I am developing a C# application that needs to reference certain Interop's for Microsoft Office (currently 2003). The problem is our development machine has Office 2003, but we don't know what all the deployment machines will have (they could have 2003 or 2007 or XP or none). The way I thought to fix this is if I set "Copy Local" to true for the references of Office in our project they would get added to the application directory and be sent to every machine that needs (and in theory, should work). Now the question is, is that the way to do this or will I be violating an Office licensing agreement by providing the Office DLL's to all computers that install my application, whether or not they have Office installed? I just want to make sure I keep things above board and couldn't find anything on the internet explaining this. thanks for your help
guid
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
There was a talk about being able to build application on Framework 1.1. with VS2005. I believe the add on was called msbuild. Try searching on google for "msbuild" or "vs2005 and framework 1.1" and see what will came up.
As far as I remember reading, with this add on you could build application on framework 1.1 with VS 2005
Goran
Mikal613,
>>We are using 2000 because our clients have that version.<<
Did you have to install 2000 on your development machine or did you somehow install the 2000 PIA's along with a later version of Office?
I Understand that the lowest version is better for backward compatibility, however as I stated in my question, its possible one of our customers won't even have a version of Office. It would be rare, but I've been told to prepare for it. In that case, will my application crash even after they install the interops if Office isn't there? Or is there some way to provide the type libraries also in case they don't have office? Or do I have to test for Office on the machine and disable that functionality if it is not found (which doesn't seem like it would be easy or the best way). Just trying to figure out how all this works so I know what to do about this. thanks for the help
What about if I provided them with Office viewers for the office applications they are using, will that allow my application to perform correctly, as long as I'm not creating office documents? Mainly what I'm trying to give the users is a way to read from existing documents (Word/Excel) and integrate the data in them into a database. There is no writing to Word/Excel, only reading so I'm thinking the viewers may work, but am wondering if you tried this before?
Excel Viewer 2003
http://www.microsoft.com/d
just curious.
thanks
guid
Business Accounts
Answer for Membership
by: Mikal613Posted on 2007-06-15 at 11:00:10ID: 19294006
You want to go with the lowest version number of office because it is bacward compatible and not forward. We are using 2000 because our clients have that version. You dont deploy the actual type libraries but you use the interop.
http://msdn2.microsoft.com