Hmm, I was unaware this folder also participates in populating the "Add
Reference" list. I am pretty sure though that the contents of the
%VSNETINSTALLDIR%\Common7\IDE\PublicAssemblies" folder is used to populate
the list, so I'd recommend that the latter folder is tried first, especially
that copying your own assemblies to the .NET Framework's installation folder
could be risky, while the 'PublicAssemblies' folder *is* dedicated to
copying your own assemblies there to appear in the list.
--
Sincerely,
Dmitriy Lapshin [C# / .NET MVP]
Bring the power of unit testing to the VS .NET IDE today!
http://www.x-unity.net/teststudio.aspx
"Abhishek Khare" <(E-Mail Removed)> wrote in message
news:eiq%(E-Mail Removed)...
> The list of assemblies you see in the "Add Reference" dialog is populated
> not from the GAC contents, But from the folder, "Windows Directory /
> Microsoft.Net / Framework / Version Folder(as v1.1.4322) /
> You can copy the assembly there and it will appear in the list.
> Happy DotNetting
>
> --
>
> Thanks & Regards,
>
> Abhishek Khare
> Asst. Software Engineer
> Differential Technologies Ltd.
> New Delhi
> "Richard Blewett [DevelopMentor]" <(E-Mail Removed)> wrote in
> message news:OmWoiax$(E-Mail Removed)...
>> Also, [1] tells you how to add other locations to the list of folders
> listed
>>
>> [1]
> http://msdn.microsoft.com/library/de...us/vbcon/html/
> vbtskaddingremovingreferences.asp
>>
>> Regards
>>
>> Richard Blewett - DevelopMentor
>> http://www.dotnetconsult.co.uk/weblog
>> http://www.dotnetconsult.co.uk
>>
>> Hi,
>>
>> The list of assemblies you see in the "Add Reference" dialog is
>> populated
>> not from the GAC contents, but rather from the Public Assemblies folder
>> under the Visual Studio .NET installation directory.
>> You can copy the assembly there and it will appear in the list.
>>
>>
>
>