vsfeedback: restore not working with project.json file (due to v1 project.lock.json file) #4570

Closed
rrelyea opened this Issue Feb 10, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@rrelyea
Contributor

rrelyea commented Feb 10, 2017

internal vsfeedback: 747014

New project was added to our source and the appropriate packages specified in the project.json. These references do not properly show up in the "References" for the project. Attempting to open Nuget Manager Console results in an error so I can't perform a manual restore.

found using 26124.2 build.
internal user is contactable via email.

@rrelyea rrelyea added the Investigate label Feb 10, 2017

@rrelyea rrelyea added this to the 4.0 RTM milestone Feb 10, 2017

@zhili1208 zhili1208 self-assigned this Feb 10, 2017

@zhili1208

This comment has been minimized.

Show comment
Hide comment
@zhili1208

zhili1208 Feb 10, 2017

Contributor

I think this is related to project.lock.json v1, talked with internal user, he can't test it now, will test it next week

Contributor

zhili1208 commented Feb 10, 2017

I think this is related to project.lock.json v1, talked with internal user, he can't test it now, will test it next week

@rrelyea rrelyea changed the title from vsfeedback: restore not working with project.json file to vsfeedback: restore not working with project.json file (due to v1 project.lock.json file) Feb 16, 2017

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

@emgarten

This comment has been minimized.

Show comment
Hide comment
@emgarten

emgarten Nov 9, 2017

Contributor

Thank you very much for your feedback. We appreciate you for letting us know about the problem you encountered, but we haven’t been able to fully investigate your problem as our focus has been on other problem reports. If there are more community feedback on this, then we'll re-evaluate this.

Contributor

emgarten commented Nov 9, 2017

Thank you very much for your feedback. We appreciate you for letting us know about the problem you encountered, but we haven’t been able to fully investigate your problem as our focus has been on other problem reports. If there are more community feedback on this, then we'll re-evaluate this.

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