.NET to COM and back.

August 13, 2004 1:41 AM Comments [2] Posted in Programming

(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?
 

Comments [2]
« Great "Top Ten Tips for Web Services Int... | Home | Appled XML Developer's Conference 5 or "... »
Sunday, August 15, 2004 9:42:46 PM UTC
somewhat off toipic, but good to see you're using a Tablet PC!

I've had my Toshiba M205 for a few months now and think it's great. Just upgraded to 1G RAM, disabled the page file, and point IE temp files to a ramdisk. It's screamin fast now (for a Tablet PC!)
Shawn
Sunday, August 15, 2004 9:42:57 PM UTC
somewhat off topic, but good to see you're using a Tablet PC!

I've had my Toshiba M205 for a few months now and think it's great. Just upgraded to 1G RAM, disabled the page file, and point IE temp files to a ramdisk. It's screamin fast now (for a Tablet PC!)
Shawn
Comments are closed.
Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer’s view in any way.