Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • If possible, I'd like to avoid branching because I find that it adds significant complexity to managing source control. Commented Mar 31, 2011 at 15:24
  • 1
    Branching - yes it does if using SVN/VSS etc. If using a DVCS then its much much less painful. This tutorial is for Mercurial but the same principles apply to others such as GIT. Having said all that I don't believe that branching is the way to solve this particular problem. Commented Mar 31, 2011 at 23:05
  • @Ryan Very interesting sidebar. We're currently using TFS as our source control system, which is not a DVCS. However it does support shelving, which would allow developers to save their code to source control without affecting everyone else. Commented Apr 4, 2011 at 13:24
  • "I could inadvertently deploy his unfinished code." means branching to me. Even when reduced to 1 web part per wsp the problem of unfinished changes to that 1 web part from multiple developers will still exist. Commented May 15, 2011 at 17:54