-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Component inheritance seems to be broken #48447
Comments
Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project that illustrates the problem. |
I can reproduce the problem. Just create a project from standard template, e.g.
There is a Add a
... and let Foo inherit from Qux, everything works fine. |
The issues you referred to, along with the accompanying code snippet, point to the problem described here: #48281 Currently there is a regression in the new SDK version 7.0.302 that is documented here dotnet/razor#8718 To address the problems, it's recommended to pin the SDK version to 7.0.203 using the You can also find this information in the Visual Studio 17.6.1 release notes: https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes#17.6.1 in section "Known Issues" |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate. See our Issue Management Policies for more information. |
I am having problems with component inheritance after the latest VS update (17.6.1). For example:
Foo.razor:
Bar.razor:
The above doesn't actually render the component. It renders as:
<foo id="foo" class="btn btn-secondary"></foo>
When I take away the inheritance and put everything in Foo.razor it renders properly.
The inheritance also did not work when deployed to Windows Server 2019, but it did work in the local dev environment prior to the latest VS update.
The text was updated successfully, but these errors were encountered: