Aspnetcore: Unexpected Markup Element Name Despite Fully Qualified / Added Using

Created on 21 Aug 2020  路  5Comments  路  Source: dotnet/aspnetcore

The semantic colorization is coming through but it still claims it's unexpected. It resolves itself with document close and re-open.

image

NamespaceIssueTyped

Would this be expected for some reason?

Done area-razor.tooling bug feature-razor.vs
Source
picture TanayParikh

All 5 comments

Would this be expected for some reason?

Definitely not expected. I'll throw it in Preview4. This is bad 馃槃

NTaylorMullen picture NTaylorMullen on 21 Aug 2020
👍1

image

Still seeing this in a clean blazorserver project after making a change to the file (in codespaces).

TanayParikh picture TanayParikh on 10 Sep 2020

@TanayParikh do you still see this happen on your box? I haven't been able to reproduce.

NTaylorMullen picture NTaylorMullen on 18 Sep 2020

@TanayParikh do you still see this happen on your box? I haven't been able to reproduce.

I don't think I've seen this recently. We can probably close this out and re-open if it persists.

TanayParikh picture TanayParikh on 18 Sep 2020

Closing out as no longer reproing. Probably fixed this somewhere along the line.

NTaylorMullen picture NTaylorMullen on 18 Sep 2020
👍1
Was this page helpful?
0 / 5 - 0 ratings

Related issues

githubgitgit picture githubgitgit  路  3Comments
rbanks54 picture rbanks54  路  3Comments
BrennanConroy picture BrennanConroy  路  3Comments
markrendle picture markrendle  路  3Comments
fayezmm picture fayezmm  路  3Comments