| Groups | Blog | Home |
dotnet clr : Assembly.LoadFrom problems called from WindowsService
in, and what is the location of the assembly you are loading using LoadFrom? If the assembly is not located in the same directory, or a subdirectory below the appbase, then the runtime cannot automatically resolve the reference. You can subscribe to the appdomain's AssemblyResolve event to manually locate dependencies for the runtime. [quoted text, click to view] "Chris Lewis" <chrislewis@hasnoemail.com> wrote in message news:41816035$0$87823$65c69314@mercury.nildram.net... > Hi, > > I have a Windows Service that processes MSMQ messages and dynamically > instantiates 'Message Processor' components according to the message type. > > I use the Assembly.LoadFrom(<assembly path>) call to load the appropriate > assembly from its path. All works fine as far as the assembly itself goes, > but I get the FileNotFoundException for any dependencies. I know that > LoadFrom should add the path of the dynamically loaded assembly to the > list > of paths searched for dependencies - but it's not happening for me. If I > drop the required assemblies into the Windows Service .exe directory all > is > fine (even though the dynamic assembly itself is not there). > > Please help - is there something different about Windows Services that > means > that this mechanism doesn't work? > > Thanks, in anticipation. > > Chris Lewis > >
Hi,
I have a Windows Service that processes MSMQ messages and dynamically instantiates 'Message Processor' components according to the message type. I use the Assembly.LoadFrom(<assembly path>) call to load the appropriate assembly from its path. All works fine as far as the assembly itself goes, but I get the FileNotFoundException for any dependencies. I know that LoadFrom should add the path of the dynamically loaded assembly to the list of paths searched for dependencies - but it's not happening for me. If I drop the required assemblies into the Windows Service .exe directory all is fine (even though the dynamic assembly itself is not there). Please help - is there something different about Windows Services that means that this mechanism doesn't work? Thanks, in anticipation. Chris Lewis
That will work if the assembly is located in a subdirectory below the
application base directory. Also, that must be specified as a relative path , not an absolute path, and it is relative to the application base directory. [quoted text, click to view] "Henning Krause [MVP]" <newsgroup.no@spam.infinitec.de> wrote in message news:Ork$NpXvEHA.3908@TK2MSFTNGP12.phx.gbl... > Hello, > > Try to add the path via AppDomain.CurrentDomain.AppendPrivatePath().. that > should help. > > Greetings, > Henning Krause [MVP] > ========================== > Visit my website: http://www.infinitec.de > Try my free Exchange Explorer: Mistaya > (http://www.infinitec.de/?page=products) > > > "Chris Lewis" <chrislewis@hasnoemail.com> wrote in message > news:41816035$0$87823$65c69314@mercury.nildram.net... >> Hi, >> >> I have a Windows Service that processes MSMQ messages and dynamically >> instantiates 'Message Processor' components according to the message >> type. >> >> I use the Assembly.LoadFrom(<assembly path>) call to load the appropriate >> assembly from its path. All works fine as far as the assembly itself >> goes, >> but I get the FileNotFoundException for any dependencies. I know that >> LoadFrom should add the path of the dynamically loaded assembly to the > list >> of paths searched for dependencies - but it's not happening for me. If I >> drop the required assemblies into the Windows Service .exe directory all > is >> fine (even though the dynamic assembly itself is not there). >> >> Please help - is there something different about Windows Services that > means >> that this mechanism doesn't work? >> >> Thanks, in anticipation. >> >> Chris Lewis >> >> > >
Hello,
Try to add the path via AppDomain.CurrentDomain.AppendPrivatePath().. that should help. Greetings, Henning Krause [MVP] ========================== Visit my website: http://www.infinitec.de Try my free Exchange Explorer: Mistaya (http://www.infinitec.de/?page=products) [quoted text, click to view] "Chris Lewis" <chrislewis@hasnoemail.com> wrote in message news:41816035$0$87823$65c69314@mercury.nildram.net... > Hi, > > I have a Windows Service that processes MSMQ messages and dynamically > instantiates 'Message Processor' components according to the message type. > > I use the Assembly.LoadFrom(<assembly path>) call to load the appropriate > assembly from its path. All works fine as far as the assembly itself goes, > but I get the FileNotFoundException for any dependencies. I know that > LoadFrom should add the path of the dynamically loaded assembly to the list > of paths searched for dependencies - but it's not happening for me. If I > drop the required assemblies into the Windows Service .exe directory all is > fine (even though the dynamic assembly itself is not there). > > Please help - is there something different about Windows Services that means > that this mechanism doesn't work? > > Thanks, in anticipation. > > Chris Lewis > >
Hi Henning,
I had already tried this - and I tried it again after your post, but to no avail - I get the same error? Chris [quoted text, click to view] "Henning Krause [MVP]" <newsgroup.no@spam.infinitec.de> wrote in message news:Ork$NpXvEHA.3908@TK2MSFTNGP12.phx.gbl... > Hello, > > Try to add the path via AppDomain.CurrentDomain.AppendPrivatePath().. that > should help. > > Greetings, > Henning Krause [MVP] > ========================== > Visit my website: http://www.infinitec.de > Try my free Exchange Explorer: Mistaya > (http://www.infinitec.de/?page=products) > > > "Chris Lewis" <chrislewis@hasnoemail.com> wrote in message > news:41816035$0$87823$65c69314@mercury.nildram.net... > > Hi, > > > > I have a Windows Service that processes MSMQ messages and dynamically > > instantiates 'Message Processor' components according to the message type. > > > > I use the Assembly.LoadFrom(<assembly path>) call to load the appropriate > > assembly from its path. All works fine as far as the assembly itself goes, > > but I get the FileNotFoundException for any dependencies. I know that > > LoadFrom should add the path of the dynamically loaded assembly to the > list > > of paths searched for dependencies - but it's not happening for me. If I > > drop the required assemblies into the Windows Service .exe directory all > is > > fine (even though the dynamic assembly itself is not there). > > > > Please help - is there something different about Windows Services that > means > > that this mechanism doesn't work? > > > > Thanks, in anticipation. > > > > Chris Lewis > > > > > >
Thanks a lot David, this worked for me!
Chris [quoted text, click to view] "David Levine" <noSpamdlevineNNTP2@wi.rr.com> wrote in message news:esoAqcTvEHA.3416@TK2MSFTNGP09.phx.gbl... > What is the appdomain's base directory that the window service is running > in, and what is the location of the assembly you are loading using LoadFrom? > If the assembly is not located in the same directory, or a subdirectory > below the appbase, then the runtime cannot automatically resolve the > reference. > > You can subscribe to the appdomain's AssemblyResolve event to manually > locate dependencies for the runtime. > > "Chris Lewis" <chrislewis@hasnoemail.com> wrote in message > news:41816035$0$87823$65c69314@mercury.nildram.net... > > Hi, > > > > I have a Windows Service that processes MSMQ messages and dynamically > > instantiates 'Message Processor' components according to the message type. > > > > I use the Assembly.LoadFrom(<assembly path>) call to load the appropriate > > assembly from its path. All works fine as far as the assembly itself goes, > > but I get the FileNotFoundException for any dependencies. I know that > > LoadFrom should add the path of the dynamically loaded assembly to the > > list > > of paths searched for dependencies - but it's not happening for me. If I > > drop the required assemblies into the Windows Service .exe directory all > > is > > fine (even though the dynamic assembly itself is not there). > > > > Please help - is there something different about Windows Services that > > means > > that this mechanism doesn't work? > > > > Thanks, in anticipation. > > > > Chris Lewis > > > > > >
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 |