With many customers and partners migrating to SharePoint 2010, one of the topics I get asked about regularly is making “safe” customizations to SharePoint and thinking about upgrades and migrations – both now and in the future. While the answer is often “it depends” there are some general guidelines that I offer:
As for making changes to SharePoint itself, as I’ve mentioned in my SharePoint as a development platform and crawl, walk, run posts and talks here are some general strategies to help speed development, testing and ease future maintenance of SharePoint solutions:
Let me also add this - if you're a "power customizer" but have been afraid of Visual Studio - get over it! Visual Studio 2010 is easier than ever for building and deploying customizations - simple data bound web parts or customized list templates in less than 15 minutes, as manageable code. VS2010 is your friend.
I fully agree Chris. With Visual Studio 2010, SharePoint 2010 development is now a 1st class citizen. I expect many ASP.NET developers to be very excited about the improvements here.