Bob Milani
Posts: 13
Joined: 2005-01-28
|
Sergey,
It's been almost 3 weeks since you said you'll help "ASAP", and I still haven't got anything from you regarding this problem.
I really think you should have a better support, this is absolutely not acceptable.
--Bob |
|
Sergey Grischenko
Add-in Express team
Posts: 7235
Joined: 2004-07-05
|
Hi Bob.
In fact we are on vacation now. But I still work on ADX for VS2005.
I will let you know when I finish the work. |
|
Bob Milani
Posts: 13
Joined: 2005-01-28
|
Sergey,
The problem is not just making ADX work on VS2005. My biggest problem is I can't even use it in VS2003, when I have VS2005 installed on my machine.
I don't want to port my old code to VS2005, but I'm working on another application using VS2005. I even re-installed VS2003 after I installed VS2005, but it's not working.
My problem is not supporting VS2005, is supporting VS2003!
Thanks,
--Bob |
|
Sergey Grischenko
Add-in Express team
Posts: 7235
Joined: 2004-07-05
|
Hi Bob.
At the moment I have only one solution for you. I mean the way that we use to support different versions of Microsoft Office. Usually we have one version of Office installed on our PCs (as you probably know, you can install different versions of MS Office on the same PC but it doesn't work properly). It is MS Office 2003. To test ADX under Office 2000 or XP we use "Virtual PC" from Microsoft. Thus we have two additional operating systems - one for Office 2000 and one for Office XP.
You can use the same approach. To support different versions of your applications you could install VS2003 in VPC.
As for another solution, if I will not able to solve the issue myself then I will ask about it Microsoft. |
|