.NET to COM and back.
(This is being written on a TabletPC with newly installed SP2 in a Quiznos in downtown Olympia using God knows whose WiFi connection.)
I'm sure we all know that you can't COM-interop to a COM object that's really a .NET COM Callable Wrapper, the question is why not? (Personally I think the answer is "Why would you want too, and how would you have expected it to behave?) However, the PTB aren't buying that answer. Yes, I know it's stupid, but why is it not supported?