Dynamic Reference Locations?
-
I know you can make web-references dynamic, which then only need a small change in the web.config file to repoint them to the new location you want to look at. My question is, can you do something aking to this with regular (non-web) references? Perhaps using the web/.config file, or a manifest file or something? We are looking to create a central library directory where we can keep our common libraries for access from any machine which needs them. One consideration was 2K's Distributed File System, but that is an awful lot of complications, especially since it means getting our domain administrators involved. So i was thinking there might be an easier way by being able to just put in a line which tells the app where to look for the reference at run-time. yes?? Thanks in advance.
-
I know you can make web-references dynamic, which then only need a small change in the web.config file to repoint them to the new location you want to look at. My question is, can you do something aking to this with regular (non-web) references? Perhaps using the web/.config file, or a manifest file or something? We are looking to create a central library directory where we can keep our common libraries for access from any machine which needs them. One consideration was 2K's Distributed File System, but that is an awful lot of complications, especially since it means getting our domain administrators involved. So i was thinking there might be an easier way by being able to just put in a line which tells the app where to look for the reference at run-time. yes?? Thanks in advance.
There is a way of doing this with regular refrences though you are required to use reflection to dynamically load the assembly you are looking for. Have a squizz here http://msdn.microsoft.com/library/en-us/cpguide/html/cpconhowruntimelocatesassemblies.asp[^] It would probably be eaiser to just setup a network share for the library, and add a project reference. I think deciding which asseblies to use at runtime is most suited to situations where you know the interface but you want the freedom to decide which assembly you will use to implement that interface.
-
There is a way of doing this with regular refrences though you are required to use reflection to dynamically load the assembly you are looking for. Have a squizz here http://msdn.microsoft.com/library/en-us/cpguide/html/cpconhowruntimelocatesassemblies.asp[^] It would probably be eaiser to just setup a network share for the library, and add a project reference. I think deciding which asseblies to use at runtime is most suited to situations where you know the interface but you want the freedom to decide which assembly you will use to implement that interface.
That sounds about right. I would just point out that assemblies run from a network share will have reduced permissions when using the default security settings for .NET. Depending on what your assemblies do, you may need to alter these settings to give your assemblies the necessary permissions. Regards Mark Smithson