(Source: Have built a full SCSI interop layer in .Net to do low level CD ripping, full with native pointer walking and all. Have also written tools to walk the PEB (process environment block) in .Net w/ no native backends.)
(Source: Have built a full SCSI interop layer in .Net to do low level CD ripping, full with native pointer walking and all. Have also written tools to walk the PEB (process environment block) in .Net w/ no native backends.)
Also because this is Windows, there is https://github.com/microsoft/CsWin32 already (and adjacent libraries) which rely on the same generator.
It is still much easier than dealing with P/Invoke and COM from .NET code.
Create a nice wrapper, exposing C# compatible types and we're done.
In regards to COM, not even the CCW/RCW replacement is as developer friendly as VB 6 or Delphi.
I have some hopes that Secure Future Initiative will finally give the spotlight to .NET on Windows, that Windows team keeps pushing away, unlike what happens on Apple and Google platforms.
Now if doing cross platform code, C++/CLI is naturally not an option.