It seems to me that in VS.Net a project = assembly = .dll file.

So, if you are putting different controls in different projects then you get multiple .dlls to deal with, right?

Or, perhaps you meant to say, different .cs files?

It seems to me that you would want all 'Company.Common.Window.Controls' in a single assembly/dll/project that you can give a strong name and install in the GAC. This would be shared by all apps.

Then, any app specific controls you would create as a .cs file right in your UI project, or you could have a seperate project in your applications solution for controls that could be shared with that solution.

In the above case if you modify a common control, you ship one .dll. IF you modify 5 common controls, you ship one .dll. Same thing with app sepcific controls, change one or more, ship one .dll.

Make sense?

Also, I believe it is possible to have an assembly span .dll's but I never got into doing that.

BOb