1

I see DllImport everywhere. I see everybody declaring Win API methods in their projects. Why doesn't people put every Win API method declaration in a .NET library and use it instead? Is there any such library? Is it open source?

2
  • 1
    Some of the Windows 7 APIs have made it into .NET 4, readily available to WPF developers. Commented Feb 28, 2011 at 19:35
  • I'm building a library like this as we speak...It's a long job! Commented Oct 10, 2012 at 10:59

2 Answers 2

5

Because this would be a huge library, and no one needs to call all of the Win API methods.

The closest thing that I know of is pinvoke.net.

Many specific APIs have .NET wrappers, if you look around (ESENT, IIS management, SQL management and more).

Sign up to request clarification or add additional context in comments.

2 Comments

See also the PInvoke Signature Generator tool: stackoverflow.com/questions/5122410/…
NET is a huge library. I doubt it would increase much in size if it included those wrappers.
4

The WindowsAPICodePack comes close for many things.

1 Comment

+1 Although specifically that's many of the new Windows 7/Vista features.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.