Blazor razor formatting bug

[gavranovic672]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

After visual studio 2019, formatting of razor files is awful. Indent of the tags is broken.
I installed the new version: 17.7.2 and it seems someone did do something to fix it but it is still broken.

Before update:

<VsoNumeric Name="@nameof(DataContext.Model.ReminderTolerance)"
        Label="@T("VSO.ReminderStageSetting.Field.ReminderTolerance")"
        @bind-Value="@DataContext.Model.ReminderTolerance"
            class="vso-edit"
        Disabled="!DataContext.HasEditPermission" />

After update

<VsoNumeric Name="@nameof(DataContext.Model.ReminderTolerance)"
            Label="@T("VSO.ReminderStageSetting.Field.ReminderTolerance")"
@bind-Value="@DataContext.Model.ReminderTolerance"
            class="vso-edit"
            Disabled="!DataContext.HasEditPermission" />

Expected Behavior

I want that the ident is aligned, like before:

                    <VsoNumeric Name="@nameof(DataContext.Model.ReminderTolerance)"
                                Label="@T("VSO.ReminderStageSetting.Field.ReminderTolerance")"
                                @bind-Value="@DataContext.Model.ReminderTolerance"
                                class="vso-edit"
                                Disabled="!DataContext.HasEditPermission" />

Steps To Reproduce

Create a blazor app, create a view, add some @IF-s or/and @foreach, add a few elements, then hit ctrl + k + d (format.

Exceptions (if any)

No response

.NET Version

.net 7.0

Anything else?

No response

[davidwengier]

@SteveSandersonMS did you mean to comment on this issue? This seems like a formatting issue, possibly a duplicate of #8606, but you are commenting about runtime sounding things?

[SteveSandersonMS]

@davidwengier Ah, sorry! Too many tabs opened. I've deleted that comment and reposted it where it was meant to go on dotnet/aspnetcore#50198.

[davidwengier]

Thanks for the report @gavranovic672 but I'm going to close this as a duplicate of #8606. I'm also putting up a fix for it though :)