|
|
You're in the
dotnet clr
group:AppDomain PrivatePath under .NET 2.0 Beta 2
dotnet clr:
I would like to add to the search path of my application a directory where
some plug-ins reside. But this directory is not under the application base directory. I tried many procedures, but nothing works. By the way, these things are quite badly documented in Beta 2. The problem is that the runtime claims it won't take into a account a private path that is not under the application base path. I overcame the probleme by overloading AppDomain.AssemblyResolve, but this solution is quite dirty. Was someone successful with another solution? -- Gael Fraiteur http://gael.fraiteur.net Prague, Czech Republic ---------------------------------------------------------------- PostSharp is an open-source post-compiler for .NET http://gael.fraiteur.net/postsharp.aspx ----------------------------------------------------------------
Please post Beta questions to the beta forums at http://forums.microsoft.com
Willy. [quoted text, click to view] "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message news:eHoo2bDlFHA.320@TK2MSFTNGP09.phx.gbl... >I would like to add to the search path of my application a directory where > some plug-ins reside. But this directory is not under the application base > directory. I tried many procedures, but nothing works. By the way, these > things are quite badly documented in Beta 2. > > The problem is that the runtime claims it won't take into a account a > private path that is not under the application base path. I overcame the > probleme by overloading AppDomain.AssemblyResolve, but this solution is > quite dirty. > > Was someone successful with another solution? > > > > -- > Gael Fraiteur > http://gael.fraiteur.net > Prague, Czech Republic > ---------------------------------------------------------------- > PostSharp is an open-source post-compiler for .NET > http://gael.fraiteur.net/postsharp.aspx > ---------------------------------------------------------------- > >
Have you tried creating an app.config file that has a codebase hint to the
assembly? Also, why is subscribing to the AssemblyResolve event 'dirty'? It sounds like it might be exactly what you need. [quoted text, click to view] "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message news:eHoo2bDlFHA.320@TK2MSFTNGP09.phx.gbl... >I would like to add to the search path of my application a directory where > some plug-ins reside. But this directory is not under the application base > directory. I tried many procedures, but nothing works. By the way, these > things are quite badly documented in Beta 2. > > The problem is that the runtime claims it won't take into a account a > private path that is not under the application base path. I overcame the > probleme by overloading AppDomain.AssemblyResolve, but this solution is > quite dirty. > > Was someone successful with another solution? > > > > -- > Gael Fraiteur > http://gael.fraiteur.net > Prague, Czech Republic > ---------------------------------------------------------------- > PostSharp is an open-source post-compiler for .NET > http://gael.fraiteur.net/postsharp.aspx > ---------------------------------------------------------------- > >
Hi Gael,
PrivateBinPath should work as well as ApplicationBase, but you need to be in control of your AppDomain creation in order for that to work. Once an AppDomain exists those properties can't be set and that might be the reason it's not working. -- Rick Strahl West Wind Technologies www.west-wind.com www.west-wind.com/weblog [quoted text, click to view] "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message news:eHoo2bDlFHA.320@TK2MSFTNGP09.phx.gbl... >I would like to add to the search path of my application a directory where > some plug-ins reside. But this directory is not under the application base > directory. I tried many procedures, but nothing works. By the way, these > things are quite badly documented in Beta 2. > > The problem is that the runtime claims it won't take into a account a > private path that is not under the application base path. I overcame the > probleme by overloading AppDomain.AssemblyResolve, but this solution is > quite dirty. > > Was someone successful with another solution? > > > > -- > Gael Fraiteur > http://gael.fraiteur.net > Prague, Czech Republic > ---------------------------------------------------------------- > PostSharp is an open-source post-compiler for .NET > http://gael.fraiteur.net/postsharp.aspx > ---------------------------------------------------------------- > >
I am implementing a similar system and have similar problems to solve.
The current runtime 1.1 has an API called AppDomain.AppendPrivatePath that allows you to dynamically extend the private path of the current AppDomain. Unfortunately, this is being deprecated in Whidbey, which greatly reduces the options available. If you are targeting the 1.1 framework then this may provide all you need. If you know in advance which plugins you want to load and what their private paths are, you can create an app.config file that contains a <configuration\runtime\assemblyBinding\probing> element that consists of the subdirectories below the appbase you want it to automatically search. But you already stated you need a dynamic solution. Because the AppendPrivatePath API is obsolete you are forced to do something such as write your own version of this that will dynamically add the paths to a list that you use in your AssemblyResolve handler. [quoted text, click to view] "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message news:%23HwgDFnlFHA.576@TK2MSFTNGP15.phx.gbl... > Hi, > > Thanks to all for your answers. > My initial problem is that I need to load plugins that eventually have > private assemblies. So I want to extend the private path of the current > AppDomain dynamically (so using app.config was not a solution). I did not > want to use AssemblyResolve because it though it was useless to implement > some logic that is already present in the framework. > > Thanks again. > > -- > Gael Fraiteur > http://gael.fraiteur.net > Prague, Czech Republic > ---------------------------------------------------------------- > PostSharp is an open-source post-compiler for .NET > http://gael.fraiteur.net/postsharp.aspx > ---------------------------------------------------------------- > > "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message > news:eHoo2bDlFHA.320@TK2MSFTNGP09.phx.gbl... >> I would like to add to the search path of my application a directory >> where >> some plug-ins reside. But this directory is not under the application >> base >> directory. I tried many procedures, but nothing works. By the way, these >> things are quite badly documented in Beta 2. >> >> The problem is that the runtime claims it won't take into a account a >> private path that is not under the application base path. I overcame the >> probleme by overloading AppDomain.AssemblyResolve, but this solution is >> quite dirty. >> >> Was someone successful with another solution? >> >> >> >> -- >> Gael Fraiteur >> http://gael.fraiteur.net >> Prague, Czech Republic >> ---------------------------------------------------------------- >> PostSharp is an open-source post-compiler for .NET >> http://gael.fraiteur.net/postsharp.aspx >> ---------------------------------------------------------------- >> >> > >
Hi,
Thanks to all for your answers. My initial problem is that I need to load plugins that eventually have private assemblies. So I want to extend the private path of the current AppDomain dynamically (so using app.config was not a solution). I did not want to use AssemblyResolve because it though it was useless to implement some logic that is already present in the framework. Thanks again. -- Gael Fraiteur http://gael.fraiteur.net Prague, Czech Republic ---------------------------------------------------------------- PostSharp is an open-source post-compiler for .NET http://gael.fraiteur.net/postsharp.aspx ---------------------------------------------------------------- [quoted text, click to view] "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message news:eHoo2bDlFHA.320@TK2MSFTNGP09.phx.gbl... > I would like to add to the search path of my application a directory where > some plug-ins reside. But this directory is not under the application base > directory. I tried many procedures, but nothing works. By the way, these > things are quite badly documented in Beta 2. > > The problem is that the runtime claims it won't take into a account a > private path that is not under the application base path. I overcame the > probleme by overloading AppDomain.AssemblyResolve, but this solution is > quite dirty. > > Was someone successful with another solution? > > > > -- > Gael Fraiteur > http://gael.fraiteur.net > Prague, Czech Republic > ---------------------------------------------------------------- > PostSharp is an open-source post-compiler for .NET > http://gael.fraiteur.net/postsharp.aspx > ---------------------------------------------------------------- > >
If you're adding plug-ins the best solution tends to be createing a new AppDomain and then loading the plug-ins into that. By doing so you can get to control the creation of hte new AppDomain and the PrivateBinPath with it. All you have to do then is to make sure that all related assemblies exist in the known paths that you've set up previously, which is a reasonable requirement for add-ins. There's no way to manipulate these settings once the AppDomain's been created. What I have done in the past where I didn't have the choice for a new AppDomain is go the brute force route and do my own 'shadow copying' of assemblies from one place to another. This is ugly as sin but it worked to make things work as long as I knew where the files where coming from. +++ Rick --- -- Rick Strahl West Wind Technologies www.west-wind.com www.west-wind.com/weblog [quoted text, click to view] "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message news:%23HwgDFnlFHA.576@TK2MSFTNGP15.phx.gbl... > Hi, > > Thanks to all for your answers. > My initial problem is that I need to load plugins that eventually have > private assemblies. So I want to extend the private path of the current > AppDomain dynamically (so using app.config was not a solution). I did not > want to use AssemblyResolve because it though it was useless to implement > some logic that is already present in the framework. > > Thanks again. > > -- > Gael Fraiteur > http://gael.fraiteur.net > Prague, Czech Republic > ---------------------------------------------------------------- > PostSharp is an open-source post-compiler for .NET > http://gael.fraiteur.net/postsharp.aspx > ---------------------------------------------------------------- > > "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message > news:eHoo2bDlFHA.320@TK2MSFTNGP09.phx.gbl... >> I would like to add to the search path of my application a directory >> where >> some plug-ins reside. But this directory is not under the application >> base >> directory. I tried many procedures, but nothing works. By the way, these >> things are quite badly documented in Beta 2. >> >> The problem is that the runtime claims it won't take into a account a >> private path that is not under the application base path. I overcame the >> probleme by overloading AppDomain.AssemblyResolve, but this solution is >> quite dirty. >> >> Was someone successful with another solution? >> >> >> >> -- >> Gael Fraiteur >> http://gael.fraiteur.net >> Prague, Czech Republic >> ---------------------------------------------------------------- >> PostSharp is an open-source post-compiler for .NET >> http://gael.fraiteur.net/postsharp.aspx >> ---------------------------------------------------------------- >> >> > >
Thank you Rick.
In my situation, I think this situation will be unusable from a performance point of view, because I cannot afford to cross AppDomain borders for every single call from the plug-in to the object model they are supposed to modify. I am writing a post-compiler, so imagine that plug-ins can potentially access the main AppDomain (where the IL DOM resides) for each IL instruction... I will go for the AssemblyResolve solution, i.e. I will implement a custom binder based on this event and use the Assembly.LoadFile method. Thank you anyway. Gael -- Gael Fraiteur http://gael.fraiteur.net Prague, Czech Republic ---------------------------------------------------------------- PostSharp is an open-source post-compiler for .NET http://gael.fraiteur.net/postsharp.aspx ---------------------------------------------------------------- [quoted text, click to view] "Rick Strahl [MVP]" <rickstrahl@hotmail.com> wrote in message news:O6x07O9mFHA.1088@TK2MSFTNGP14.phx.gbl... > > If you're adding plug-ins the best solution tends to be createing a new > AppDomain and then loading the plug-ins into that. By doing so you can get > to control the creation of hte new AppDomain and the PrivateBinPath with it. > All you have to do then is to make sure that all related assemblies exist in > the known paths that you've set up previously, which is a reasonable > requirement for add-ins. > > There's no way to manipulate these settings once the AppDomain's been > created. What I have done in the past where I didn't have the choice for a > new AppDomain is go the brute force route and do my own 'shadow copying' of > assemblies from one place to another. This is ugly as sin but it worked to > make things work as long as I knew where the files where coming from. > > +++ Rick --- > > -- > > Rick Strahl > West Wind Technologies > www.west-wind.com > www.west-wind.com/weblog > > > > "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message > news:%23HwgDFnlFHA.576@TK2MSFTNGP15.phx.gbl... > > Hi, > > > > Thanks to all for your answers. > > My initial problem is that I need to load plugins that eventually have > > private assemblies. So I want to extend the private path of the current > > AppDomain dynamically (so using app.config was not a solution). I did not > > want to use AssemblyResolve because it though it was useless to implement > > some logic that is already present in the framework. > > > > Thanks again. > > > > -- > > Gael Fraiteur > > http://gael.fraiteur.net > > Prague, Czech Republic > > ---------------------------------------------------------------- > > PostSharp is an open-source post-compiler for .NET > > http://gael.fraiteur.net/postsharp.aspx > > ---------------------------------------------------------------- > > > > "Gael Fraiteur" <gael@nosppam.fraiteur.net> wrote in message > > news:eHoo2bDlFHA.320@TK2MSFTNGP09.phx.gbl... > >> I would like to add to the search path of my application a directory > >> where > >> some plug-ins reside. But this directory is not under the application > >> base > >> directory. I tried many procedures, but nothing works. By the way, these > >> things are quite badly documented in Beta 2. > >> > >> The problem is that the runtime claims it won't take into a account a > >> private path that is not under the application base path. I overcame the > >> probleme by overloading AppDomain.AssemblyResolve, but this solution is > >> quite dirty. > >> > >> Was someone successful with another solution? > >> > >> > >> > >> -- > >> Gael Fraiteur > >> http://gael.fraiteur.net > >> Prague, Czech Republic > >> ---------------------------------------------------------------- > >> PostSharp is an open-source post-compiler for .NET > >> http://gael.fraiteur.net/postsharp.aspx > >> ---------------------------------------------------------------- > >> > >> > > > > > >
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 |