There is not much documentation of best practices on this topic, but on MSDN there is an article about how to deal with SharePoint development environments, finally! This article is based on how to deal with internal development. There are some area’s however that still have some need for attention according to me:
- What about offsite development? We often work at the customer location because it’s good for user adoption and because it’s a very easy way to communicate. How should we deal with VSS, testing and developers that have no internet access at the customers office?
- What about styles, area/list structures and site definitions? SharePoint development is not only about webparts and webservices. It has also a lot to do with how to design the environment. In many cases, lists are used as source for data in webparts. Also area structures can be important for development scenario’s. I posted a little about deploying structures before here.
Besides that, a good article in the good direction! We are currently redesigning out development achitecture and this article is some usefull input.
From MSDN:
“Learn to conduct team-based development of Microsoft Windows SharePoint Services and Microsoft Office SharePoint Portal Server 2003–based applications. These applications can include customized Web Part Pages, Web Parts, supporting Web applications, and Web services.”
Read the complete article