UniGetUI (formerly WingetUI) 3.1.0 alpha 0

[marticliment]

IMPORTANT:
This is the first development release to implement the UniGetUI rebranding.
Instaling this release will automatically migrate settings and other data to new folders (WingetUI -> UniGetUI), so rolling back to older versions of WingetUI may cause settings to be reset.

Changes

• Rebranding from WingetUI to UniGetUI
  • Any occurrences of WingetUI have been changed to UniGetUI
  • Settings have been moved from user profile to AppData\Local
• Improvements to the package managers
  • All dotnet-based package managers do call the nuget api when possible. This dramatically speeds up find packages and loading package details, as well as provides more reliability.
  • All dotnet-based packages will load the official package icon
  • WinGet implements the WinGet COM Api, for improved performance and reliability. WinGet packages do not show elypsis (...) anymore.
  • Microsoft Store packages (currently msix only) will show icons and screenshots
  • The icon caching mechanism has been rebuilt from the grounds up, providing more compatibility with Widgets for WingetUI
• Improvements to Software pages
• Better search experience on the Discover Software page
• Refactoring. Lots of refactoring
• Other improvements and internal changes.

SHA256: 0ec58bc34ff63f0bc1904fe88e8cdd247a2348e259ce8394911979aef5477281

---

This discussion was created from the release UniGetUI (formerly WingetUI) 3.1.0 alpha 0.

[Mertsch]

Wow, this is amazing! Keep up the good work.

[Jonathing]

Loving the work being put into this project. Keep on rocking.

I kind of think UniGet would be a better name than UniGetUI since the "UI" part was born from this program being a UI for Winget. Since it is more of its own thing now, I think it's a little redundant.

[aggietallboy]

Thank you for the new update!! Installing and playing with it now.

Did you get the load package from command line capability added in this release?

[marticliment]

No. While the respective Feature Request is open the feature has not been implemented yet

[ipisano]

Can anyone check if scoop works here? I can't get it to work with latest stable, it's installed in my system and works from terminal but doesn't get recognized by WingetUI. (I already posted about this in the relevant issue thread)

[Schielegerhard]

Scoop works, but I have to deactivate and reactivate it manually in the settings every time I start UniGetUI. Only then is Scoop recognized. The same applies to npm.

[J-HS-L]

Compared to the stable release, how flaky is this.
Is it still relatively stable/safe? TY/BR!

[marticliment]

It depends. It might work 100% or it might always crash. This is why it is an alpha

[MAX4ARCH]

Works great, the only issue I got - it doesnt see my chocolatey packages installed.

[marticliment]

Please check this two folders:

• %userprofile%\AppData\Local\Programs\WingetUI\choco-cli\
• %userprofile%\AppData\Local\UniGetUI\Chocolatey\

Are there any contents there?

[MAX4ARCH]

Please check this two folders:

• %userprofile%\AppData\Local\Programs\WingetUI\choco-cli\
• %userprofile%\AppData\Local\UniGetUI\Chocolatey\

Are there any contents there?

Yes, I even tried to delete them, because I use system chocolatey. Reverted to stable for myself meanwhile. Again, thank you for your great effort and fast replies!)

[MAX4ARCH]

finally found what cause that issue, choco was only in administrator path, when I added to user path, everything become to be shown in unigetui. (v 3.1.0)

[Janzzze]

Found a couple of places where it's not rebranded to UniGetUI

Anywhere Windows displays the name its still WingetUI

The executable is still WingetUI.exe

[marticliment]

Thanks for the report.

Please note that this is still an alpha release