Groups | Blog | Home
all groups > dotnet interop > may 2005 >

dotnet interop : Windows API .NET wrappers


Mitja Semolic
5/27/2005 12:00:00 AM
I always come down, to writing wrappers in managed code,
to access Windows API dlls, why there are not simply included
in the .NET framework, or any tool that would build you a wrapper
from a dll?

Rewriting data and methods definitions is a waste of time,
done by all most every programmer using .NET, is there no simpler way?

Mitja Semolic

Mattias Sjögren
5/27/2005 12:00:00 AM

[quoted text, click to view]

Standard (non COM) DLLs don't contain enough information about its
exported functions to make it possible to write such a tool.


[quoted text, click to view]

Visit http://www.pinvoke.net



Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Philip Nelson
5/27/2005 9:35:05 AM
I would argue that the goal is to replace the need for underlying windows
api calls with managed code. Truthfully, I've been writing .net code since
2000 and have less than 100 lines of api calls in my hundreds of thousands
of lines of code. The ones I have were written to access gnu ghostscript ;-)


[quoted text, click to view]

Jared Parsons [MSFT]
5/27/2005 11:12:52 AM
IMHO, the best way to do this type of operation is with MC++ or CLI\C++.
Since Whidbey Beta1, all of my wrappers at home are written in CLI\C++. For
me I can code them faster and more efficiently than I can in C#.

--
Jared Parsons [MSFT]
jaredpar@online.microsoft.com
http://blogs.msdn.com/jaredpar
"This posting is provided "AS IS" with no warranties, and confers no rights"
[quoted text, click to view]

Mitja Semolic
5/28/2005 12:00:00 AM
http://www.pinvoke.net

Yes, that was I looking for!

Thanks

AddThis Social Bookmark Button