aws / aws/aws-toolkit-visual-studio

VisualStudio Publish - fails when nuget added to global tooling

Open
#89 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
135
Forks
37
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
when a nuget repo is added to VisualStudio via the package management (ie. globally) and you perform a publish using the AWS tooling fails to build with a **401 error**. however building using VisualStudio works without issue.

**To Reproduce**
create a lambda project
add a global nuget repo using VisualStudio
add a reference to the project from the added nuget repo
right-click the project select deploy

**Expected behavior**
project should build and deploy as normal

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure with a Lambda project, a globally added NuGet repository, and a project reference from that repository, then use Visual Studio's right-click Deploy flow. Compare the AWS tooling publish build with a normal Visual Studio build and trace where the 401 occurs. Done means the project builds and deploys normally with the global repository configured.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
build-system, cloud, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.