F
Faraz Rasheed
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
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