Skip to content
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

Put dependency diagnostics in the lock file #1599

Closed
davidfowl opened this issue Oct 17, 2015 · 4 comments
Closed

Put dependency diagnostics in the lock file #1599

davidfowl opened this issue Oct 17, 2015 · 4 comments
Labels
Platform:Xplat Type:DCR Design Change Request
Milestone

Comments

@davidfowl
Copy link
Member

Today the DNX has a rich set of diagnostics that are computed from the lock file on compile and inside of design time host (and it should also do that after restore is complete but it doesn't today). These diagnostics are super useful and are used for things like:

  • Unresolved dependencies
  • Mismatched dependencies
  • Incompatible dependencies

If we stored all of the diagnostics in the lock file, they could be shown by any tool that consumed the lock file. We also introduced a bunch of error codes so that tools like visual studio could link to help pages about the topic.

@yishaigalatzer yishaigalatzer modified the milestone: Client-VNext Oct 23, 2015
@harikmenon harikmenon modified the milestones: Client-VNext, Future Apr 19, 2016
@rrelyea rrelyea added Type:DCR Design Change Request Platform:Xplat labels Jun 9, 2016
natidea added a commit to natidea/sdk that referenced this issue Jan 4, 2017
…et (but still report them in solution explorer). Long term, NuGet will add to these to lock file and they will simply be raised here (NuGet/Home#1599)
@emgarten emgarten modified the milestones: 4.3, Future-2 Mar 28, 2017
@emgarten
Copy link
Member

Moving to 4.3 to track adding warnings/errors to the assets file.

@davidfowl
Copy link
Member Author

When is 4.3?

@emgarten
Copy link
Member

2017 Update 1

@rrelyea
Copy link
Contributor

rrelyea commented Mar 28, 2017

I'm unsure if "update 1" is a thing.

I've updated "4.3" milestone to describe it as:
4.3 will be the working name of the next major update after 4.1.
POR: It will ship with what is internally called VS 2017 "15.3"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Platform:Xplat Type:DCR Design Change Request
Projects
None yet
Development

No branches or pull requests

5 participants