Microsoft's "Dies Patchae" Break .NET/COM interoperability.

[INGSOC]

Check out the Microsoft support groups post this weekend.

The weekend of "patches".

They seem to have broken COM/.net interop on W2K.

..Net apps calling any COM component are met with nasty, unresolvable
"security" errors that can't be fixed with dcomcfg or the .Net
configuration manager.

Pure .Net apps work just fine, of course...but there's a whole lot of hand
wringing going on...

--
Texeme
http://texeme.com

[Elidel]

Opps, this was a product of trying to install remote debugging.

The Component Services/My Computer security was set from Identify to
Anonymous.

Once set back, all the COM components started working.

Man, that was a hard one to trace back though...thank god for a great
little article on COM configuration:

http://consumer.installshield.com/kb.asp?id=Q108324
INGSOC wrote:

Check out the Microsoft support groups post this weekend.

The weekend of "patches".

They seem to have broken COM/.net interop on W2K.

.Net apps calling any COM component are met with nasty, unresolvable
"security" errors that can't be fixed with dcomcfg or the .Net
configuration manager.

Pure .Net apps work just fine, of course...but there's a whole lot of hand
wringing going on...