Are there any guidelines / best practices on developing a class library (custom internal 'enterprise library') or shared source project or solution with multiple projects perhaps, within a small to medium sized webdevelopment company (~50 employees)?
Currently there is one project which includes all 'reusable' code and can be included in new projects. The project is not 'heavy' by far, but the code is not logically connected either, it's just a big pile of previously created functionality. Which questions need to be asked to decide if this is a good approach?
Guidelines/Best Practices on developing class libraries: http://msdn.microsoft.com/en-us/library/ms229042.aspx
Can you clarify? What exactly do you mean when you say "...it's just a big pile of previously created functionality."?