Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[9.0.100-alpha.1.24070.3] dotnet tool install command get access deny message #38183

Closed
Junjun-zhao opened this issue Jan 23, 2024 · 6 comments
Closed
Milestone

Comments

@Junjun-zhao
Copy link
Member

Junjun-zhao commented Jan 23, 2024

Application Name: globaltools
OS: Windows 10 21H2
CPU: X64
.NET Build Number: dotnet-sdk-9.0.100-alpha.1.24070.3
Also can checking it on https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1943809

Verify Scenarios:

  1. Windows 10 21H2 x64 + dotnet-sdk-8.0.101: Pass
  2. Windows 10 21H2 x64 + dotnet-sdk-9.0.100-alpha.1.24066.1: Pass
  3. Windows 10 21H2 x64 + dotnet-sdk-9.0.100-alpha.1.24070.3: Fail
  4. Windows 10 21H2 x64 + dotnet-sdk-9.0.100-alpha.1.24072.15: Fail
  5. Windows 10 21h2 x64 + dotnet-sdk-8.0.200-win-x64: Fail
  6. Windows 10 21h2 x64 + dotnet-sdk-8.0.102-win-x64: Pass

Issue Description:
When installing dotnet tools with "gti -c install" command, it get access deny error for gti tool installation.

Repro steps:

The machine only has dotnet-sdk-9.0.100-alpha.1.24070.3 installed. And environment variable DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX set as 2.

1.Open command prompt window.
2. Execute "dotnet tool install –g gti" command.
4. Navigate to a local folder with "cd {localfolderpath}" command
7. Execute "gti –c save" command.
8. Execute "gti –c install" command.

Expected Result:
Tools will be installed successfully and "Tool is already installed" message will show if the tools were installed before.

image

Actual Result:

Get access deny error when installing gti tool which had installed before.

image

DotNet Info:

.NET SDK:

 Version:           9.0.100-alpha.1.24070.3
 Commit:            f91d4ca399
 Workload version:  9.0.100-manifests.0d37fe7a

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19045
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\9.0.100-alpha.1.24070.3\

Host:
  Version:      9.0.0-alpha.1.24066.33
  Architecture: x64
  Commit:       dbb335c6ba

.NET SDKs installed:
  9.0.100-alpha.1.24070.3 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 9.0.0-alpha.1.24068.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 9.0.0-alpha.1.24066.33 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 9.0.0-alpha.1.24068.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Findings:

The permissions for the folder path in error message not changed when running with both dotnet-sdk-8.0.101 and dotnet-sdk-9.0.100-alpha.1.24070.3.

@dotnet-actwx-bot @dotnet/compat

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Tools untriaged Request triage from a team member labels Jan 23, 2024
@Junjun-zhao
Copy link
Member Author

The same error occurred on 8.0.200-rtm.24069.25, the above verification scenarios has been updated.

@Junjun-zhao
Copy link
Member Author

@marcpopMSFT @JL03-Yue This issue repro on the latest build for both .NET 9 Preview1 and .NET 8 Servicing, could you please help confirm whether it is a blocker for .NET 9 Preview1 and .NET 8 Servicing?

@JL03-Yue
Copy link
Member

similar to #38354

@JL03-Yue JL03-Yue added this to the 9.0.1xx milestone Apr 4, 2024
@JL03-Yue JL03-Yue removed their assignment Apr 19, 2024
@Junjun-zhao
Copy link
Member Author

@marcpopMSFT @JL03-Yue According the last update, it seems this issue has been moved to .NET 9.0 servicing 9.0.1xx. Could you please help confirm what's the plan for the .NET 8.x issue #38354 ?

@marcpopMSFT marcpopMSFT added the needs team triage Requires a full team discussion label Jun 4, 2024
@marcpopMSFT
Copy link
Member

We'll discuss in triage. Annie has left the team so we do not currently have someone digging into the tools issues anymore. We're short on time for 8.0.4xx and would not fix it in any other 8 sdk.

@marcpopMSFT marcpopMSFT removed the needs team triage Requires a full team discussion label Jun 18, 2024
@Junjun-zhao
Copy link
Member Author

Verified this issue and it has been Fixed on dotnet-sdk-9.0.100-preview.7.24352.8. Hence closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants