jennyq
Tue Aug 12 13:31:49 CDT 2003
Hi, Faraz:
I am not clear about the detailed situation at your end. As far as I
know, there is issue regarding using the GAC dll in remoting.
The problem is you can't specify full name of your strongnamed dll in
client configure files(exception with message like some "XXX" is not allowed
in wellknown node" will be thrown out), and if you use partical name, the
client will get crashed with server stack trace information, telling
"FileNotFound".
The workaround for this is to put runtime assemblyBinding
configuration to inform the client assembly loader to actually load a
strongnamed assembly which matchs the partial name.
e.g:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<qualifyAssembly partialName="Hello" fullName= "Hello,
Culture=Neutral, PublicKeyToken=be17f7ab45496828, Version=0.0.0.0"/>
</assemblyBinding>
</runtime>
If it is the situation you have encountered, you can get more information
from
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&frame=right&th=8fa2742fc38bd87d&seekm=eb3mzNdhCHA.1864%40tkmsftngp11#link1
Qiu
"Faraz Rasheed" <frazrasheed@hotmail.com> wrote in message
news:0c6801c360cb$43fbaa20$a501280a@phx.gbl...
> I am having a problem when using a shared assembly with
> remoting.
>
> I have a shared assembly (shared.dll) added in the gloabal
> assembly cache. The remoting server application
> (server.exe) uses this shared.dll. I have added a
> reference of this assembly with set local property false.
> On client application (client.exe), i have also added the
> shared.dll assembly's reference.
>
> When i execute the server app (server.exe), it starts with
> no problem. When i start the client application, it gets
> crashed with the FileNotFoundException saying that it
> can't find the shared.dll assembly and shows the server
> assembly's path while the server continues to execute
> without any problem.
>
> I have managed to solve the problem by making the copy
> local property of shared.dll assembly's reference to true
> at server side. But, this is not what required... I want
> to use the shared assembly from its original location
> (global assembly cache).
>
> If someone can tell me what exactly is the problem, i
> would be grateful.
>
> Thanks,
> Faraz