At least all the config files should be compatible between 32bit and 64bit which is good.Using the windows shell to edit a file with Notepad++ might not always use the one they want.
If 32bit and 64bit are allowed to be installed simultaneously:.Either way, I think a couple of things have to be considered: That might be a good solution (possibly ask/warn the user?). How about remove automatically the 32-bit version while installing 64-bit version and vice versa? I’m curious how other applications work that have both 32bit and 64bit installations. Maybe ask if you want to preserve you current session and history data? It would be nice if the 64-bit installer handled an existing config.xml and/or session.xml file differently.
Note I was careful with what I copied and where I pasted. Then I opened the old config.xml and session.xml and copied in the session data and history data into the new 64-bit installed ones which worked fine and didn’t seem to trouble NPP. On another machine I copied the existing 32-bit NPP config.xml and session.xml files to a temporary location and then removed 32-bit NPP before installing 64-bit NPP. In other words, both 32-bit and 64-installs point to the same C:\Users\%username%\AppData\Roaming\Notepad++ path so running either uninstall will remove all of these files. I would have preferred to keep my history and session data. located in C:\Users\%username%\AppData\Roaming\Notepad++. Not necessarily a problem but when you then uninstall the 32-bit version it also removes the various configuration files like config.xml, session.xml, etc. The 32-bit install ends up in C:\Program Files (x86)\Notepad++ and the 64-bit install ends up in C:\Program Files\Notepad++ as you would expect. Installing 64-bit on 64-bit Windows with 32-bit Notepad++ already installed ends up with two installations because the 64-bit installer doesn’t check to see if there is already a 32-bit version installed.
0 kommentar(er)
