GAC

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Phil
    #1

    GAC

    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


    Tags: None
    • Tim Stephenson
      #2
      Re: GAC

      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


      "Phil" <phil.a.wood@nt lworld.com> wrote in message
      news:047801c38f 32$a67cf650$a00 1280a@phx.gbl.. .[color=blue]
      > 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
      >
      >[/color]


        Comment

        • phil
          #3
          Re: GAC

          A Cracking, quality answer!

          Thanks VERY MUCH


          [color=blue]
          >-----Original Message-----
          >The idea of the GAC is to allow multiple versions of[/color]
          assemblies shared[color=blue]
          >between applications. While it's perfectly possible to[/color]
          deploy lots of[color=blue]
          >different versions into the GAC, only the latest will be[/color]
          used unless you[color=blue]
          >specifically declare a dependency on a particular[/color]
          version.[color=blue]
          >
          >Unless you're just going to let the old versions keep[/color]
          collecting in the GAC,[color=blue]
          >it can also get a little tedious to have to continually[/color]
          add a new version,[color=blue]
          >and remove the previous ones each time you change your[/color]
          code.[color=blue]
          >
          >While you're developing the shared components it's often[/color]
          a good idea (read[color=blue]
          >as making life easier!) to develop using private[/color]
          assemblies in your[color=blue]
          >application' s folders until you reach a point where the[/color]
          code is stabilised.[color=blue]
          >
          >Hope that helped,
          >--
          >Regards
          >
          >Tim Stephenson MCSD.NET
          >Charted MCAD & MCSD.NET Early Achiever
          >
          >
          >"Phil" <phil.a.wood@nt lworld.com> wrote in message
          >news:047801c38 f32$a67cf650$a0 01280a@phx.gbl. ..[color=green]
          >> If a shared assemblies interface changes quite a lot,[/color][/color]
          is[color=blue][color=green]
          >> it worth deploying into the GAC to aid side by side
          >> execution etc
          >>
          >> Any help appreciated
          >>
          >> Muchos
          >>
          >>[/color]
          >
          >
          >.
          >[/color]

            Comment

            • Tim Stephenson
              #4
              Re: GAC

              No worries

              --
              Regards

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


              "phil" <phil.a.wood@nt lworld.com> wrote in message
              news:0df801c38f 41$3cbe8170$a40 1280a@phx.gbl.. .[color=blue]
              > A Cracking, quality answer!
              >
              > Thanks VERY MUCH
              >
              >
              >[color=green]
              > >-----Original Message-----
              > >The idea of the GAC is to allow multiple versions of[/color]
              > assemblies shared[color=green]
              > >between applications. While it's perfectly possible to[/color]
              > deploy lots of[color=green]
              > >different versions into the GAC, only the latest will be[/color]
              > used unless you[color=green]
              > >specifically declare a dependency on a particular[/color]
              > version.[color=green]
              > >
              > >Unless you're just going to let the old versions keep[/color]
              > collecting in the GAC,[color=green]
              > >it can also get a little tedious to have to continually[/color]
              > add a new version,[color=green]
              > >and remove the previous ones each time you change your[/color]
              > code.[color=green]
              > >
              > >While you're developing the shared components it's often[/color]
              > a good idea (read[color=green]
              > >as making life easier!) to develop using private[/color]
              > assemblies in your[color=green]
              > >application' s folders until you reach a point where the[/color]
              > code is stabilised.[color=green]
              > >
              > >Hope that helped,
              > >--
              > >Regards
              > >
              > >Tim Stephenson MCSD.NET
              > >Charted MCAD & MCSD.NET Early Achiever
              > >
              > >
              > >"Phil" <phil.a.wood@nt lworld.com> wrote in message
              > >news:047801c38 f32$a67cf650$a0 01280a@phx.gbl. ..[color=darkred]
              > >> If a shared assemblies interface changes quite a lot,[/color][/color]
              > is[color=green][color=darkred]
              > >> it worth deploying into the GAC to aid side by side
              > >> execution etc
              > >>
              > >> Any help appreciated
              > >>
              > >> Muchos
              > >>
              > >>[/color]
              > >
              > >
              > >.
              > >[/color][/color]


                Comment

                • Tim Stephenson
                  #5
                  Re: GAC

                  No worries

                  --
                  Regards

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


                  "phil" <phil.a.wood@nt lworld.com> wrote in message
                  news:0df801c38f 41$3cbe8170$a40 1280a@phx.gbl.. .[color=blue]
                  > A Cracking, quality answer!
                  >
                  > Thanks VERY MUCH
                  >
                  >
                  >[color=green]
                  > >-----Original Message-----
                  > >The idea of the GAC is to allow multiple versions of[/color]
                  > assemblies shared[color=green]
                  > >between applications. While it's perfectly possible to[/color]
                  > deploy lots of[color=green]
                  > >different versions into the GAC, only the latest will be[/color]
                  > used unless you[color=green]
                  > >specifically declare a dependency on a particular[/color]
                  > version.[color=green]
                  > >
                  > >Unless you're just going to let the old versions keep[/color]
                  > collecting in the GAC,[color=green]
                  > >it can also get a little tedious to have to continually[/color]
                  > add a new version,[color=green]
                  > >and remove the previous ones each time you change your[/color]
                  > code.[color=green]
                  > >
                  > >While you're developing the shared components it's often[/color]
                  > a good idea (read[color=green]
                  > >as making life easier!) to develop using private[/color]
                  > assemblies in your[color=green]
                  > >application' s folders until you reach a point where the[/color]
                  > code is stabilised.[color=green]
                  > >
                  > >Hope that helped,
                  > >--
                  > >Regards
                  > >
                  > >Tim Stephenson MCSD.NET
                  > >Charted MCAD & MCSD.NET Early Achiever
                  > >
                  > >
                  > >"Phil" <phil.a.wood@nt lworld.com> wrote in message
                  > >news:047801c38 f32$a67cf650$a0 01280a@phx.gbl. ..[color=darkred]
                  > >> If a shared assemblies interface changes quite a lot,[/color][/color]
                  > is[color=green][color=darkred]
                  > >> it worth deploying into the GAC to aid side by side
                  > >> execution etc
                  > >>
                  > >> Any help appreciated
                  > >>
                  > >> Muchos
                  > >>
                  > >>[/color]
                  > >
                  > >
                  > >.
                  > >[/color][/color]


                    Comment

                    Previous template Next
                    Working...