Results 1 to 2 of 2

Thread: limitations/disadvantages to using the GAC

  1. #1

    Thread Starter
    Evil Genius alex_read's Avatar
    Join Date
    May 2000
    Location
    Espoo, Finland
    Posts
    5,538

    limitations/disadvantages to using the GAC

    I have an assembly/ a dll which I'll be using throughout several different upcoming projects.

    Rather than include this file in each project I wanted to use a way for each of the projects to use the same file. As these projects will all be on the same webserver & not needed to be used over a network or the internet, I've ruled out a webservice & looked into deploying this into the GAC.

    I'm sure I picked up some drawbacks of using the GAC in the past, but now can't find anything on this on the web. Can anyone provide any articles/points on what the drawbacks are on using the GAC please????

    Please rate this post if it was useful for you!
    Please try to search before creating a new post,
    Please format code using [ code ][ /code ], and
    Post sample code, error details & problem details

  2. #2
    Addicted Member
    Join Date
    Aug 2003
    Posts
    153

    Re: limitations/disadvantages to using the GAC

    Only drawback I can think of is that you can't use XCopy deployment. You will need to register the DLL in the GAC via an installer, or instruct the user how to do so manually.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width