Re: Visual Studio 2005 is a memory hog!!
- From: "Mikhail Arkhipov (Microsoft)" <mikhaila@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 07 Nov 2005 20:45:34 -0800
On 11/7/05 4:57, in article OVRsHr54FHA.1188@xxxxxxxxxxxxxxxxxxxx, "Kevin
Spencer" <kevin@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>> It may be C++, but it is defintely COM. At least that's what the MSIL and
>> the system registry, as well as the COM mangager tell me.
>
> I'm so embarrassed. I realized that I violated my prime directive, by
> speaking about what I do not know.
>
> If I'm correct, Mikhail, those are both COM and .Net interfaces to the C++
> Visual Studio application, aren't they?
>
> I misspoke, and will now quietly flail myself.
:-)
Yes, in fact, both managed and native code are exposed as COM components
since main VS IDE is COM and hence expects all its components to be COM
objects. All native interfaces are available to managed code via VS primary
interop assemblies that cam be obtained from VSIP SDK.
Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights
.
- Follow-Ups:
- Re: Visual Studio 2005 is a memory hog!!
- From: Kevin Spencer
- Re: Visual Studio 2005 is a memory hog!!
- References:
- Re: Visual Studio 2005 is a memory hog!!
- From: Robert Conde
- Re: Visual Studio 2005 is a memory hog!!
- From: Kevin Spencer
- Re: Visual Studio 2005 is a memory hog!!
- From: Robert Conde
- Re: Visual Studio 2005 is a memory hog!!
- From: Mikhail Arkhipov (Microsoft)
- Re: Visual Studio 2005 is a memory hog!!
- From: Kevin Spencer
- Re: Visual Studio 2005 is a memory hog!!
- From: Kevin Spencer
- Re: Visual Studio 2005 is a memory hog!!
- Prev by Date: Re: Can you target 1.1 with Visual Studio 2005
- Next by Date: RE: MSVC++ Version 7.0
- Previous by thread: Re: Visual Studio 2005 is a memory hog!!
- Next by thread: Re: Visual Studio 2005 is a memory hog!!
- Index(es):
Relevant Pages
|