-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Automatically copy wwwroot/** to publish directory #4537
Comments
@SteveSandersonMS if this is more consistent with other SDKs, I'm all for it. How does one change from |
Actually following @javiercn's suggestion, I re-checked this and it turns out that it's not necessary to have this. It must be built into the SDK or package already. The fact that So, I'll close this issue, and will update the CTI steps to remove this bit. As we create the other CTI scenarios for other platforms, we'll be forced to validate in each case that it's not necessary to have anything like this in the csproj. |
Apparently this is not functioning currently. I'm not sure why it appeared to work correctly when I tried it, but either I did something wrong or there was a difference in my local environment. As per this comment: https://github.com/aspnet/Tooling-ManualTests/pull/1591#issuecomment-1040059686 the project on WinForms at least doesn't work unless you explicitly copy |
@SteveSandersonMS maybe you had the files in the bin folder from a previous build? And they didn't get cleaned up on rebuild because they're not seen as output files anymore? Anyway, weird. |
…directory in development Fixes #4537
Description
https://github.com/aspnet/Tooling-ManualTests/pull/1591#discussion_r799659030
We should consider putting some MSBuild logic in the Blazor Hybrid MAUI, WinForms, and WPF packages that is equivalent to adding the following to your
.csproj
:Otherwise, developer have to clutter their own
.csproj
with this, and might forget to do so. This would bring things into line withwwwroot
being published automatically in theWeb
SDK.Public API Changes
Intended Use-Case
The text was updated successfully, but these errors were encountered: