Fixed failed NuGet validation due to webview2 reference

[michael-hawker]

Tries to remove extraneous WebView2Loader that was included in WASDK 1.6. If this works we can report back to platform team for proper fix.

Required PR: CommunityToolkit/Tooling-Windows-Submodule#216

Info in CommunityToolkit/Tooling-Windows-Submodule#215

[michael-hawker]

Nope, this did not seemingly resolve the issue:

@Arlodotexe you want to confirm I put the flag in a good place in the tooling PR?

Btw, UWP packages look good now that we have the #490 / #500 regression fixed:

[Arlodotexe]

@Arlodotexe you want to confirm I put the flag in a good place in the tooling PR?

Looks like it was put in a good place. If this is the correct property, I'm not sure why it'd be failing 🤔
Would be good to dig through the binlog to see if the property was blocked by the condition or if it just didn't work.

[Arlodotexe]

Let's try Sergio's comment here, just need to bump the webview2 version in the submodule.

[Arlodotexe]

@michael-hawker I've managed to fix the issue. It took a combination of updating WebView2 (as per @Sergio0694's suggestion) and removing both conditions around WebView2NeverCopyLoaderDllToOutputDirectory. Leaving either condition would result in broken packages again, but with both removed and webview2 updated:

This seems to have also resolved the issue with the extra net8.0-windows10.0.22621.0 TFM being included alongside net8.0-windows10.0.22621.

[michael-hawker]

Looks good here! 🎉

Though now we have the hard/dependency inclusion of WebView2:

[Sergio0694]

"Though now we have the hard/dependency inclusion of WebView2"

Mark that as PrivateAssets="all" for now to fix that. It's transitive anyway through WinAppSDK.

[michael-hawker]

"Though now we have the hard/dependency inclusion of WebView2"

Mark that as PrivateAssets="all" for now to fix that. It's transitive anyway through WinAppSDK.

FYI @Arlodotexe for CommunityToolkit/Tooling-Windows-Submodule#216