VS2003 to VS2005 porting

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Boni - 01 Feb 2006 13:55 GMT

Dear all,
is there any special article somewhere about VSIP/addin porting issues?
I hoped to find some on Carlos page :), but it is not there. Can I conclude
from that that there is no problems with porting? :)
With best wishes,
Boni

Reply to this Message

Carlos J. Quintero [VB MVP] - 01 Feb 2006 17:04 GMT

Hi Boni,

I didn´t find the time to write such article. From my experience, porting to
get something that compiles is easy, a change in the commandbars, some new
assemblies and so on. The burden is testing the new build in the new IDE
because some implementations have changes, VS 2005 introduces new bugs and
so on. If you are creating a VB.NET and C# you can post in the yahoo forum
(http://groups.yahoo.com/group/vsnetaddin/) since I live there (I get posts
in my e-mail inbox) but there are people working on C++ add-ins too.

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com

> Dear all,
> is there any special article somewhere about VSIP/addin porting issues?
> I hoped to find some on Carlos page :), but it is not there. Can I
> conclude from that that there is no problems with porting? :)
> With best wishes,
> Boni

Reply to this Message

VS2003 to VS2005 porting

Free Magazines