Azurestorageexplorer: dotnet runtime 2.2 is EOL

Created on 25 Mar 2020  路  10Comments  路  Source: microsoft/AzureStorageExplorer

Storage Explorer Version: 1.12.0
Build Number: 20200116.10
Platform/OS: Arch Linux
Architecture: x64
Regression From: N/A

Bug Description

Since dotnet-runtime 2.2 is already EOL, is there plan to upgrade the dependency to 3.1?

Steps to Reproduce

Currently it still require dotnet runtime 2.2. I've tried removing 2.2 installing only 3.1, it doesn't work for me.
image

Additional Context

I'm the maintainer for Storage Explorer in AUR (Arch User Repo) (https://aur.archlinux.org/packages/storageexplorer/). dotnet-runtime-2.2 has been removed from AUR so I'm raising it here since I can't find anyone else mentioning the same problem.

merged

All 10 comments

Hey @faultylee , thank you for the heads-up on this. I've brought this up to team which owns the component used by storage explorer that uses .net core.

In the mean time, unfortunately I don't have a workaround for you. Do you know who removed 2.2 from the AUR?

I have this issue also. same message as @faultylee

It works now with 3.1.3

Hey @faultylee we're actually going to try switching to .net core 2.1 in our next release. I hope this doesn't muck up your workaround.

No worries @MRayermannMSFT , thanks for the heads up

@faultylee would you be up for installing a private build and letting me know if it works for you? We also had to make a change to the structure of the tar package to support Electron 8, and I'd be interested to have both that and the .NET change validated by a real user.

@MRayermannMSFT sure. I usually do a quick test locally before I push the update to AUR.

@faultylee awesome! Again though, this is not meant to be pushed to the AUR. I'm just giving it to you to see if it solves the .net core 2.2 issue (by working with .net core 2.1) and to see if our change to what's inside the .tar.gz works out ok. I do not recommend using this against prod data or anything like that. Simply validate the changes. 馃構 Ok with that out of the way, here's a link to the build: https://storageexplorerpublish.blob.core.windows.net/privatebuilds/1.14-linux/StorageExplorer-linux-x64.tar.gz

@MRayermannMSFT totally understand :smiley: .I just tested, it worked with dotnet-runtime-2.1 without any issue. I also tested with only dotnet-runtime-3.1 installed and it complained about missing 2.1. I looked around some tables and blobs all loads fine. Is there anything specific that you want me to test?

image

I noticed some console error from electron when I browse around, probably harmless

- An error has occurred.  Please try the operation again.
- You can search for the error online: JSPlugin.4002
- No attribute loader for: $cloudName
- No attribute loader for: accessTier
- No attribute loader for: accountKind
- No attribute loader for: connectionType

Btw, I did some test with 1.13.1 before installing 1.14.0, I just realized it stuck at the Loading spinner forever, the tree didn't load. I believe I didn't test it properly before this. I saw this error in electron's console

Hub Controller process exited prematurely with exit code 150

No one complain in AUR, so not sure how many has updated to 1.13.1 though

Ya, I have a feeling .net core 3.1 doesn't actually work with 2.x. From what I have read online, it is not backwards compat. Anyways, ok cool. I'm glad we were able to finally get onto an EOL version! You'll see this change roll out in our 1.14 release. Thanks for helping to verify. :)

Was this page helpful?
0 / 5 - 0 ratings