|
-
Dec 14th, 2004, 06:02 AM
#1
Thread Starter
Evil Genius
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????
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|