Package Details: storageexplorer 1.36.2-1

Git Clone URL: https://aur.archlinux.org/storageexplorer.git (read-only, click to copy)
Package Base: storageexplorer
Description: Microsoft Azure Storage Explorer is a standalone app from Microsoft that allows you to easily work with Azure Storage data on Windows, macOS and Linux.
Upstream URL: https://github.com/microsoft/AzureStorageExplorer/releases
Keywords: azure cloud microsoft storage
Licenses: unknown
Provides: storageexplorer
Submitter: XenGi
Maintainer: faultylee
Last Packager: faultylee
Votes: 28
Popularity: 0.000050
First Submitted: 2017-02-23 15:38 (UTC)
Last Updated: 2024-10-31 06:03 (UTC)

Pinned Comments

faultylee commented on 2024-05-28 06:20 (UTC)

The latest update from 1.34.0 is now using .NET Core 8.0 (extra/dotnet-runtime)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

faultylee commented on 2022-05-28 14:09 (UTC)

I've updated to dotnet-runtime, it's v6, seems to work properly locally. There's no more 3.1 out in the wild. Let me know if v6 is giving any issue. Thanks for reporting!

lukaszmoroz commented on 2022-05-27 19:25 (UTC)

dotnet-runtime-3.1 is missing.

faultylee commented on 2021-10-17 01:51 (UTC)

@Soroshi thanks for the feedback. I removed both libgnome-keyring and gnome-keyring and it continue to work. I'm not well verse in this area. I'll pin a note in case anyone having issue I can restore gnome-keyring.

Soroshi commented on 2021-10-15 17:28 (UTC)

I installed this without the libgnome-keyring dependency (it's deprecated anyway) and it is working fine so this doesn't seem to be a hard dependency.

faultylee commented on 2021-09-23 14:35 (UTC)

Since 1.21.0 it's using dotnet-runtime-3.1 from community

faultylee commented on 2020-06-27 03:53 (UTC)

1.14.0 is out and it's now working properly with dotnet-runtime-2.1

faultylee commented on 2020-05-20 03:56 (UTC)

Sorry for the late update. The latest 1.13.1 works with dotnet-runtime > 2.2, please update if you encounter any issues.

armadillo commented on 2020-04-01 14:49 (UTC)

@faultylee - thanks for that - to be frank, I'm not sure why the dotnet package was pulled so quickly - seems to be against the spirit of .net to remove older versions with such haste