In your client's app.config file you can add an <assemblyBinding> section that can specify things like binding redirects (for versioning), codebases, and probing information.
True, but that would require changes in the config files of all clients, wouldn't it? Our application doesn't necessarily know all its clients, so it can't patch their config files automatically. The other alternative would be to have users modify the client config files, but most users will never understand the XML syntax, and don't want to fool around with config files anyway. Another alternative is to have the client's installation programs search for our app and modify the client config file accordingly.
All of those schemes break when we install a new version of our app or just move the existing installation.
For these reasons, we were really looking for some way to a) advertise the fact that our app's assembly is publicly available on the system and b) tell everybody that the code is not in the GAC, but, for instance, at C:\Program Files\whatever\.... this way, the information about the actual location of our assembly is recorded in only one place, making it much easier to keep it in sync with reality (uninstallation, installation of new versions etc etc).
Thanks!
Claus
=================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in:
NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls
View archives and manage your subscription(s) at http://discuss.develop.com
