Skip to content

Releases: DHancock/WinAppSdkCleaner

Release 1.5.0

18 Aug 07:31
dc134bf
Compare
Choose a tag to compare

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

12 Oct 17:16
7aeb787
Compare
Choose a tag to compare

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

31 Aug 19:09
0f3c23f
Compare
Choose a tag to compare

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

03 May 12:57
af84446
Compare
Choose a tag to compare

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

15 Apr 16:53
788d1fd
Compare
Choose a tag to compare

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

15 Nov 15:29
a0adc3c
Compare
Choose a tag to compare

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.

Version 1.1.1

25 Oct 10:15
c0761ce
Compare
Choose a tag to compare

This is a bug fix release.

  • If the removal of a Windows App SDK times out, cancel the remaining waiting package removal tasks.

While time outs are unlikely, cancelling any outstanding tasks will release the system resources used to wait for the tasks to complete.

Version 1.1.0

15 Oct 10:14
6259c78
Compare
Choose a tag to compare

This version contains numerous code improvements. Notable changes are:

  • There is a new Output tab that displays the Trace messages emitted by the code, without the need to attach a debugger.

  • The searching for SDKs has been optimized. When removing SDKs, the code now uses Package Manager rather that Power Shell.

  • The versions.json file is now an embedded resource. The code will always try to download the online version first, falling back to the embedded version if you're offline.

First release

26 Sep 18:33
c08da03
Compare
Choose a tag to compare

First release of the completed program. The binaries are published single file, framework dependant builds. They are build for .Net 6.0 using WPF. The "versions.json" file isn't esssential, an online version will be loaded by the application. It is used to convert between obscure package versions and human readable WinAppSdk releases.

Note: Windows defender may object to these executables. Not only do they download files, they also spawn processes that execute power shell scripts. In my testing, when installing on a clean machine, Windows defender promptly deleted the executable (that is until I disabled it). I've created this release for reference. It may be better to build your own exe's.