>>When building a COM object one is not dealing directly with the WIN32 system but through COM+,COM1.5 subsystem. COM+,COM1.5 then deals with the WIN32 system directly...
>>
>>Is .NET currently just a very well made system that accesses/uses the COM+ OR COM1.5 subsystem?
>
>.NET will use COM+ for "remoting".
>
>>
>>From what I understand .NET does not directly access the WIN32 subsystem.... is this true?
>
>I'm not totally versed in .NET, but I think it would have to. Windows is all based in Win32.

the question *IS* does a `.NET built app` DIRECTLY access WIN32 libraries?
i do not believe it does... i believe it gets at WIN32 via COM1.5/COM+.
Thus, in effect .NET is a system built on top of COM.

>
>>
>>Is one of the goals of 'longhorn' to have the .NET managed code access the WIN32 system directly without requiring COM+,COM1.5 ?
>
>Nope. In Longhorn, WIN32 will be REPLACED with .NET managed code. WIN32 will then be legacy and in maintenance mode.

So .NET managed code IS Win32 of the future....
got it.


So I guess WIN32 stuff will work as DOS stuff works in windows applications....


Thanks.