Better diagnostics when precompiled view lookup fails

[pranavkm]

Copied from #4426 (comment)

Since razor precompilation will be on by default on the publish stage, more people will be affected by this.*

The issue I see here is that people developing on windows will hit this at runtime on production while errors will be silent at development time.

I'm ok with being careful (casing and relative paths) or to need an extra step of publish locally to test everything is working as expected. being said that, any tool/step that can improve the experience will be very appreciated.

*this = casing differences that result in precompiled lookups to fail.

[pranavkm]

cc @Bartmax \ @DamianEdwards

[pranavkm]

Presumably this is less likely to happen now that we've removed case sensitivity as part of addressing aspnet/MvcPrecompilation#37. We can re-open this if users discover other scenarios where this is problematic.

[Bartmax]

agree, looks like the right direction! 👍