aws / aws/aws-toolkit-visual-studio

Cannot launch in WSL2 filesystem

Open
#263 4 comments 0 reactions 0 assignees View on GitHub
bug dotnet-deploy publish
Dominant language
No language data
Stars
135
Forks
37
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
When attempting to use the AWS Toolkit on a project that is located in the WSL2 filesystem (`\\wsl.localhost`) it is unable to find the `.csproj` file.
Error thrown:
```
{"ErrorCode":"FailedToFindDeployableTarget","Message":"Failed to find a valid .csproj or .fsproj file at path \\\\wsl.localhost\\Ubuntu\\home\\\\\\\\.csproj","ProcessExitCode":null}
```

**To Reproduce**
1. Install WSL2 (official docs: https://docs.microsoft.com/en-us/windows/wsl/install).
2. Create a project in the WSL2 filesystem. My case I created a ASP.NET Web API project at `\\wsl.localhost\Ubuntu\home\`.
3. In the Visual Studio editor, right click on the project in the Solution Explorer panel and click "Publish to AWS".
4. This will attempt to load the AWS Toolkit which will eventually throw the error.

**Expected behavior**
I expect the AWS Toolkit to launch as expected.

**Screenshots**
![image](https://user-images.githubusercontent.com/42851426/174398805-3df52c42-7d1f-4d65-b60e-259458da0dc3.png)

**Computer:**

- Windows Version:
Edition Windows 11 Home
Version 21H2
OS build 22000.708

- Visual Studio Version:
Microsoft Visual Studio Community 2022 (64-bit) - Current
Version 17.2.3

- AWS Toolkit for Visual Studio Version:
Version: 1.31.0.0

Contributor guide

Open the contributing guide

Research direction

Reproduce the Publish to AWS flow with an ASP.NET Web API project stored under the mentioned \\wsl.localhost path, then trace the project-target lookup around the reported FailedToFindDeployableTarget error. Done means the AWS Toolkit launches from Solution Explorer and recognizes the project's .csproj file in the WSL2 filesystem.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, csharp, linux
Domain
cloud, devtools, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.