lonix1

No worries, and no one was insulted. I'm sure that alternative extension will be very useful to many people. But to those with large codebases who want a drop-in replacement...

That wasn't it, but you helped me nonetheless because it forced me to play around with the UI a bit until I solved it. Thanks :smile: My "solution" was to...

I think that is the best way to repro: - blame doesn't work - click on "uncommitted changes" - click "Blame" - click on old commit... blame will be shown...

My [issue](https://github.com/dotnet/aspnetcore/issues/41930) was closed, as were similar ones over the years. There seems to be resistance to this, but I don't know how it can be justified. Managing something as...

@wstaelens Like I said above, this goes back years. There has been resistance to handling it for technical reasons (understandable...), but it's strange given how important this is. Especially given...

That trick may work for razor components, but not for razor pages. None of the workarounds here or the SO questions I linked above work for Razor Pages. Please consider...

This works for RazorPages: ```cs @page @attribute [RazorCompiledItemMetadata("RouteTemplate", MyConstants.Pages.Foo.Bar)] ``` But that is unnecessarily complicated, and still has a magic string in it. A better syntax is needed.

The vscode team [doesn't believe it's their fault](https://github.com/microsoft/vscode/issues/47993#issuecomment-381795992) - so where does the problem lie? This drives me crazy every day. I'm glad I'm not alone :) Does someone know...