-
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
Blazor Wasm Preview7: Broken build generates MvcApplicationPartsAssemblyInfo.cs #24171
Comments
For a little more info: removing the |
Added workaround to disable the generation of this file. I'm up and running! |
Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project (ideally a GitHub repo) that illustrates the problem. |
I'll definitely try and reproduce this. A build error gives a nice easy benchmark to achieve. I think whatever special sauce that causes my project not to be debuggable must also relate to this. I have a project started and will continue adding to that until a reproduction happens. |
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 have exactly the same issue when porting from 3.1. |
Describe the bug
After upgrading a hosted Blazor Wasm project to .NET 5 preview 7, the client project produces a
MvcApplicationPartsAssemblyInfo.cs
file with the following contents:The
ApplicationPartAttribute
references the two project references in the client project, but are not recognized:To Reproduce
I don't yet know how to reproduce, but maybe it's related to the reason my project could not debug these same project references in wasm mode: #21849 (comment)
Workaround
Add
<GenerateMvcApplicationPartsAssemblyAttributes>false</GenerateMvcApplicationPartsAssemblyAttributes>
to project props.Further technical details
dotnet --info
Build happens via
dotnet build
on the command line.The text was updated successfully, but these errors were encountered: