>> I don't think you should actually include the projects into your solution, though for my purpose I'm going to do that.
>
>Actually, I'd normally suggest just the opposite unless you have a reason not to (solutions with a large number of projects being the main example). If you add a project to your solution (and add project references to your other projects instead of referencing the DLL), VS will automatically handle a lot of things for you, like keeping your assembly versions up to date. It also makes debugging into referenced assemblies easier (you don't run into the stupid issues w/it not automatically finding the debug symbols). It's also nice to be able to quickly make changes in those other projects w/o having to close the current proj. and open the other one.

Thanks, Paul, sounds like a good idea, I will keep it in mind.

BTW, today I started to add base classes internal code using the Scott's blog you gave me a link some time ago, but haven't finished yet.