-
Notifications
You must be signed in to change notification settings - Fork 52
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
[Problem/Bug]: The excess projection.dll is copied to the output directory #4795
Comments
Thank you for reporting it @Gaoyifei1011 . Can you please double check that when you delete Also, if the file happens to be not needed as you suspect, can you please provde your |
After I force the removal of Microsoft.Web.WebView2.Core.Projection.Dll in Wapproj, the application works fine. After all, Native AOT compiles applications to machine code and doesn't rely on any managed assemblies.
wapproj removes code for the Microsoft.Web.WebView2.Core.Projection.Dll assembly GetStoreApp.CsProj project file
Gert Storebweieb.Csproj project file
Project link https://github.com/Gaoyifei1011/GetStoreApp Note: I manually removed Microsoft.Web.WebView2.Core.Projection.dll. If you want to test this bug, you'll need to remove this line of code from wapproj.
|
What happened?
The excess projection.dll is copied to the output directory
多余的 projection.dll 被复制到输出目录
When I upgraded to the local Microsoft.web.WebView2 package provided by you and packaged the application in Native AOT mode, I found that output directory of the emergence of a repeat. Microsoft.Web.WebView2.Core.Projection.Dll file
当我升级到你们提供的本地 Microsoft.Web.WebView2 包,并以 Native AOT 方式打包应用后发现,输出目录意外的出现了一个重复的 Microsoft.Web.WebView2.Core.Projection.dll 文件
Importance
Low. My app is not very affected, or this only affects development.
Runtime Channel
Stable release (WebView2 Runtime), Prerelease (Edge Canary/Dev/Beta)
Runtime Version
stable version
SDK Version
1.0.2817-prerelease
Framework
WinUI2/UWP
Operating ### System
Windows 11
OS Version
26100
Repro steps
see describe
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
The text was updated successfully, but these errors were encountered: