-
Notifications
You must be signed in to change notification settings - Fork 198
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
@typeparam where is not being recognized #8572
Comments
the same problem, UPD: changing .NET 7 to .NET 6 and then back to .NET 7 helped me for some reason... UPD 2: rebuild also helps, but it leave ghost errors |
I hit this too, but the project F5 compiles fine, so it's something between the tooling and the design time code generation that's breaking, and I also observed switching TFM seemed to fix it. Also reported here: https://stackoverflow.com/questions/72095268/net6-blazor-typeparam-where-constraint-error-rz1017 |
Ran in to this today, and also noticed that |
Just a quick site note that this actually worked back in VS17.5 |
@davidwengier Do we think this is actually a compiler error, or something weird going on with the project system? |
Thats an interesting question I had not considered, but I happen to be looking at project system code right now, so will see if I can see anything interesting. |
Okay, dug in a bit, and I think this is tooling. |
@davidwengier when will this patch be available? |
@MarvinKlein1508 this will be out in the first preview of 17.8 |
This works in latest stable VS release but not in VS 2022 Preview 2. The code does compile successfully and everything works as expected.

To reproduce check this file:
https://github.com/MarvinKlein1508/FormPortal/blob/master/FormPortal/Components/Admin/Forms/RuleEditor.razor
The text was updated successfully, but these errors were encountered: