-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Remove WinForms/WPF BlazorWebView controls #33410
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
Conversation
They are now in the dotnet/maui repo.
eng/ProjectReferences.props
Outdated
<ProjectReferenceProvider Include="Microsoft.AspNetCore.Components.WebView.WindowsForms" ProjectPath="$(RepoRoot)src\Components\WebView\Platforms\WindowsForms\src\Microsoft.AspNetCore.Components.WebView.WindowsForms.csproj" /> | ||
<ProjectReferenceProvider Include="Microsoft.AspNetCore.Components.WebView.Wpf" ProjectPath="$(RepoRoot)src\Components\WebView\Platforms\Wpf\src\Microsoft.AspNetCore.Components.WebView.Wpf.csproj" /> | ||
<ProjectReferenceProvider Include="Microsoft.AspNetCore.Components.WebView" ProjectPath="$(RepoRoot)src\Components\WebView\WebView\src\Microsoft.AspNetCore.Components.WebView.csproj" /> | ||
<ProjectReferenceProvider Include="Microsoft.AspNetCore.Components.WebView" ProjectPath="$(RepoRoot)src\Components\WebView\src\Microsoft.AspNetCore.Components.WebView.csproj" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be OK to leave this where it was so we can still have other platforms?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Restored.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than my request to not move the src
project, this all looks good!
I mean, really it actually looks awful because you're killing all our beautiful code, it's a total bloodbath - our babies! - but I'll get counselling and carry on.
@dotnet/aspnet-build - how do I fix this build failure?
I am deleting projects that never shipped RTM. They did ship as preview, but they are being deleted from here because they moved to another repo. |
If the only failure is that one in code-check, one of us can just use our admin privileges to merge this for you. |
@wtgodbe - thanks! I still have some work in this PR so I'll let you know when it gets to that point. |
@Eilon please also remove the now-useless block at https://github.com/dotnet/aspnetcore/blob/main/eng/Build.props#L46-L54 |
# Visual Studio Version 17 | ||
VisualStudioVersion = 17.0.31324.12 | ||
# Visual Studio Version 16 | ||
VisualStudioVersion = 16.0.31320.298 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have unintentionally not yet installed VS17. But I will do that soon. I assume this header flip-flops all the time anyway?
@SteveSandersonMS the folder structure is restored, so this is a more clean removal now. |
@wtgodbe - can you super-admin merge this PR now? The code is done and it's signed off. |
They are now in the dotnet/maui repo: dotnet/maui#1199