This is in connection with
another post here, about "simulating" the Visual Studio Add Reference functionality.
I have got a very good working version and it looks pretty good, but during testing I discovered that System.dll and numerous other assemblies, are contained in this folder:
I want to ask, how Visual Studio "knows" that some assemblies are in this folder? that folder path does NOT appear beneath any of the
AssemblyFolders registry keys.
I've manually included this folder path string in my solution, but there must be some systematic way that Visual Studio "knows" that some key assemblies are in this folder.
If you do an Add Reference in Visual Studio and locate System.dll, you will see it is in the above folder, even though I am using v 3.5 of the framework.
Just to remind you, when a 3rd party adds components to the users GAC, they must also have copies in some folder, and add that folder beneath the
AssemblyFolders registry key, this is how you ensure your newly added component will appear in the Add Reference dialog of Visual Studio.
But System.dll (and the others in that folder) seem to bre
View Complete Post