Skip to content

message when compilation breaks for mismatch between packages and runtime #823

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

Closed
lucamorelli opened this issue Aug 13, 2015 · 3 comments
Closed

Comments

@lucamorelli
Copy link

Hi,
It's a know fact that during compilation if there is a big mismatch between project packages and tools/runtime build fails sending tons of errors, but looking around I see that a lot of people is not aware of it.
I think that is not to be sure that is the reason of a build fail, but I think that when you have errors as "cannot find system.object" or system.string there are not so many other possible reasons.
Why don't add a simple message suggesting check this giving an eventual url to download the latest version? just to avoid if possible that this kind of issues are opened over and over

@aspnet-hello
Copy link

This issue is being closed because it has not been updated in 3 months.

We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.

@davidalpert
Copy link

davidalpert commented Dec 31, 2017 via email

@davidalpert
Copy link

davidalpert commented Dec 31, 2017 via email

dougbu pushed a commit to dotnet-maestro-bot/AspNetCore that referenced this issue Sep 11, 2019
Add Policheck exclusion for .min.js file in jquery-validation (dotnet#822)
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants