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

Besides the usual bin and obj folders, what else can be excluded from source control in the Visual Studio 2010 SharePoint solution I've built?

I'm particularly interested in whether the pkg and pkgobj folders can be excluded. They contain copies of files I created but the pkgobj folder contains a subfolder called TokenReplaceFolder. If I don't check this in, is my solution likely to blow up when someone checks it out for the first time?

share|improve this question
up vote 5 down vote accepted

You do not need the pkg or the pkgobj folders, they are temporary and used by the packaging routine

share|improve this answer

I did not check this yet. If it aint in your VS2010 project, it doesn't need to go in your source control. My SP2010 project doesn't have theses files/folders in TFS and it's not an issue for check-out. I've switched VM a couple of times, check-out my projects, build it and deployed without any issue.

To test that you can copy the files in another location, remove all the folders/files you think are unecessary and build it.

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.