This project has moved. For the latest updates, please go here.

On how to start SP™ development right away!

Topics: General '15, Survey Project Team
Apr 14, 2012 at 10:10 AM
Edited May 5, 2012 at 10:17 AM

The Survey™ Project Source Code Repository was moved from Subversion to Mercurial (Distributed source control management system). The change was made to better support the joint development from a central shared repository. No need to join the project. All registered Codeplex users can start developing right away.

I. Subversion versus Mercurial

Mercurial is a Distributed Version Control System (DVCS). Unlike Subversion, DVCS has a very different model for collaborating on an open source project.

    - In DVCS, you do not check in and out changes. You check in and out the entire set of changes (aka the repository).

    - To get started, you first make a local copy of the repository, or clone the repository. In TFS speak, this is the equivalent of getting the entire history (source code + metadata) of each and every change set in source control. It is literally making a copy of everything you see in the CodePlex source control. Since you are copying the entire repository, there isn’t a notion of “checking out”.

   - In DVCS, you commit to the local repository, and push your changes back to CodePlex.

   - Since you have your own repository, you “check in” by committing to your local repository. Once you’ve committed locally, you can “check in” those changes back to CodePlex by pushing those changes. Hence the term “check in” doesn’t apply because it is overloaded in the DVCS context.

II. Using Mercurial Step by Step:

Follow these links:

Note: some of the instructions are outdated e.g. HG Repository Explorer = Workbench.

III. Survey Repository Access

To access the Survey Repository to create your copy (Clone) use the Mercurial Clone URL:
Username/ password: use your Codeplex account data.

To download and install the Mercurial client for windows on you computer:

IV. Development by creating Forks

To work on the Survey project as a developer and contribute to the central code you have to start creating you own Fork. Instructions on how to create and use a fork:

For instructions on how to get the latest changes from a project into your fork see Updating a Fork with Changes from the Master Repository.

V. Summary on how to start Developing

Make sure to take the following steps when contributing code:

- Create a Fork at the Codeplex site (Source Code).
- Clone a copy of the Forks Source Code to your local machine.

- Create a work item through the Issue Tracker (mail us if you want to work on an existing one)
- Make changes to the code locally, for ONE work item, and test them thoroughly.
- Update the Survey_changelog.txt accordingly (see solution rootdirectory)

- Commit the changes to your local repository and Push the changes to the Codeplex Fork.
- Synchronise your Fork with the latest changes from the Central Repository
- Next you can submit a Pull Request to have the project review the changes

- Changes that are accepted will be Merged to the Central Repository to become part of the next release.

Please read the following updated documents that contain general guidelines:

- Survey™ project Codeplex guidelines - 2012,
- Survey Project Codeplex & Software Configuration Management - 2012

If you have any questions please check the Community Forums or send a message to

Kind regards,

Jun 10, 2013 at 6:24 PM

There is no such thing as a silly question. Laziness is yet another thing.

Instead of spending scarce time on answering all questions politely we choose to serve you by working on the next version of SP.
Unless we think the question can or has not been answered elsewhere already.

Kind regards
SP coordinator
Marked as answer by fwsmaster on 2/23/2014 at 12:30 PM
Dec 5, 2014 at 12:29 PM
Additional info:

Check the instructions on how to get the SP Solutions up and running locally in Visual Studio at: