| Deepak 2005-01-26, 5:54 pm |
| Hi,
I'm not sure whether it's Bug. I think you might have a
problem with your design.
The Best approach I have seen so far with Biztalk 2004 is
to separate your assemblies based on the usage.
Since Pipeline Components need not be placed in the GAC
and it's enough if it's copied to the pipeline folder,
doing so might help you in avoiding your current
situation.
Deepak
http://deepakl.blogspot.com
>-----Original Message-----
>Hello guys,
>
>I'm facing following problem. I have assembly that
contains pipeline
>components and some classes which are used from
orchestration.
>
>I deploy this assembly to GAC and copy to
the ...Microsoft BizTalk
>2004\PipelineComponents folder. Both GAC and
PipeLineComponents folder
>contain always the same version of assembly (including
public key token).
>
>At runtime I'm experiencing following symptoms:
>1) BizTalk 2004 loads the asssembly into app domain
twice - once from GAC
>and once from PipeLineComponents folder.
>2) When creating instances of objects residing in the
assembly using
>reflection or other reflection-relation operations (such
as
>deserialization), instances belong to only one of loaded
assemblies -
>therefore typecast is not working.
>
> I check the assembly by using obj.GetType().Assembly
property on an object
>created using reflection (for example
Activator.CreateInstance). It ussually
>refers to assembly from PipelineComponents folder. If I
however create the
>instance using "new" construct, object refers to
assembly loaded from GAC.
>
>This bug is causing the typecast to fail, although the
type names and
>namespaces are correct.
>
>I'm experiencing this problem on several
projects/computers/setups, so this
>is not a local anomaly. Anyone solved this issue yet?
>
>Thanks
>
>Tomas
>
>
>.
>
|