ISerializable - Roy Osherove's Blog

Roy,
I’m currently helping a large pharma do the exact same thing. You can contact me offline if you have any questions. The first thing I recommended was creating a Architecture Portal using Sharepoint Team Services. If your company has a MSDN Universal subscription, a license is included in that. This becomes your home, and all projects, and reusable parts (whether that be a component or a class) need to be documented here. Once you and the teams get use to working thru the portal, things become self documenting (for the most part). The biggest obstacle I’ve found is figuring out how to fund development of reusable components. Usually it takes more time to develop a component with reusability in mind, and time is the one thing most projects don’t have. They usually don’t mind donating code to the cause of reusability, but not at the cost of time on their project. Then you also have the cost of support for the components. The question is “Where do you get that money?” If you have a strong architectural group, which has final say on if a project goes into production, then you can at least twist some arms to get them to build the reusable components, but someone still needs to support them.

DonXML

This may interest you - http://www.eweek.com/article2/0,3959,1065920,00.asp