GAC

  • Thread starter Thread starter Phil
  • Start date Start date
P

Phil

If a shared assemblies interface changes quite a lot, is
it worth deploying into the GAC to aid side by side
execution etc

Any help appreciated

Muchos
 
The idea of the GAC is to allow multiple versions of assemblies shared
between applications. While it's perfectly possible to deploy lots of
different versions into the GAC, only the latest will be used unless you
specifically declare a dependency on a particular version.

Unless you're just going to let the old versions keep collecting in the GAC,
it can also get a little tedious to have to continually add a new version,
and remove the previous ones each time you change your code.

While you're developing the shared components it's often a good idea (read
as making life easier!) to develop using private assemblies in your
application's folders until you reach a point where the code is stabilised.

Hope that helped,
 
A Cracking, quality answer!

Thanks VERY MUCH


-----Original Message-----
The idea of the GAC is to allow multiple versions of assemblies shared
between applications. While it's perfectly possible to deploy lots of
different versions into the GAC, only the latest will be used unless you
specifically declare a dependency on a particular version.

Unless you're just going to let the old versions keep collecting in the GAC,
it can also get a little tedious to have to continually add a new version,
and remove the previous ones each time you change your code.

While you're developing the shared components it's often a good idea (read
as making life easier!) to develop using private assemblies in your
application's folders until you reach a point where the code is stabilised.

Hope that helped,
--
Regards

Tim Stephenson MCSD.NET
Charted MCAD & MCSD.NET Early Achiever





.
Click to expand...
 
Back
Top