How to Copy Settings of Double Commander to another Computer

  1. Under Configuration/Options/Configuration, if the location of configuration files is not set to user home directory, change it to user home directory. You may set this back afterwards.
  2. Check all the checkboxes under Save on exit
  3. Close Double commander. Only when closing, all of the configuration files are saved.
  4. All the config files are now in the user home directory, under doublecmd.
  5. Copy these files.

You can even copy the files from Windows to Linux.

Double Commander: Less Known Features

I love Double Commander (DC) as a two-pane file manager and have already written about its basic features, how to add 7z support and some svn woes.

But DC has got some advanced features which you maybe wouldn’t expect.

  • Under Files-Multi Rename it has got a tool with which you can do a rule-based rename of many files easily. Very useful e.g. to rename songs downloaded from Amazon.
  • You can create symbolic and hard filesystem links. (Files-…)
  • Under Files-Compare by Content you’ll find a diff tool. But you could also configure DC to use the diff tool you prefer.
  • You can use DC as a FTP-client. When using this feature the first time, do this:
    1. Select Commands-Open VFS List.
    2. One of the panes then will show the entries FTP and Network.
    3. Double-click on FTP, then it will show Add connection and Quick connection.
    4. Double click one of them to add a connection.

DC is extremely configurable and extensible. Some examples.

  • The toolbar is fully configurable:
    1. Go to Configuration-Options-Toolbar.
    2. Click Insert new button.
    3. Select an internal command from the combobox or create an external command. You can use anything you want as a command and you can pass parameters like the currently selected file or path to it.
    4. Add a tooltip, icon and hotkey as you like.
  • You can connect file extensions with commands and hotkeys. For example, I as a software developer often need to know the version of a certain dll.
    So I connected the F3 key with a viewer for the dll version like this:

    1. Open Options dialog, select node File associations.
    2. Under File types select Add and add file type dll.
    3. Under Extensions select Add and type in dll.
    4. Under Actions select Add and then click the + and select View. This relates to the View command or cm_View in the DC.
    5. Under Commad select the + on the right and there Run in terminal (as my version reading program is a command line tool). Then select full path under the +. Resulting is a command like {!SHELL} version.exe %p

    Now, when a dll is highlighted and I hit F3, its complete version info is shown. Much easier and faster than right-click-properties-details.

  • You can color files according to their types: Configuration-Options-Colors-File types
  • All hotkeys are configurable: Configuration-Options-Keys-Hot keys

Add ASP.NET Masterpage Afterwards

When you’ve got some existing ASP.NET pages and you later on want to add a common masterpage, do this:

Master Page

  1. Create a masterpage, e.g. Management.Master.
  2. Add the sub pages’ comon controls to the master.
  3. In the Management.Master, add ContentPlaceHolder items for head and body:
<asp:ContentPlaceHolder ID="CphHead" runat="server" />
<asp:ContentPlaceHolder ID="CphBody" runat="server" />

Sub Page

Do the following in the subpage.aspx:

  1. Add masterpagefile to page level directive:
    <%@ Page ... MasterPageFile="Management.Master"
  2. Remove the <!DOCTYPE>, <html>, <form> and </form>, </html> tags.
  3. Replace the <head> tag by the <asp:Content...> tag respecting the link to the ContentPlaceHolder via ID and ContentPlaceHolderID, like this:
<asp:Content ID="Cont1" ContentPlaceHolderID="CphHead" runat="server">
    // former head content goes here
  1. Likewise replace the body tag by the tag:
<asp:Content ID="Cont2" ContentPlaceHolderID="CphBody" runat="server">
    // former body content goes here

Sub Page Easy

If you’ve got nothing than the <title> tag inside of the <head> section, it is a bit easier:

  1. Add masterpagefile and title to page level directive:
    <%@ Page ... MasterPageFile="Management.Master" Title="Subpage"
  2. Remove the <head> section.
  3. Replace the <body> tag by the <asp:Content...> tag respecting the link to the ContentPlaceHolder via ID and ContentPlaceHolderID, like this:
<asp:Content ID="Cont1" ContentPlaceHolderID="CphBody" runat="server">
    // former body content goes here