Do the WebView2 packages still support VS2015 and higher?

[mrtsecurity]

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.

AB#36811177

[champnic]

Hey @mrtsecurity - what type of app are you trying to build? It's possible we introduced a dependency issue, and might need to fix is or change our supported VS versions.

[mrtsecurity]

I'm working on an app to interact with identity providers for SAML authentications and required the ICoreWebView2_5 interface. Though that is immaterial as Microsoft's own WebView2SampleWinComp solution has the same build error when using the latest WebView2 package and VS2017 with the WebView2SampleWinComp properties set to toolset v141 and Windows SDK 10.0.17763.0,

If I comment out the "using =" declaration at line 2543 of resource.h (Microsoft.Windows.ImplementationLibrary.1.0.210930.1\include\wil\resource.h) along with the two that follow it, then I am able to build my app successfully, as our code apparently does not have dependencies on those three declarations.

While this resolves our issue for the time being, we would still like to know whether this will be fixed or will Microsoft's WebView2 no longer claim support for VS2015 and VS2017 as it does currently.

[champnic]

Thanks for clarifying. I've added this as a bug on our backlog to investigate further. Thanks!

[icnocop]

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

See microsoft/wil#25 and microsoft/wil#272 and microsoft/wil#302

[icnocop]

As a work-around, downgrade the NuGet package Microsoft.Windows.ImplementationLibrary to 1.0.210803.1.