A while back I posted some thoughts on Win32 signatures… The CLR interop team has been hard at work figuring out the right solution, expect to see more soon.  In the mean time check out these PInvoke signatures the C# team posttest a while back.  Looks like they address at least part of the issue. 

 

http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=f1dd70e4-c212-4a6f-bff7-c82e34c8836f.