when assemblies in gac change;programs should update themselves

[Kayıhan]

i have an developer server. I write c# code on it and publish programs from
the same server with "only online" option.
I am using same custom library(in gac) for all projects. I want that when i
changed library(assembly in gac);all programs that i publish must update
themselves without buid them again. Is it possible;if not could you offer me
a solution close to i am trying to do.
thanks for answers in advance

 

[Peter Duniho]

i have an developer server. I write c# code on it and publish programs from
the same server with "only online" option.
I am using same custom library(in gac) for all projects. I want that when i
changed library(assembly in gac);all programs that i publish must update
themselves without buid them again. Is it possible;if not could you offer me
a solution close to i am trying to do.

Can you be more specific? All managed code, unless already in the GAC,
is compiled "just-in-time". Even managed code in the GAC, if a
dependency of the code is updated, will still be recompiled
"just-in-time" when executed.

What does it mean to "update" a program yet "without building them
again"? Please explain your use of the word "update" here. How is it
different from "build them again"?

Pete

 

[Kayıhan]

i meant with "update" that when the assembly in gac changes;programs using
this assembly should use this new assembly.

specifically;
you have a server named developerServer, you publish programA(only online)
uses assembly1 versioned 1.0 .
if you changed assembly1 which is versioned 1.1
then the programA which downloaded by clients , must be most updated version
that i meant it must use assembly1 versioned 1.1(but i dont have to compile
programA)

 

[Peter Duniho]

i meant with "update" that when the assembly in gac changes;programs using
this assembly should use this new assembly.

specifically;
you have a server named developerServer, you publish programA(only online)
uses assembly1 versioned 1.0 .
if you changed assembly1 which is versioned 1.1
then the programA which downloaded by clients , must be most updated version
that i meant it must use assembly1 versioned 1.1(but i dont have to compile
programA)

I'm not sure, but I don't think you can force that. For example, the
client could include a copy of the 1.0 assembly1 in the same directory
as the programA assembly.

But I also believe that the _normal_ scenario is for the assembly1 to be
in the GAC, and to replace the 1.0 version, and for the new version to
be the one that programA uses. Only if the user is intentionally
fiddling with the configuration would that break, and if the user's
doing that, you need something stronger than what .NET is able to
provide inherently (i.e. programA needs a way to learn and enforce the
most-recent version at runtime).

Pete