- Background: I write a lot of software/scripts that automate repeated tasks around our office. My speciality is integrating applications that interface with SolidWorks, AutoCAD and various databases.
When I want to integrate with AutoCAD, I have to add a reference thru the Add Reference Dialog. I select COM then select AutoCAD 2000 Type Library. I go thru a simular step when I need to automate SolidWorks.
After I have completed and tested my application on my own computer I want to create an install package for distribution. The computers that I am using this on already have SolidWorks and AutoCAD installed. Do I need to include the reference files Interop.AutoCAD.dll and Interop.SldWorks.dll Won't their be an inheritant problem with the local machine having multiple copies of these .dll files
Second Problem: I am developing on a Windows 2K box with Visual Studio 2005. On several occasions, after creating the Installation File or Publishing to a Web Location, the installed application does not function on a Windows XP box. Can anyone point me in the correct direction for resolving this issue Do I need to compile my application on an XP box before distributing
Thanks
John P. Greiner
Interop, COM and Office Automation Question
Miah Helpmann
Hi!
You need this interop assemblies to make sure all will work. Just copy them with your app and no dll hell.
About 2000/XP problem - I don't think it's about created package, no matter which OS you are on - compiler produce same results. So the problem may be in used shared assemblies (different versions on different systems) or hard coded paths or may be something else.
What is the visual signs of not functioning application Is it started Did it throw exceptions What missing