The Artima Developer Community
Sponsored Link

.NET Buzz Forum
.NET to COM and back.

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Scott Hanselman

Posts: 1031
Nickname: glucopilot
Registered: Aug, 2003

Scott Hanselman is the Chief Architect at Corillian Corporation and the Microsoft RD for Oregon.
.NET to COM and back. Posted: Aug 12, 2004 11:23 PM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Scott Hanselman.
Original Post: .NET to COM and back.
Feed Title: Scott Hanselman's ComputerZen.com
Feed URL: http://radio-weblogs.com/0106747/rss.xml
Feed Description: Scott Hanselman's ComputerZen.com is a .NET/WebServices/XML Weblog. I offer details of obscurities (internals of ASP.NET, WebServices, XML, etc) and best practices from real world scenarios.
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Scott Hanselman
Latest Posts From Scott Hanselman's ComputerZen.com

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

 

 

Read: .NET to COM and back.

Topic: The Problem and A Solution Previous Topic   Next Topic Topic: Capturing Tacit Knowledge

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use