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

I am creating a custom sharepoint feature (2010) it will have the following:

-5 custom lists -3 workflows -Adding some fields to existing lists

All this can be done in sharepoint designer, however i want to be able to give this feature to other clients without having to go into sharepoint designer and set it up for every client (i want a more automated process as this will save time and reduce bugs).

The first idea that comes to mind it to do this programatically e.g. create all lists, workflows, fields etc in visual studio.

Is this the best approach? Are there any downsides to this?

share|improve this question
up vote 0 down vote accepted

I don't think there is any downside in this approach... as this seems to fit best for your need! However, other options to consider may be that you setup a single site with the custom lists, workflows and fields and save the site as template! Then distribute the .wsp file created for the site template... This will save you from programming everything!

But that really depends on the requirements you have!

Kind of similar question is answered here

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.