| Groups | Blog | Home |
dotnet distributed apps : Assembly or dependency not found using Remoting.
I have this particular problem. I am using .NET Remoting. My server (an
EXE) listening on a port has a reference (a dll) that is registered in the GAC. While trying to access a class in this reference (DLL) via my client, I receive a remoting error stating that it cannot find the referenced dll. unregistering my dll from the GAC and putting this one in the same directory than my EXE causes no problem. Everything works fine. What seems to be the
How do you reference your assembly? When you make a dynamic reference to an
assembly by providing the calling method only with partial information about assembly (e.g. only assembly name) then in this case only application directory is searched for the assembly. You have to provide full reference or call LoadWithPartialName method. Adam "Luc" <Luc@discussions.microsoft.com> schrieb im Newsbeitrag news:060556DB-7CB5-4177-BE36-4C25C9D7222F@microsoft.com... [quoted text, click to view] > I have this particular problem. I am using .NET Remoting. My server (an > EXE) listening on a port has a reference (a dll) that is registered in the > GAC. > > While trying to access a class in this reference (DLL) via my client, I > receive a remoting error stating that it cannot find the referenced dll. > unregistering my dll from the GAC and putting this one in the same directory > than my EXE causes no problem. Everything works fine. What seems to be the > problem?
Thank's for your reply,
Actually I am referencing it directly in the solution explorer. The path I am using to reference it is the codebase path (ex: d:\apps\dgag\infr). But when in the GAC, the assembly goes in the C:\Winnt\Assemblies subdirectory. I am then calling the functions just by invoking the method in the proxy (client side) which in turn is calling the real object on the server side using remoting. Then BANG. How should I make this reference when compiling my service on the server side to avoid this behavior? [quoted text, click to view] "Adam Boczek" wrote:
> How do you reference your assembly? When you make a dynamic reference to an > assembly by providing the calling method only with partial information about > assembly (e.g. only assembly name) then in this case only application > directory is searched for the assembly. You have to provide full reference > or call LoadWithPartialName method. > > Adam > > > "Luc" <Luc@discussions.microsoft.com> schrieb im Newsbeitrag > news:060556DB-7CB5-4177-BE36-4C25C9D7222F@microsoft.com... > > I have this particular problem. I am using .NET Remoting. My server (an > > EXE) listening on a port has a reference (a dll) that is registered in the > > GAC. > > > > While trying to access a class in this reference (DLL) via my client, I > > receive a remoting error stating that it cannot find the referenced dll. > > unregistering my dll from the GAC and putting this one in the same > directory > > than my EXE causes no problem. Everything works fine. What seems to be > the > > problem? > >
Thank's for answering Ice. But the GAC problem reside on the server side.
When both my service and the dll are residing in the same directory, I have no problem. Putting away my dll in another directory and registering it in the GAC causes this message. are you saying that the qualifyAssembly element can correct the problem? [quoted text, click to view] "Ice" wrote:
> the remoting infrastructure on the client doesn't look in the GAC. to use > the GAC you have to the qualify the assembly. look at the qualifyAssembly > element. > "Luc" <Luc@discussions.microsoft.com> wrote in message > news:060556DB-7CB5-4177-BE36-4C25C9D7222F@microsoft.com... > > I have this particular problem. I am using .NET Remoting. My server (an > > EXE) listening on a port has a reference (a dll) that is registered in the > > GAC. > > > > While trying to access a class in this reference (DLL) via my client, I > > receive a remoting error stating that it cannot find the referenced dll. > > unregistering my dll from the GAC and putting this one in the same > directory > > than my EXE causes no problem. Everything works fine. What seems to be > the > > problem? > >
I read a bit more about the qualifyAssembly element and it's impact on my
problem. I think it will work but I still have this question before using this method: Before going to the GAC, this assembly was in the local directory of my EXE. When I compiled my EXE, I assume the information about this assembly went in the manifest of my EXE with only partial name information. It's only then I decided to put my assembly in the GAC giving it a strong name. Is it because I didn't recompiled my EXE while my dll was in the GAC that the problem occured? Is the full name information of my assembly stored in the manifest of my EXE because it's now in the GAC and it can find it more easily? And finally, which method is invoked in the EXE to load my assembly when a) my EXE is built while my assembly is referneced in the same directory with no strong name? b) my EXE is built while my assembly is referenced in the GAC? Is it the same method but the manifest gives partial or full name information? Thank's for the info. [quoted text, click to view] "Ice" wrote:
> the remoting infrastructure on the client doesn't look in the GAC. to use > the GAC you have to the qualify the assembly. look at the qualifyAssembly > element. > "Luc" <Luc@discussions.microsoft.com> wrote in message > news:060556DB-7CB5-4177-BE36-4C25C9D7222F@microsoft.com... > > I have this particular problem. I am using .NET Remoting. My server (an > > EXE) listening on a port has a reference (a dll) that is registered in the > > GAC. > > > > While trying to access a class in this reference (DLL) via my client, I > > receive a remoting error stating that it cannot find the referenced dll. > > unregistering my dll from the GAC and putting this one in the same > directory > > than my EXE causes no problem. Everything works fine. What seems to be > the > > problem? > >
the remoting infrastructure on the client doesn't look in the GAC. to use
the GAC you have to the qualify the assembly. look at the qualifyAssembly element. [quoted text, click to view] "Luc" <Luc@discussions.microsoft.com> wrote in message news:060556DB-7CB5-4177-BE36-4C25C9D7222F@microsoft.com... > I have this particular problem. I am using .NET Remoting. My server (an > EXE) listening on a port has a reference (a dll) that is registered in the > GAC. > > While trying to access a class in this reference (DLL) via my client, I > receive a remoting error stating that it cannot find the referenced dll. > unregistering my dll from the GAC and putting this one in the same directory > than my EXE causes no problem. Everything works fine. What seems to be the > problem?
You never really reference assemblies in the GAC. I guess you should try
compiling your assembly against the strong-named version of your assembly. I've never tried that scenario explicitly. [quoted text, click to view] "Luc" <Luc@discussions.microsoft.com> wrote in message news:E3FDBB18-14EF-40A1-AE46-CAA4C03EFB29@microsoft.com... > I read a bit more about the qualifyAssembly element and it's impact on my > problem. I think it will work but I still have this question before using > this method: > > Before going to the GAC, this assembly was in the local directory of my EXE. > When I compiled my EXE, I assume the information about this assembly went in > the manifest of my EXE with only partial name information. It's only then I > decided to put my assembly in the GAC giving it a strong name. > > Is it because I didn't recompiled my EXE while my dll was in the GAC that > the problem occured? Is the full name information of my assembly stored in > the manifest of my EXE because it's now in the GAC and it can find it more > easily? > > And finally, which method is invoked in the EXE to load my assembly when > a) my EXE is built while my assembly is referneced in the same directory > with no strong name? > b) my EXE is built while my assembly is referenced in the GAC? > > Is it the same method but the manifest gives partial or full name information? > > Thank's for the info. > > "Ice" wrote: > > > the remoting infrastructure on the client doesn't look in the GAC. to use > > the GAC you have to the qualify the assembly. look at the qualifyAssembly > > element. > > "Luc" <Luc@discussions.microsoft.com> wrote in message > > news:060556DB-7CB5-4177-BE36-4C25C9D7222F@microsoft.com... > > > I have this particular problem. I am using .NET Remoting. My server (an > > > EXE) listening on a port has a reference (a dll) that is registered in the > > > GAC. > > > > > > While trying to access a class in this reference (DLL) via my client, I > > > receive a remoting error stating that it cannot find the referenced dll. > > > unregistering my dll from the GAC and putting this one in the same > > directory > > > than my EXE causes no problem. Everything works fine. What seems to be > > the > > > problem? > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |