updated the SDK 7.0.304 version, but the bug won't go away.

[cyberprophet]

The bugs I had in SDK 7.0.302 still seem to exist.

#8718 (comment)

[Luk164]

Same, I am running on sdk 7.0.304 and also tried out 7.0.400-preview.23274.1 and the bug is still there, though the components seem to render this time around. This occurs on both VS 17.6.4 and 17.7.0 Preview 2

[cyberprophet]

The solution is the only thing I can do is force down the sdk version using global.json.

[chsienki]

Can you confirm exactly which SDK + Visual Studio versions you are using? Thanks

[Luk164]

@chsienki 7.0.304 + VS 17.6.4 for me. Also 7.0.400-preview.23274.1 and 17.7.0 Preview 2

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 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.

Please see our Issue Management Policies for more information.

[Luk164]

Please don't close this, the issue is very annoying because I have to keep an instance of 17.5.4 installed to work with blazor projects.

[jaredpar]

Do you have a repro project that we can look at?

[Luk164]

@jaredpar Here you go, though realistically all you need is a fresh blazor repo and add this:

@typeparam T where T : new()

<h3>LookAtMe</h3>

@code {

}

[davidwengier]

@Luk164 Could you confirm exactly which bug you're hitting? You mentioned above that "the components seem to render this time around" which makes me think that you are hitting a different bug than the comment linked above. This seems to be backed up by your repro file, which has no components.

Is it possible you're hitting #8572 instead?

[Luk164]

@davidwengier RZ1017 I believe, so #8572 could be a match, but I am not sure. And yes it does indeed compile. I am currently stuck using VS17.5.4 as it is the last version I know of without the bug.

[davidwengier]

Thanks for confirming. That was fixed last week, so sadly there will be a little bit of a wait before its available in a VS release. Should be in the first preview of the next minor version of VS though.

The issue should fix itself when there is a project change of any kind, including just adding whitespace to the project file, but I understand that's not the most fun way to live :)

[jaredpar]

Closing as a dupe of #8572