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

NuGet ProjectSystemCache error when adding package in vsix package #4545

Closed
rrelyea opened this Issue Feb 9, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@rrelyea
Contributor

rrelyea commented Feb 9, 2017

vsfeedback 784047 filed with RC3.1 | https://developercommunity.visualstudio.com/content/problem/16659/nuget-projectsystemcache-error-when-adding-package.html

(please consider that the user may had added the package via PackageRef or Packages.config)

I have an existing solution that builds in VS2017RC. It is a VSIX project and I'm trying to add the Microsoft.VSSDK.BuildTools package to it. When I add the package NuGet throws an exception saying value cannot be null or an empty string.

System.ArgumentException: Value cannot be null or an empty string.
Parameter name: name
at NuGet.PackageManagement.VisualStudio.ProjectSystemCache.ContainsKey(String name)
at NuGet.PackageManagement.VisualStudio.VSSolutionManager.RemoveEnvDTEProjectFromCache(String name)
at NuGet.PackageManagement.VisualStudio.VSSolutionManager.d__57.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.PackageManagement.UI.NuGetUI.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.PackageManagement.UI.UIActionEngine.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at NuGet.PackageManagement.UI.UIActionEngine.d__7.MoveNext()

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Feb 9, 2017

Contributor

Likely #4433 -- currently in 4.0.1
Please take a peek to confirm. Want to think more if we should be taking 4433 in RTM.

Contributor

rrelyea commented Feb 9, 2017

Likely #4433 -- currently in 4.0.1
Please take a peek to confirm. Want to think more if we should be taking 4433 in RTM.

@CoolDadTx

This comment has been minimized.

Show comment
Hide comment
@CoolDadTx

CoolDadTx Feb 9, 2017

I'm no longer having this issue in RC4-26206.0. The packages are being stored in packages.config.

CoolDadTx commented Feb 9, 2017

I'm no longer having this issue in RC4-26206.0. The packages are being stored in packages.config.

@rohit21agrawal

This comment has been minimized.

Show comment
Hide comment
@rohit21agrawal

rohit21agrawal Feb 9, 2017

Contributor

@rrelyea @CoolDadTx good to close this out then?

Contributor

rohit21agrawal commented Feb 9, 2017

@rrelyea @CoolDadTx good to close this out then?

@CoolDadTx

This comment has been minimized.

Show comment
Hide comment
@CoolDadTx

CoolDadTx Feb 9, 2017

Fine with me.

CoolDadTx commented Feb 9, 2017

Fine with me.

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