 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / New Users / May 2004GAC and the .NET IDE
I have done a lot of poking around on the newsgroups trying to find a good explanation as to why I have to take the extra step of making a registry entry in order for the .NET IDE to show my registered GAC assemblies. I understand technically why they don't show up but why wouldn't we want them to? Can anybody give me an acceptable reason why I might 'not' want to see the entire list of GAC assemblies in my 'Add Reference...' dialog? Why isn't the 'Add Reference...' function smart enough to pull the entire GAC? thanks, Sean The default references aren't to the GAC anyway. They're to the Windows\Microsoft .NET\Framework.... folder. If it was purely to the GAC you'd see 1.0, 1.1 etc assemblies, but VS .NET is developed with 1.0, VS 2003 with 1.1 etc.  SignaturePhil Wilson [MVP Windows Installer] ---- > I have done a lot of poking around on the newsgroups trying to find a > good explanation as to why I have to take the extra step of making a [quoted text clipped - 7 lines] > thanks, > Sean I 'understand' the technical reasons why my assemblies do not automatically appear in the 'Add Reference..' dialog, BUT, what I do not understand is why the dialog was not designed to pull all the registered assemblies from the GAC. It's almost as if they intentionally added this registry step to confuse and prevent the more novice users from abusing the function of the GAC. Can someone please answer this for me? thanks, Sean Sean, >abusing the function of the GAC. So what is the function of the GAC according to you? To me, it's primarily a deployment feature, and as such there's rarely any reason to use it during development. Why is your assembly in the GAC? Mattias SignatureMattias Sjögren [MVP] mattias @ mvps.org http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com Please reply only to the newsgroup. Hi again. It seems to be very difficult to get a straight answer to my question for some reason so I'm going to try to make it as clear as possible, here goes: WHY didn't Microsoft DECIDE to have all GAC-registered assemblies AUTOMATICALLY populate in the 'Add Reference...' dialog? If someone can please answer this question, I would be most grateful. thank you Sean Sean, I believe that *if* an assembly is GAC registered, it displays in the 'Add reference...' dialog. At least from my experience. ==================== RBisch - C# enthusiast ryanbischoff@PLZyahooNO_SPAM.com > Hi again. It seems to be very difficult to get a straight answer to > my question for some reason so I'm going to try to make it as clear as [quoted text clipped - 7 lines] > thank you > Sean > Sean, > I believe that *if* an assembly is GAC registered, it displays in the 'Add [quoted text clipped - 3 lines] > RBisch - C# enthusiast > ryanbischoff@PLZyahooNO_SPAM.com Hi, Ryan?? Your 'belief' is incorrect, for the reason that, despite the fact an assembly may be registered in the GAC, it is further necessary to manually add a specific registry entry in order for it to appear in the .NET IDE. To all other people out there, I implore you, please, IF, and only IF, you can answer the following question, then please do so: WHY didn't Microsoft DECIDE to have all GAC-registered assemblies AUTOMATICALLY populate in the 'Add Reference...' dialog, without the need for a manual registry entry? Thanks once again, Sean Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.