microsoft / microsoft/AzureStorageExplorer

Better error needed when .NET not installed

Open
#9,196 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version

1.43.0 (also other versions)

Regression From

No response

Architecture

x64

Storage Explorer Build Number

No response

Platform

All

OS Version

Windows

Bug Description

The Azure Storage Explorer application tries to install .NET . If it cannot (say for a user without admin privileges), it will error and say something along the lines of "not all functionality will work" but finished.

This is misleading, because as far as I can tell Azure Storage Explorer requires .NET to complete startup. Without .NET, it will get stuck with a "Loading" spinning in the Explorer pane.

The application should either fail during the install because of .NET missing, error on startup about .NET missing instead of getting stuck, or remove this .NET dependency if it was intended for the application to launch.

Ideally for my use case with researchers, the application would offer to use the non-admin .NET installer if it can't install otherwise, but I don't expect that is a solution that will be acceptable.

Resource Types

No response

Authentication Method

None

Connection Type

None

Steps to Reproduce
  1. Install Storage Explorer without admin privlidges
  2. Have .NET fail
  3. Launch storage explorer, watch it never completely load
Actual Experience

Described above

Expected Experience

No response

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Windows, non-admin installation described in the issue and observe the .NET installation failure and subsequent loading state. Trace the startup path that handles missing .NET and determine which behavior is intended: a clear startup error, a failed installation, or continued launch without the dependency. Done means the missing-.NET case no longer leaves the application stuck on Loading and the outcome is communicated accurately.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.