SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are currently working on a project where the first release will be in 2007 and the next release will be in 2010.

In previous projects we have created webparts using user controls and defining everything in code.

Question is should we develop webparts in a specific way in order to make the upgrade as painless as possible?

share|improve this question
up vote 5 down vote accepted

You can continue creating your Web Parts as you are now. As long as you are not using any known deprected method in the SharePoint OM then you are fine. There are no breaking changes in Web Part development, more like enhancements that you can take advantage of in SP2010.

My guess is that you have seen the Visual Web Parts and there is no way to convert a "standard" Web Part to a Visual Web Part.

The upgrade path depends on what tools you are using right now. VSeWSS 1.3 projects can be imported to VS2010, WSPBuilder/STSDev requires you to create a new project and import file by file (not that difficult though). And of course you can still use VS2008 and build your Web Parts but you cannot then take advantage of the new VS2010 UI features.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.