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

First, let me say, I am new to SharePoint Development.

I have been able to create a couple of related custom lists using SharePoint Designer. I was able to deploy them and they work quite well. However, I am debating if I should have created them using Visual Studio instead for ease of deployment to other sites.

It seems like list creation is very easy in Designer as opposed to all the CAML in Visual Studio. But is there one method that preferred over another? What are the advantages/disadvantages to each approach?

share|improve this question
up vote 1 down vote accepted

You've touched on one of the reasons I use VS instead of Designer - having files and packages independent of a specific site does make redeployment much easier.

For me, the main advantage is the integration with Source Control so I can track all the changes I (or anyone else) have made.

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.