centuryloha.blogg.se

1. #Tortoisehg set password how to
2. #Tortoisehg set password install
3. #Tortoisehg set password update
4. #Tortoisehg set password software

Now, you can look at the Hg Repository Explorer and you should see something like this:

#Tortoisehg set password update

I make one more update (this is the *third* part) and check in.

New changeset should be one number higher than the previous one (in my case, 1). If your Hg Commit windows is still open, you can just Refresh it to see the changed files. For this demo, I’m going to update my home page text: Naturally in a real scenario I would be doing major changes that touch many files, not simple things I could easily accomplish typing by hand or using code snippets. Now it’s time for me to complete my demo steps. If you’re trying to follow these steps in an existing repository, your changeset may be a much higher number than 0! It’s important to note the changeset number. If it doesn’t work, you’ll need to troubleshoot that before proceeding. Select all of the files, click Commit, and you should see a dialog telling you:

However, in my case I’m ignoring these folders just as I do with my production source control provider. and in fact you may even want to check in your /bin folder if you want to be able to show your demos without even needing to rebuild. It’s not as important that you ignore all kinds of files like /obj, /bin. svn folders, since this is the initial checkin. You can do your commits from the command prompt, but in my case I’m just going to use Hg Commit from Windows Explorer:Īt this point, you may need to ignore some of the files, like the. Now that I have the opening version of my demo done, I’m going to check it into Hg (but not SVN). In my case, to keep things simple, I’m just going to do some simple edits to the home page of the page, adding a line saying this is the first part of the demo: Get your demo into its basic, starting state where you want it when you start to show it as part of your presentation. You can do this from Windows Explorer by using shift-rightclick, and then selecting Open command window here (not sure which versions of Windows this works on – I’m running Windows 7 and I’m pretty sure it’s been in there for a few versions).įrom there, if you simply type ‘hg’ into the command prompt, you should get output like this, showing that hg is in your path and usable (which will become important). Next, create a command prompt in the same folder location.

You should see something like this showing the repo was created successfully: Assuming you have TortoiseHg, just right-click in your project root folder, go to the TortoiseHg menu option, and select Create Repository Here.

#Tortoisehg set password install

You’ll want to install TortoiseHg if you want to follow along with my steps, though you’re certainly able to do these same steps from the command line. The next step is to add an Hg repository. Here’s a screenshot of the starting root folder: In my case, I’m going to create a local Hg repository which I will then check into my remote SVN repo. You certainly don’t have to do so, and if you don’t keep your presentations in any kind of source control currently, you can ignore this unless it spurs you to start doing so (which might be a good idea). One of the cool things I want to show here, too, is how you can combine Mercurial (Hg) and other source control tools. At the start, I simply have this project, and I’ve checked it into my personal SVN repository (note, I haven’t made the jump to Hg/Git yet for this).

#Tortoisehg set password how to

It worked amazingly well and I thought I would document how to set this up yourself, so that when you’re giving a technical presentation that involves a somewhat complex set of changes to a project, you can easily step through the updates without having to resort to a lot of on-stage typing, code snippets in multiple files, or switching between different projects/folders.įor this example, I’m going to be using as a base a stock ASP.NET MVC 3 web project, but that choice was made somewhat arbitrarily and you could certainly use this technique with any project, and even with non-software demos that involve many changes to files.

#Tortoisehg set password software

Last summer at the Software Engineering 101 event put on by NimblePros in Cleveland, I saw Kevin Kuebler do a demo using git or Mercurial to iterate from phase of the project he was building to the next.