Windows API Wrapper for .Net?

Question

Windows API

---

So, I know that WinForms is a bit concerned with the Windows API, but frankly, this is terrible. ESPECIALLY with laminated windows and flicker. So I was wondering if anyone had written partial or full wrappers for the Windows API. I'm particularly interested in the Layered Window aspect, but in fact, any part of the API is a good place to start.

Update . I found the Windows API code code here: http://code.msdn.microsoft.com/WindowsAPICodePack , but it doesn't seem to wrap Layered Windows? Am I accepting this right?

Embedded API (Windows)

---

Ive learned a little about the Native API, but I'm not quite sure what it is for? What features does it provide? would it be nice to peek?

Summary (questions in a nutshell)

---

• Does anyone know about the existing (partial or full) shell of the Windows API?
  • If the answer is not one, where will there be a good resource to learn about it yourself, and perhaps write your own?
• An explanation of the native API? What does it do? Can I use it to improve applications? Can I even use it at all?

The answer to any of them is highly appreciated :) thanks

Answer 1

LayeredWindows really works better on WinForms than on Windows. Built-in window controls do not even support the alpha channel for WinForms analogues, so native windows flicker and require a lot of subclass to redefine the picture to use alpha-compatible routines.

WPF. windows , (WS_EX_COMPOSITED), , , , , , .

WPF "" Windows, () . , .

Answer 2

PInvoke.NET.

Answer 3

The Windows API is huge. It has a lot of tons. Windows Forms is a wrapper of its parts. WPF is a wrapper of its parts. Parts of the base class libraries (for example, System.IO. *) Are wrappers of its parts. The Code Pack is a wrapper specifically designed for new products in Vista and Windows 7, not in Windows Forms or WPF.

Have you looked in WPF? Combined with P / Invoke for specific API functions, you may need a long way to go where you want to be.