[vsfeedback] While using Package Manager Console, the 'Enter' key may not work at times. #4204

Closed
rrelyea opened this Issue Jan 5, 2017 · 10 comments

Comments

Projects
None yet
7 participants
@rrelyea
Contributor

rrelyea commented Jan 5, 2017

[anangaur] Changed the title from "[vsfeedback] pmc will throw null ref when there is project which contains v1 project.lock.json"

vsfeedback item: 718874 (talk to me about how to look up internally)
https://developercommunity.visualstudio.com/content/problem/6350/package-manager-console-freezes.html

customer title: package manager console freezes
Tools -> Nuget package manager -> Package Manager Console
prompt appears - but return key does not do anything
e.g. try pwd or dir or ls command - but no response
Then error on trying to close down Visual Studio - see attachment

@nkolev92

This comment has been minimized.

Show comment
Hide comment
@nkolev92

nkolev92 Jan 9, 2017

Member

I cannot repro this.
Seems like the issue is a month old, so it might have been fixed in the meanwhile?

Member

nkolev92 commented Jan 9, 2017

I cannot repro this.
Seems like the issue is a month old, so it might have been fixed in the meanwhile?

@rrelyea rrelyea modified the milestones: 4.0 RTM, 4.0 RC3 Jan 10, 2017

@dg2k

This comment has been minimized.

Show comment
Hide comment
@dg2k

dg2k Jan 17, 2017

Happened to me a moment ago. The keyboard doesn't respond to the Console window at all. Mouse interaction seems OK because I can place the cursor anywhere in the pmc window.
If this is a hint, there is red text prompt on the last two lines reading:

Value cannot be null.
Parameter name: key

Exiting VS2017RC and re-launching it cured the problem and I can interact with the pmc.

dg2k commented Jan 17, 2017

Happened to me a moment ago. The keyboard doesn't respond to the Console window at all. Mouse interaction seems OK because I can place the cursor anywhere in the pmc window.
If this is a hint, there is red text prompt on the last two lines reading:

Value cannot be null.
Parameter name: key

Exiting VS2017RC and re-launching it cured the problem and I can interact with the pmc.

@rrelyea rrelyea modified the milestones: 4.0.1, 4.0 RTM Jan 19, 2017

@nkolev92

This comment has been minimized.

Show comment
Hide comment
@nkolev92

nkolev92 Jan 28, 2017

Member

Happened to me just now.
Opening our NuGet.Clients.sln in VS17 just after the migration reproduces the problem as of 4.0.0.2252

Member

nkolev92 commented Jan 28, 2017

Happened to me just now.
Opening our NuGet.Clients.sln in VS17 just after the migration reproduces the problem as of 4.0.0.2252

@rrelyea rrelyea modified the milestones: 4.0 RTM, 4.0.1 Feb 2, 2017

@rrelyea rrelyea added Investigate and removed Type:Bug labels Feb 2, 2017

@nkolev92

This comment has been minimized.

Show comment
Hide comment
@nkolev92

nkolev92 Feb 2, 2017

Member

Potential workaround:

  1. Open VS
  2. Open PMC prior to opening a solution
Member

nkolev92 commented Feb 2, 2017

Potential workaround:

  1. Open VS
  2. Open PMC prior to opening a solution
@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Feb 2, 2017

Contributor

Balancing to @zhili1208

Contributor

rrelyea commented Feb 2, 2017

Balancing to @zhili1208

@rrelyea rrelyea assigned zhili1208 and unassigned nkolev92 Feb 2, 2017

@rrelyea rrelyea modified the milestones: 4.0.1, 4.0 RTM Feb 2, 2017

@zhili1208 zhili1208 changed the title from [vsfeedback] cannot press enter in pmc to [vsfeedback] pmc will throw null ref when there is project which contains v1 project.lock.json Feb 2, 2017

@zhili1208

This comment has been minimized.

Show comment
Hide comment
@zhili1208

zhili1208 Feb 2, 2017

Contributor

the issue here is PMC is reading project.lock.json for running ps script during initialization, if the version of project.lock.json is v1, package type of all packages are null. nuget will throw null ref and user can't use pmc

Contributor

zhili1208 commented Feb 2, 2017

the issue here is PMC is reading project.lock.json for running ps script during initialization, if the version of project.lock.json is v1, package type of all packages are null. nuget will throw null ref and user can't use pmc

@rrelyea rrelyea modified the milestones: 4.0.2, 4.0.1 Feb 9, 2017

@mrueedi

This comment has been minimized.

Show comment
Hide comment
@mrueedi

mrueedi May 28, 2017

So a solution for me was to close VS and rename or delete the old v1 project.lock.json. After starting VS again, a v2 version of the file was generated...

mrueedi commented May 28, 2017

So a solution for me was to close VS and rename or delete the old v1 project.lock.json. After starting VS again, a v2 version of the file was generated...

@emgarten emgarten modified the milestones: 4.0.2, 4.4 Jul 14, 2017

@anangaur

This comment has been minimized.

Show comment
Hide comment
@anangaur

anangaur Oct 2, 2017

Member

@zhili1208 , @rrelyea Is this fixed in 4.4? If so, can you close this? This has been a known issue since VS 15.3 RTW and I would have to keep it or remove it from 15.4 release notes based on whether this was fixed or not.

Member

anangaur commented Oct 2, 2017

@zhili1208 , @rrelyea Is this fixed in 4.4? If so, can you close this? This has been a known issue since VS 15.3 RTW and I would have to keep it or remove it from 15.4 release notes based on whether this was fixed or not.

@anangaur anangaur changed the title from [vsfeedback] pmc will throw null ref when there is project which contains v1 project.lock.json to [vsfeedback] While using Package Manager Console, the 'Enter' key may not work at times. Oct 2, 2017

@zhili1208 zhili1208 modified the milestones: 4.4, 4.5 Oct 17, 2017

@zhili1208

This comment has been minimized.

Show comment
Hide comment
@zhili1208

zhili1208 Oct 17, 2017

Contributor

@anangaur few customers hit this, please remove it from know issues, close it as won't fix, we should be considering a better plan for moving to next version in the future.

Contributor

zhili1208 commented Oct 17, 2017

@anangaur few customers hit this, please remove it from know issues, close it as won't fix, we should be considering a better plan for moving to next version in the future.

@zhili1208 zhili1208 closed this Oct 17, 2017

@anangaur

This comment has been minimized.

Show comment
Hide comment
@anangaur

anangaur Oct 20, 2017

Member

Thanks @zhili1208 This will not show up in 15.5 release notes.

Member

anangaur commented Oct 20, 2017

Thanks @zhili1208 This will not show up in 15.5 release notes.

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