|
Home > Archive > BizTalk Server Orchestration > March 2004 > BT2004 + Strong Naming problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BT2004 + Strong Naming problem
|
|
|
| Can BT2004 use assemblies that are NOT strongly named?
I have a need to use a pre-existing .NET library that is
not strongly named from within an Orchestration. If I
strong name my BizTalk assembly, I get the expected build
error. If I don't strong name my BizTalk assembly, I can
build and even deploy the project (by using the BizTalk
Deployment Wizard and clearing the "install to GAC"
checkbox) but get the following error when trying to
enlist the Orchestration:
Could not enlist
orchestration 'Hello_World.Generate_Greeting,Hello Word,
Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null'.Exception from HRESULT: 0x80131044.
And if the answer is "No", has anyone had to deal with the
deployment implications of converting a non-strongly named
class library to a strongly named one.
| |
| Tomas Restrepo \(MVP\) 2004-03-24, 9:35 pm |
| Hi John,
> Can BT2004 use assemblies that are NOT strongly named?
They need to be deployed to the GAC, and the strong name on Biztalk
assemblies are use for artifact versioning, so I'd guess the answer is no.
> I have a need to use a pre-existing .NET library that is
> not strongly named from within an Orchestration. If I
> strong name my BizTalk assembly, I get the expected build
> error. If I don't strong name my BizTalk assembly, I can
> build and even deploy the project (by using the BizTalk
> Deployment Wizard and clearing the "install to GAC"
> checkbox) but get the following error when trying to
> enlist the Orchestration:
>
> Could not enlist
> orchestration 'Hello_World.Generate_Greeting,Hello Word,
> Version=1.0.0.0, Culture=neutral,
> PublicKeyToken=null'.Exception from HRESULT: 0x80131044.
>
> And if the answer is "No", has anyone had to deal with the
> deployment implications of converting a non-strongly named
> class library to a strongly named one.
Well, normally, recompiling it should be enough, if you own the code, but it
will mean the assembly identity will change, naturally. So if you expect
that same assembly to be used from other clients, you'll need to recompile
them against the new version, too.
--
Tomas Restrepo
tomasr@mvps.org
|
|
|
|
|