.NET BCLs and Windows API

Why doesnt the .NET Base Class libraries not contain all Windows API
comparable methods , kinda like MFC would wrap Win32 functions and add other
framework enhancements. Why must I always end up calling into the Windows
DLLs for those features? Will these be added to the BCLs at a later date?
For example I want to code up a message queue peeker and injector but that
requires calling into the DLLs, why isnt this functionality in the classes?
Thanks.

[Rob Tillie]

.. wrote:

Why doesnt the .NET Base Class libraries not contain all Windows API
comparable methods , kinda like MFC would wrap Win32 functions and
add other framework enhancements. Why must I always end up calling
into the Windows DLLs for those features? Will these be added to the
BCLs at a later date? For example I want to code up a message queue
peeker and injector but that requires calling into the DLLs, why isnt
this functionality in the classes?
Thanks.

Eventually every part will be covered, but it is a hell of a lot of work to
do that. That is why they first did the most important parts.
Btw: aren't the message queue operations provided in
System.EnterpriseServices?

Greetz,
-- Rob.

[Ulf Bietz]

> I want to code up a Message watcher and message injector for windows I

specify after i do an EnumWindow, kinda like spy++ but injecting messages
into the queue. For example, an automated test tool.

I'm afraid you still need to use the API calls for automated test functions.
As Rob said, eventually every part will be covered ... but it will take some
time.

Bye,

Ulf