Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Outlook / Programming Forms / May 2004

Tip: Looking for answers? Try searching our database.

.NET vs VB6 for COM Addin

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jack - 11 May 2004 21:51 GMT
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....
Sue Mosher [MVP-Outlook] - 11 May 2004 23:33 GMT
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.

Signature

Sue Mosher, Outlook MVP
Author of
    Microsoft Outlook Programming - Jumpstart for
    Administrators, Power Users, and Developers
    http://www.outlookcode.com/jumpstart.aspx

> 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....
Michael Tissington - 12 May 2004 00:48 GMT
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.

Signature

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

> 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....
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.