> Better still would be a Win32 namespace that actually encapsulated
> the whole API in a managed way.
Yes, yes yes!!!
I guess the chances are between zero and none :-)

Signature
Jeff Gaines Damerham Hampshire UK
> Better still would be a Win32 namespace that actually encapsulated the
> whole API in a managed way.
I do not know if it would be better, since I still would not get the benefit
of knowing how Windows messages translate into .NET events. It would be
helpful so that one would not have to #include <windows.h> in VC++, use IJW,
and create mixed mode assemblies that way with their current destructive
bugginess, and of course it would be better for all languages not to have to
use InterOp just to drop to the Windows API level. But if MS documented the
messages -> .NET events better, I might not have to ever go the Win32 API
route anymore in the first place.
>> Microsoft has put out a document relating Win32 API calls to .NET
>> methods
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/h
>> tml/win32map.asp ) . An equally valuable document, esspecially from
>> the component developer point of view, would map Windows messages to
[quoted text clipped - 12 lines]
>> Am I the only .NET developer who feels a need for such a document
>> from Microsoft to aid in porting Win32 functionality to .NET ?