Releases: DHancock/WinAppSdkCleaner
Release 1.7.2
This is primarily bug fix release. It fixes:
- Fixes an issue clicking the cancel button in the confirmation dialog displayed when removing an Sdk.
- Screen readers can now read the contents of the versions list on the Info tab.
- When copying data from the versions list, the data is now sorted correctly.
- When switching to the Sdk tab, the tree is only updated once irrelevant of how many times the data was automatically refreshed.
In addition, several code improvements have been made notably:
- For consistency, a confirmation dialog is presented when removing any Sdk, not just when the Sdk contained dependant apps.
- When copying items from the Sdk tree, the copied data now only contains valid powershell commands.
Release 1.7.1
This is a bug fix release. The following bug has been fixed:
- The Sdk tree view is now updated after removing an Sdk.
(this was a regression introduced in version 1.7.0)
Release 1.7.0
This release includes two changes:
- The UI has been ported to WinUI.
- The application now has an installer.
Release 1.6.0
The release contains a couple of changes that may improve the application's start up time:
- The versions json array, downloaded from this repository is now compressed.
- The tasks that download the versions and query the computers installed packages are now run in parallel.
Other changes include:
- The self contained .Net version is now 9.0
- Numerous small code improvements.
Edit: I've replaced the self extracting exe files with zip archives. Windows Defender falsely identified them as containing trojans when the file had the zone identifier alternate stream indicating that the exe was downloaded (local published builds work fine).
Release 1.5.0
This release contains two changes to how Win App Sdk packages are displayed:
- Convert package names to either DDLM, Main, Framework or Singleton.
- Convert package versions to the Win App Sdk release version.
Release 1.4.2
This is a bug fix release.
-
If a package dependency error occurred when removing a WinAppSdk, the code attempted to get further information to aid resolving the problem. Unfortunately that involved calling an api that requires elevation. When running as a normal user, an exception resulted in no trace output being produced so that there was no indication that an error had occurred.
-
A confirmation dialog is now shown before attempting to remove a WinAppSdk that has dependent apps.
Release 1.4.1
This is a bug fix release.
- WinAppSdk packages signed by the system were incorrectly included in the search results. It now only list sdks installed as dependencies of store apps or that were manually installed.
Release 1.4.0
This release adds a couple of new features:
-
The app will now attempt to load the WinAppSdk version data file "versions.json" from the same directory as the app. If it isn't present then it falls back to downloading the online version in this repository. If the net is down, it will use a copy embedded in the apps resources.
-
When running elevated, the search results will now omit sdk packages that have a package install state that doesn't equal Installed. This will filter out packages that have been marked as staged by the package manager when the package has been removed for all users. Trace output will detail omitted packages.
Release 1.3.0
This release adds a new feature:
- A new tab has been added which displays the relationship between WinAppSdk releases and it's associate package version.
Release 1.2.0
This release adds a couple of new features:
-
The sdk list now indicates if a Win App Sdk release has any dependent applications (or packages) that are not Win App Sdk packages. The count of these applications is shown in red next to the Win App Sdk name.
-
The sdk list is now rebuild automatically each time the application becomes the foreground application.