MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Do the WebView2 packages still support VS2015 and higher?
@champnic is already working on this.
Since Oct 22, 2021.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Do the WebView2 packages still support VS2015 and VS2017 as stated on the getting started page, prerequisites?
I just updated from
- Microsoft.Web.WebView2.1.0.902.49
- Microsoft.Windows.ImplementationLibrary.1.0.210803.1
to - Microsoft.Web.WebView2.1.0.992.28
- Microsoft.Windows.ImplementationLibrary.1.0.210930.1
And I now get the error:
- resource.h(2543): error C2440: 'specialization': cannot convert from 'void (__stdcall *)(HANDLE) noexcept' to 'unknown-type'
- resource.h(2543): note: Context does not allow for disambiguation of overloaded function
I am using VS2017 on Windows 10, and everything builds successfully with the earlier package.
When I attempt to build the WebView2SampleWinComp solution, I get the following error:
MSB8020 The build tools for v142 (Platform Toolset = 'v142') cannot be found. To build using the v142 build tools, please install v142 build tools.
And if I modify the project to use toolset v141 and Windows SDK 10.0.17763.0, I get the same error mentioned above.
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.
Assessment
This issue has not been assessed yet.