Replies: 1 comment
-
That's the same for all https://stackoverflow.com/questions/6156550/replacing-the-wpf-entry-point has generic guidance.
https://github.com/cefsharp/CefSharp.MinimalExample/blob/master/CefSharp.MinimalExample.Wpf/Program.PublishSingleFile.cs provides an example.
The tested/recommended publish command is listed at #3407 (comment) The minimal example should work for both |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What version of the product are you using?
109.1.110
Nuget Package:
CefSharp.Wpf.NETCore
What architecture x86 or x64?
tried both, target is
x64
What version of .Net?
.Net 7
On what operating system?
Win 10 22h2
Are you using
WinForms
,WPF
orOffScreen
?WPF
What steps will reproduce the problem?
What is the expected output? What do you see instead?
-> application does not crash
-> Application crashes, debug information unavailable due to missing symbols exception returning some memory locations in excep.cpp
Please provide any additional information below.
The problem with single File Publish is known from earlier versions where I found some issues and documentation.
The solution is supposedly to selfhost the BrowserSubprocess from within the applications main entrance point.
In .Net 7, the main entrance point is defined in xaml so I could not find how I would host my own BrowserSubprocess.
The most helpful answer so far was in Publish self-contained .NET 5 application
#3407.
I tried to add the code from https://github.com/cefsharp/CefSharp.MinimalExample/blob/master/CefSharp.MinimalExample.Wpf/App.xaml.cs to my app.xaml.cs without success.
I attached the exception I get:
errors.log
Trying the minimal example and changing its target framework wont work either.
Beta Was this translation helpful? Give feedback.
All reactions