-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Print a warning if FindAssembliesWithReferencesTo cannot find file #11226
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
Labels
Milestone
Comments
pranavkm
added a commit
to dotnet/razor
that referenced
this issue
Jun 25, 2019
Currently FindAssembliesWithReferencesTo produces a stacktrace when P2P builds fail - for instance if the referenced project has a compiler error. This changes it to use LogErrorFromException. In addition, there was a typo in the property that disabled the feature. Fixes dotnet/aspnetcore#11226
This was referenced Jun 25, 2019
pranavkm
added a commit
to dotnet/razor
that referenced
this issue
Jun 26, 2019
…702) Currently FindAssembliesWithReferencesTo produces a stacktrace when P2P builds fail - for instance if the referenced project has a compiler error. This changes it to use LogErrorFromException. In addition, there was a typo in the property that disabled the feature. Fixes dotnet/aspnetcore#11226
We went with using LogFromException, so the outcome looks like what csc prints when it cannot find an assembly (instead of a stack trace). Much better. |
Reviving this, the plan here is to print a pretty warning and let the task not fail in the event assemblies are missing. Usually this is indicative of other build issues and we want to avoid getting flooded with issues for random problems. |
JunTaoLuo
referenced
this issue
May 17, 2020
…otnet/razor#702) Currently FindAssembliesWithReferencesTo produces a stacktrace when P2P builds fail - for instance if the referenced project has a compiler error. This changes it to use LogErrorFromException. In addition, there was a typo in the property that disabled the feature. Fixes https://github.com/aspnet/AspNetCore/issues/11226\n\nCommit migrated from dotnet/razor@87c12a1
dougbu
referenced
this issue
in dougbu/razor-compiler
Nov 17, 2021
…otnet/razor#702) Currently FindAssembliesWithReferencesTo produces a stacktrace when P2P builds fail - for instance if the referenced project has a compiler error. This changes it to use LogErrorFromException. In addition, there was a typo in the property that disabled the feature. Fixes https://github.com/aspnet/AspNetCore/issues/11226\n\nCommit migrated from dotnet/razor@87c12a1 Commit migrated from dotnet/aspnetcore@4e16cfd4daf0
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Missing assemblies will fail the build, but since FindAssemblyWithReferencesTo gets first dibs, it throws the exception rather than csc. We should instead consider printing a warning and letting later parts in the build fail.
The text was updated successfully, but these errors were encountered: