Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / December 2005

Tip: Looking for answers? Try searching our database.

.Net Use in Visual Studio

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Greg - 22 Dec 2005 22:19 GMT
In VS2005, are the extensibility objects such as DTE2 based on .NET? I.e. are
they themselves .NET objects?

Thank You
Signature

Greg McPherran
www.McPherran.com

Carlos J. Quintero [VB MVP] - 23 Dec 2005 09:36 GMT
Hi Greg,

No, VS.NET extensibility is still COM-based although some COM stuff that
emerged to the surface previously (ActiveX registration of add-ins, ActiveX
shim control for toolwindows, etc.) is now removed in VS 2005 or well
hidden.

You have lots of resources to get you started with add-ins on a section of
my web site (below).

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio 2005, Visual Studio .NET,
VB6, VB5 and VBA
You can code, design and document much faster in VB.NET, C#, C++ or VJ#
Free resources for add-in developers:
http://www.mztools.com

> In VS2005, are the extensibility objects such as DTE2 based on .NET? I.e.
> are
> they themselves .NET objects?
>
> Thank You
Greg - 23 Dec 2005 17:48 GMT
Hello Carlos and thank you.

In what I've done with add-ins so far I haven't noticed any need to map COM
objects to .Net objects (i.e. unmanaged to managed), even though I have
written the add-in code in managed C++. Can you elaborate on this?

Signature

Greg McPherran
www.McPherran.com

> Hi Greg,
>
[quoted text clipped - 11 lines]
> >
> > Thank You
Carlos J. Quintero [VB MVP] - 26 Dec 2005 11:03 GMT
Hi Greg,

VS.NET is not a managed (.NET) app yet, so managed add-ins use Interop
assemblies internally. You don´t need to map anything, but the COM objects
are underlying there. In the past, despite programming a managed add-in (C#,
VB.NET) you had to register your add-in dll assembly for COM interop using
regasm.exe or equivalent, and you had to use an ActiveX shim control to host
.NET usercontrols in the toolwindows of your add-in. Despite this has been
eliminated, the .NET objects that you use in your managed assemblies are
wrappers around COM objects, and in fact you will see quite a few
COMExceptions from time to time.

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio 2005, Visual Studio .NET,
VB6, VB5 and VBA
You can code, design and document much faster in VB.NET, C#, C++ or VJ#
Free resources for add-in developers:
http://www.mztools.com

> Hello Carlos and thank you.
>
> In what I've done with add-ins so far I haven't noticed any need to map
> COM
> objects to .Net objects (i.e. unmanaged to managed), even though I have
> written the add-in code in managed C++. Can you elaborate on this?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
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.