Einar-

>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?

It would seem to me that a solution (the solution?) is to build the class into a dll and then include a reference to that dll in your project.