[Announce] diagnosing interop marshaling

[Stephane Rodriguez]

Someone who wrote a book[^] about .NET interop has released a free tool[^] to monitor type marshaling inside the CLR. It takes advantage of .NET 1.1. It works on all machines, although Windows XP is required to show the balloon tooltips.

[David Stone]

Clicking on the second link gives you a "Server error in / application."

---

Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing

[Kant]

The tool link works for me. For others if you don't know about Adam Nathan, he is CLR Test Lead. Don't :beer: and drive.

[David Stone]

Kant wrote: For others if you don't know about Adam Nathan, he is CLR Test Lead. And a freaking god when it comes to Interop.

---

Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing

[Kant]

I bet he is Stephane's guru. ;) Don't :beer: and drive.

[Stephane Rodriguez]

eh... who knows ;)

[Richard Deeming]

Don't forget to read his blog[^] as well. Apparently, the new Application.EnableVisualStyles() method has a marshalling bug in it. :rolleyes:

---

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

[Stephane Rodriguez]

I am subscribed to it since day one. But quite honestly, I think I am gonna quit it altogether as I tend to think that as a "customer" I don't have to learn the intrinsics of an engine whose implementation is going to change anyway. For any current problem, the work around is to write a dll and use a P/Invoke native call to bypass the CLR itself. It only takes an F-grade know-how to do so. I swallow a small raisin, leaving away all this crap.