I have posted a similar question before but I wanted to change the title to get more replies :)

OK here is the scenario. I have a folder with several utility classes that I want to use in several solutions/projects, but when I add an existing file from my utility folder VS.NET makes a copy of that class file into the solution/project folder. So now if I find a bug (or want to optimize my class) in the utility class I have to make changes in the original utility class file and also in all the places where VS.NET has copied my utility class.
This seems kind of like a step in the wrong direction to me. Any thoughts?
In VFP this was really easy to do.

Is this going to be addressed in .NET 2005?

In my previous post I got a reply from Bonnie and she said she solved this using the sharing feature of VSS. I guess this will work but I will have to look more into it before I feel comfortable with letting VSS handle this.

So anywho any thoughts or comments about this are welcome. How do you do this? I don't mind distributing DLLs with my apps but I don't want to distribute 300 DLLs with my apps.

Thanks,
Einar