.NET vs VB6 for COM Addin

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am looking for info on the benefits (or drawbacks) of developing a COM Add-in in VB.NET vs. VB6. I currently have many thousands of lines of VB6 code in an existing Addin that I am (eventually) going to port to VB.NET, but now an starting a new Add-in and want to know if it is worth the hassle maintain two dev environments to develop this one in .NET

Comments....
 
I can't think of any reason to port an existing COM add-in to .NET. I'd
stick with VB6 since you already have a substantial investment there.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



jack said:
I am looking for info on the benefits (or drawbacks) of developing a COM
Click to expand...
Add-in in VB.NET vs. VB6. I currently have many thousands of lines of VB6
code in an existing Addin that I am (eventually) going to port to VB.NET,
but now an starting a new Add-in and want to know if it is worth the hassle
maintain two dev environments to develop this one in .NET.
 
Not strictly a COM Add-in but in VB6 you can create ActiveX controls which
can you use on an Outlook form.

The controls you create in .NET can NOT be hosted on an Outlook form.

--
Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com


jack said:
I am looking for info on the benefits (or drawbacks) of developing a COM
Click to expand...
Add-in in VB.NET vs. VB6. I currently have many thousands of lines of VB6
code in an existing Addin that I am (eventually) going to port to VB.NET,
but now an starting a new Add-in and want to know if it is worth the hassle
maintain two dev environments to develop this one in .NET.
 
Back
Top