mojoPortal source code is now hosted in a Mercurial repository at Codeplex.
The easiest way to get the latest stable source code is using TortoiseHG. You can follow steps 1 and 3 in this tutorial and for the Source path use https://hg01.codeplex.com/mojoportal
After you have done an initial clone, you can get updates to the source code as follows:
-
Right click the folder where you cloned and choose HG Repository Explorer
-
In Repository Explorer click the toolbar icon to "Pull incoming changes" (if you mouse over the buttons you will see the tool tip). It is the 4th toolbar item from the left (the down arrow with a line under it)
-
Close Repository Explorer
-
Right click the folder where you cloned again, and this time choose TortoiseHG > Update, this will apply all the changes you pulled down to your copy of the repository
-
After getting the latest code you should always rebuild the solution in Visual Studio and then visit the /Setup/Default.aspx page to run any new scripts that may have come down with the code.
You can also use Repository Explorer to review comments for all change sets pulled down to your copy of the repository.
You can find out when new code is available on the server by viewing this page on Codeplex, you can also subscribe to this RSS feed using Google Reader or any Feed reader to get updates on new code that has been pushed to the server.
Differences between our new Mecurial (aka HG) Repository and our previous Subversion (aka svn) Repository
Whereas when we were using TortoiseSVN/svn, we had the concept of "trunk" which was the main branch, in Mercurial this is just called the default branch which is what you get when you clone the repository.
Whereas Subversion was a centralized repository, Mercurial is a distributed repository, this blog post about Distributed Source Control vs Centralized Source Control (especially the comments) provides a lot of insights. When you clone a repository your local copy is a full blown repository of its own. You could even add your custom projects and commit them to your local copy of the repository and use it to track changes in your own files so you can revert to previous versions and keep logs of changes in your development of custom features. The repository on the server is still the central authoritative repository but you have all the repository functionality on your local copy. If you do use the local repository for your own code you should have some kind of file backup strategy since your code is not backed up on the server like the main repository.
Additional Resources
Last Updated 2010-05-20