Sounds you need a 'well known store' of information that would indicate
what code is available, where it is what version it is, etc...
Some central xml file that clients know the location of.
Or, a webservice that returns this info to the caller, or, client machines
just enumerate a directory structure at a well known location to derive what
is available. E.g,
\CodeRoot
|
\AssemblyName
|
\V1.0.0.0(dir)
|
\V1.0.0.1 (dir)
|
\assembly.dll
In the AssemblyName folder have an xml file of known format, that indicates
which version is the 'current' production one, which version is the current
'testing' one, etc...
-----Original Message-----
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Claus Brod
Sent: Thursday, January 08, 2004 4:23 PM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Trying to avoid the GAC using the /codebase
option
Brandon Manchester wrote:
> 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
===================================
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
