PC Review


Reply
Thread Tools Rate Thread

COMAdmin needs strong name?!

 
 
nostradamnit
Guest
Posts: n/a
 
      23rd Jan 2004
A colleague has a Web Service project that uses a Queued Component. In
the global.asax, we are trying to add code that will start the COM+
Application in the Application_OnStart method. When we compile, we get
the following message:

Unable to emit assembly: Referenced assembly 'InterOp.COMAdmin' does
not have a strong name

I was able to take the same code and compile it into a console app
without it complaining about the strong name... Has anyone run into
this issue, and if so, how do I overcome it?

Another solution to this problem would be if there is another way to
access the COM+ Admin Catalog without referencing the InterOp.COMAdmin
object. Does System.EnterpriseServices expose the Catalog? I didn't
see a way to reference it.

Thanks,
Sam
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Strong Name Key spaulsamin@yahoo.co.in Microsoft VB .NET 3 5th Mar 2007 07:46 AM
COMAdmin.ICOMAdminCatalog2 failed =?Utf-8?B?TGkgUGFuZw==?= Microsoft VB .NET 1 5th Nov 2004 10:37 AM
Re: Strong Naming a Non-Strong Named assembly Joyjit Mukherjee Microsoft Dot NET Framework 0 24th Aug 2004 02:17 PM
strong naming an assembly that has non-strong named references? SStory Microsoft VB .NET 2 10th Jun 2004 06:41 PM
Error with COM + 1.0 Admin Type Library (COMAdmin) interop on Win2K. 2003 works. Grant Microsoft Dot NET 0 26th Sep 2003 06:20 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 02:20 PM.