I thought somebody else had already answered it - those .Net components on windows _are implemented_ by wrapping around advapi32.dll, etc. Many .Net methods have their equivalent to Win32 APIs, because they are thin-wrappers around, and implemented (on windows) using, the Win32 APIs.
It would be a bad idea to implement advapi32.dll using c<->c#<->c to native mono, which you seems to be suggesting.
-------------------------------------------- On Sat, 9/11/13, Akira Nakagawa matyapiro31@gmail.com wrote:
Subject: using mono dll components on wine(C#) To: "wine-devel" wine-devel@winehq.org Date: Saturday, 9 November, 2013, 12:39
I do not know how to use COM classes on wine lib,for example , System.dll
wine dlls should be written by C,but I found many .Net methods equivalent to Win32 APIs.You can implement methods easily.
(for example, ClearEventLog
() in advapi32.dll by Eventlog.Clear() in System.Diagnostics)
Isn't this good idea?