-
Notifications
You must be signed in to change notification settings - Fork 253
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
Labels
Milestone
Comments
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)
Moving to 4.3 to track adding warnings/errors to the assets file. |
When is 4.3? |
2017 Update 1 |
I'm unsure if "update 1" is a thing. I've updated "4.3" milestone to describe it as: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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.
The text was updated successfully, but these errors were encountered: