Hi Nick!  Thanks for the info.

There is no reason I can't give it a strong name, I just have not yet and
was curious if I could skip that step.  Versioning my software is not a
concern - yet...

As a side note, I skipped the whole COM/.NET interop stuff and just have my
messaging port posting the xml to an ashx.  It works perfectly for my
situation and keeps everything I write .NET based without dealing with COM.

Mike


"Nick Malik" <nickmalik@hotmail.nospam.com> wrote in message
news:FJjEb.391403$Dw6.1243492@attbi_s02...
> Hi Mike,
>
> First off, I don't know if you can do what you ask.  Sorry.  I am creating
> C# AICs and Preprocessors, and have given every assembly a strong name all
> the way down the line.  You are correct in assuming that you have to place
a
> strong name on every component that your AIC calls.
>
> I'm just wondering, why can't you just give a strong name to the assembly
> you are referencing?  Is it code that you don't control?  I ask this
because
> nearly every commercial component that I'm aware of is strongly named.
> (That supports versioning, and other features that are important to
> commercial vendors).
>
> I know that it's a minor hassle to sign everything, but it's a hassle that
> you only pay once.  You are going through a much bigger hassle trying to
> work around it.
>
> I will take a look at the GAC issue later today and see if I can come up
> with any ideas.
>
> Good Luck,
> --- Nick Malik
>      Biztalk Bum
>
> "Mike Doerfler" <mikedoerfler@hotmail.com> wrote in message
> news:uhOzUALxDHA.1500@TK2MSFTNGP12.phx.gbl... 
> create 
have
> to 
> interface 
> going 
> For 
path 
GAC
> it 
don't 
MessagingManagerClient\bin 
them 
> keys 
> use 
> finish 
> component 
be 
>
>

[ Post a follow-up to this message ]