I've been a vb programmer for many years. The location of files (not the actual files) included in your vb project was saved in the project. If you modified the file (module, class, etc) every project received the latest version because there was only the one file. Not to mention the obvious advantage to only having one instance of a file on your harddrive. In dotnet it appears that when I add one of my existing modules or classes, a copy of it is made in the project folder. So now there are two instances of my file (a very undesirable situation as it can lead to confusion if a problem arises, made even more confusing as the number of instances of a file increases) Also, if I edit any of these modules or classes won't I now have to check all projects to see if they use the modified file and make sure each gets updated? And what about source control? The concept itself depends upon only 1 instance of all controlled files on your drive.

Thanks,
Robb