2
Vote

Seperate MOSS, SharePoint, and Non-SharePoint modules

description

Currently, all dot net specific non-sharepoint code is stored in the same assembly as SharePoint. Also, functionality specific to MOSS has not been seperated into its own assemblies and features. This may make some components difficult to leverage in diverse environments. Should we break the solution apart for flexibility, or keep it together for simplicity and manageability?

comments