It may well have, Tom.
Consider that when Visual Studio 6 was released, the current browser was
then IE v4 IIRC.
So I imagine there's lots of things the VS IDE may have taken advantage of
that have since been plugged.
However, you might also take a look at 909444, which is a 'fix' for some
complications that have occurred as a result of 902400. I don't expect that
particular issue is the case here (though it could be), but it does open the
door that your issue with the IDE might be 'fixable' by some access
permission modifications.
I will say this though.. .even thou VS6 is basically an 'abandoned' dev
suite, I doubt the dev community will sit very still if a sec update has
broken the debugger. There's still a TON of COM/COM+ code out there,
including a lot of it belonging to Microsoft, and I doubt that /all/ of it
is being developed/maintained in VS.NET -- so, if it's an endemic 'bug', I
suspect there will be a fix coming along shortly.
"Tom" <> wrote in message
news:CABD398C-1A81-4EE7-B5AB-...
> This only happens when I try to debug the dll using the VB6 IDE. It runs
> correctly outside of the debugger. So I guess the VB6 IDE exploited this
> particular security vulnerability.
>
> Tom
>
> "Lawrence Garvin [MVP]" wrote:
>
>>
>> Have you actually read KB902400? http://support.microsoft.com/kb/902400
>>
>> It refers to MS05-051
>> http://www.microsoft.com/technet/sec.../ms05-051.mspx
>> Microsoft Security Bulletin MS05-051
>> Vulnerabilities in MSDTC and COM+ Could Allow Remote Code Execution
>> (902400)
>> This patch plugs some holes in the COM+ subsystem. Perhaps your code took
>> advantage of that hole that has now been plugged?
>>
>>
>> "Tom" <> wrote in message
>> news:C1D8DB4F-420E-4841-83DB-...
>> > When I install KB902400 on XP SP2 I can no longer debug VB6 COM+
>> > applications
>> > with the IDE. The COM+ DLL that I'm debugging is called from another
>> > COM+
>> > component. The calling COM+ component returns the error "Method '~' of
>> > object
>> > '~' failed". If I uninstall the 902400 update I can debug the COM+
>> > component
>> > correctly. Has anyone else had this problem with 902400 and if so how
>> > did
>> > you
>> > resolve it?
>>
>>
>>