MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Nuget Package Selection
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
When using a project with packages.config for nuget package management and including the WebView2 SDK nuget package, references are added to the Microsoft.Web.WebView2.Core.dll, Microsoft.Web.WebView2.Wpf.dll and Microsoft.Web.WebView2.WinForms.dll. Core I get as it contains common functionality shared between WPF and WinForms (and is in fact not for .NET Core). But why are both WPF and WinForms references added? The Nuget package should target the appropriate project type or be split such that there are different nuget packages.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with a packages.config project that includes the WebView2 SDK NuGet package and inspect the references it adds. Compare the WPF and WinForms project types and the Microsoft.Web.WebView2.Core.dll, Microsoft.Web.WebView2.Wpf.dll, and Microsoft.Web.WebView2.WinForms.dll references. Done means the package selects only the appropriate UI references or provides a clear package split.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100