Associating a file extension with your application on Windows

In some cases, your fantastic application needs to be opened with just a double-click on a file with an extension associated with it. This is the case with MS Word, MS Excel, and many other well-known pieces of software. If you have a file generated with a program, double-click on the file and the program that generated the file will bring up pointing to that file. So, if you click on a mywordfile.docx file, MS Word will be opened and the mywordfile.docx file's content will be shown. This is what we'd like to do in this recipe. The association can be useful also when you have multiple configurations for a program. Double-click on the ConfigurationXYZ.myext file and the program will start using that configuration.

Getting ready

The hard work is done by the operating system itself. We have to instruct Windows to provide the following information:

The file extension to associate
The description of file type (this will be shown by Windows Explorer describing the file type)
The default icon for the file type (in this recipe, we'll use the application icon itself, but it is not mandatory)
The application that we want to associate

Let's start!

How to do it…

Create a new VCL application and drop two TButton components and a TMemo component. Align all the buttons as a toolbar at the top of the form and the memo to all the remaining form client area.
The button on the left-hand side will be used to register a file type while the button on the right-hand side will be used to unregister the association (cleaning the registry).
We have to handle some MS Windows-specific features, so we need some Windows-related units. Under the implementation section of the unit, write this use clause:
```
uses System.Win.registry, Winapi.shlobj, System.IOUtils;
```

In the implementation section, we need two procedures to do the real work; so just after the uses clause, put this code:

procedure UnregisterFileType(
   FileExt: String; 
   OnlyForCurrentUser: boolean = true);
var
  R: TRegistry;
begin
  R := TRegistry.Create;
  try
    if OnlyForCurrentUser then
      R.RootKey := HKEY_CURRENT_USER
    else
      R.RootKey := HKEY_LOCAL_MACHINE;

    R.DeleteKey('\Software\Classes\.' + FileExt);
    R.DeleteKey('\Software\Classes\' + FileExt + 'File');
  finally
    R.Free;
  end;
  SHChangeNotify(SHCNE_ASSOCCHANGED, SHCNF_IDLIST, 0, 0);
end;

procedure RegisterFileType(
   FileExt: String; 
   FileTypeDescription: String;
   ICONResourceFileFullPath: String;
   ApplicationFullPath: String;
   OnlyForCurrentUser: boolean = true);
var
  R: TRegistry;
begin
  R := TRegistry.Create;
  try
    if OnlyForCurrentUser then
      R.RootKey := HKEY_CURRENT_USER
    else
      R.RootKey := HKEY_LOCAL_MACHINE;

    if R.OpenKey('\Software\Classes\.' + FileExt, 
         true) then begin
      R.WriteString('', FileExt + 'File');
      if R.OpenKey('\Software\Classes\' + FileExt + 'File', 
               true) then begin
        R.WriteString('', FileTypeDescription);
        if R.OpenKey('\Software\Classes\' + 
         FileExt + 'File\DefaultIcon', true) then
        begin
          R.WriteString('', ICONResourceFileFullPath);
          if R.OpenKey('\Software\Classes\' + 
               FileExt + 'File\shell\open\command', 
                true) then
            R.WriteString('', 
               ApplicationFullPath + ' "%1"');
        end;
      end;
    end;
  finally
    R.Free;
  end;
  SHChangeNotify(SHCNE_ASSOCCHANGED, SHCNF_IDLIST, 0, 0);
end;

These two procedures allows us to register (and unregister) a file type considering only the current user or all the machine users. Note that if you want to register the association for every user, write your data to the following location:
```
HKEY_LOCAL_MACHINE\Software\Classes
```
If you want to register the association for the current user only, write your data to the following location:
```
HKEY_CURRENT_USER\Software\Classes
```
On the newest Windows versions, you need admin rights to register a file type for all the machine users. The last line of the procedures tells Explorer (the MS Windows graphic interface) to refresh its setting to reflect the changes made to the file associations. As a result, for instance, the Explorer file list views will be updated.

We've almost finished. Change the left-hand side button name to btnRegister, the right-hand side button name to btnUnRegister, and put the following code on their onclick event handlers:

procedure TMainForm.btnRegisterClick(Sender: TObject);
begin
  RegisterFileType(
    'secret',
    'This file is a secret',
    Application.ExeName,
    Application.ExeName,
    true);
  ShowMessage('File type registered');
end;

procedure TMainForm.btnUnRegisterClick(Sender: TObject);
begin
  UnregisterFileType('secret', true);
  ShowMessage('File type unregistered');
end;

Now, when our application is invoked with a double-click, we'll get the file name as a parameter. It is possible to read a parameter passed by Windows Explorer (or command line) using the ParamStr(1) function. Create a FormCreate event handler using the following code:
```
procedure TMainForm.FormCreate(Sender: TObject);
begin
  if TFile.Exists(ParamStr(1)) then
    Memo1.Lines.LoadFromFile(ParamStr(1))
  else
  begin
    Memo1.Lines.Text := 'No valid secret file type';
  end;
end;
```
Now the application should be complete. However, a nice integration with the operating system requires a nice icon as well. In the code, the associated file will get the same icon as the main program, so let's change our default icon by navigating to Project | Options | Application and choose a nice icon. Click on the Load Icon button, choose an ICO file, and then select the third item from the resultant dialog:
Changing the default application icon for our application
Now, create some text files with our registered .secret extension.
These files will appear with the default Windows icon, but in some seconds, they will have a brand new icon.
Run the application by hitting F9 (or navigate to Run | Run).
Click on the btnRegister button and close the application. Now the files get a new icon, as shown in the following screenshot:
The files in Windows Explorer before and after having registered the .secret extension
Now, with the application not running, double-click on the .secret file. Our program will be started by Windows itself, using the information stored in the registry about the .secret file, and we'll get this form (the text shown in the memo is the text contained into the file):
Our application, launched by the operating system, while showing the content of the file

There's more...

One application can register many file types. In some cases, I've used this technique to register some specific desktop database files to my application (FirebirdSQL Embedded database files or SQLite database files). So a double-click on such database file (registered with an application-specific extension) was actually a connection to that database.

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Delphi Cookbook

By : Daniele Teti

Delphi Cookbook

By: Daniele Teti

Overview of this book

Associating a file extension with your application on Windows

Getting ready

How to do it…

There's more...

Delphi Cookbook

By : Daniele Teti

Delphi Cookbook

By: Daniele Teti

Overview of this book

Associating a file extension with your application on Windows

Getting ready

How to do it…

There's more...

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access