Feature Request: Auto-re-assign file associations on new computer to NP++

[Thomas]

To understand the problem assume the following steps:

1.) NP++ is setup on computer 1 (e.h. Desktop computer).
2.) In Preferences-->File Associations all user preferred file associations are successfully set (e.g. for .txt)
3.) The full NP++ installation folder (including the preferences in the .xml files) is copied
to an USB flash drive
4.) the justc opied NP++ installation folder is copied from USB flash drive to the hard disc of another computer 2 (e.g. Notebook)
5.) Now lets go again to menu
Preferences-->File Associations
..... and no file associations are set.

So NP++ should automatically check at startup if all file associations are already set.
If there are differences between current Registry file associations on computer and NP++ *.xml settings then NP++ should prompt the user: "Update file associations on this computer YES/NO"

Can this be added in the next release?

Thank you
Thomas

[Thomas]

Hi Thomas,

I think the issue is related to the location where the configuration is stored.

All Notepad++ configuration items are stored:

1. in %AppData%\Notepad++
2. in the Notepad++ installation directory

The choice depends on you installation method. If you choose "Do not use AppData directory" during installation you have the second case (additionally indicated by an empty file called doLocalConf.xml residing in the installation directory). If you do not have a doLocalConf.xml file in your installation directory you must copy the %AppData%\Notepad++ directory hierarchy as well.

As file associations are not part of Notepad++ but part of Windows they will be stored in the registry. Therefore the file association cannot be copied by copying a Notepad++ installation. This is true even you can view the file association in the Notepad++ option dialog.

If you want to copy the file associations you must search for a Windows tool which can do this.

Regards,
Thomas

[Thomas]

Yes I know, file associations are stored outside of NP++.
But they can be setup (=created in Registry) by NP++

As I said in my initial posting:
NP++ can check in an appropriate, own .xml file whether the user has defined some file associations in the past. These user defined must be stored in an .xml file.
If NP++ finds some of them and they differ from the ones in the Registry
then NP++ could (after a user prompt) re-create them in Registry.
This is an NP++ driven approach.

If the user defines file associations outside of NP++ they the are lost (e.g. after Window crash) or they should be stored in NP++ own file association *.xml.

This way file associations in NP++ and in Registry are always corresponding

[AZJIO]

Also add a library of icons to files differ in appearance