Nancy,
Could you please list some of the drawbacks using the share file feature in VSS to use a myUtility.cs in several projects?

Is this, building classes into DLLs, Microsoft's official solution?

Thank you for taking the time to reply to my posts.

Sincerely,
Einar

>Einar-
>
>>Yes I think that is the solution from M$, but lets say I have 300 utility classes. Should I build 300 DLLs or one DLL with all 300 classes in it. Neither one of those scenarios sounds appealing to me. Now there is probably some middle ground, i.e. 3 DLLs with 100 classes in them each or something like that.
>
>How you organize your utilities would be up to you, the utilities, and your future plans for using them. I won't venture a recommendation on this.
>
>>Can you think of any drawback with allowing to "point" to a class location from within your project in the way I am sugesting?
>
>Sure. I can also think of benefits, too, which is keeping my modules that are independent truly independent.
>
>If you want to share the code, then I'd do what Bonnie suggested of using shared files in VSS. What don't you trust about that solution? Unless you're not already using VSS, in which case I understand the hesitancy. It's a bother getting that set up correctly.
>
>Don't know if this helps, it's just a solution I'm suggesting, given the tool.