>
>You should ask someone who is using that approach I guess. I'm not. Haven't even considered it, so haven't given it any thought. But it would probably work okay. You just have to remember to keep your source up-to-date in each project. Seems like an additional complication.

Yes if the source is replicated in several projects it would be a mess to maintain, but if the source (myFile.cs) is located in one place and each project reference that file using the path and not copying the file (like you can do in VFP) it would be almost as easy to maintain as building DLLs.

>
>Sure. What's your gut feeling about what you want to do? It sounds like you prefer the VSS route.

Well like the old saying goes "it is hard to teach an old dog new tricks" :) I guess I am just comfortable with the way it can be done in VFP. It makes a lot of sense to bundle utility classes into some DLLs also, the only drawback I see about this approach at this point is that I will have to distribute a lot of DLLs with my applications. I don't know if that is truly a drawback or if I am just calling it a drawback since I am comfortable with the way files can be added to a project by reference in VFP.
So I guess my gut feeling was to go the VSS route with the sharing feature, but I am beginning to lean more towards the alternate DLL way.

Again thank you for taking your time to share your view.

Sincerely,
Einar