mirror of
https://github.com/microsoft/PowerToys.git
synced 2024-12-04 11:59:07 +08:00
073caffef4
* Unify exe/dll naming - PowerToys.Runner Align naming with other exes - PowerToys Runner -> PowerToys.Runner * Unify exe/dll naming - Microsoft.PowerToys.Common.UI Project name - Microsoft.PowerToys.Common.UI -> Common.UI dll name - Microsoft.PowerToys.Common.UI.dll -> PowerToys.Common.UI.dll * Unify exe/dll naming - Settings Project names - Microsoft.PowerToys.Settings* -> Settings* Dll names - Microsoft.PowerToys.Settings*.dll -> PowerToys.Settings*.dll * Revert file autoformat * [Docs] Update paths to settings projects/files * Fix tests - Update path
1.4 KiB
1.4 KiB
Compatibility with legacy settings and runner
The following must be kept in mind regarding compatibility with settings v1 and runner.
1. Folder Naming structure
- Each of the modules has a folder within the
Local/Microsoft/PowerToys
directory which contains the module configurations within thesettings.json
file. The name of this folder must be the same across settingsv1 and settingsv2. - The name of the settings folder for each powertoy is the same as the
ModuleName
. It is set within each of the viewModel files. This name must not be changed to ensure that the user configurations for each of the powertoys rolls over on update.
2. Communication with runner
- The status of each of the modules is communicated with the runner in the form of a json object. The names of all the powerToys is set in the
EnableModules.cs
file. TheJsonPropertyName
must not be changed to ensure that the information is dispatched properly to all the modules by the runner.
ImageResizer anomaly
All the powertoys have the same folder name as well as JsonPropertyName to communicate information with the runner. However that is not the case with ImageResizer. The folder name is ImageResizer
whereas the JsonPropertyName is Image Resizer
(Note the additional space). This should not be changed to ensure backward compatibility as well as proper functioning of the module.