Conversation
1. Plugin.cs — CefSettings now sets BrowserSubprocessPath, LocalesDirPath, and ResourcesDirPath to the plugin's own directory (resolved from Assembly.GetExecutingAssembly().Location). CefSharp will find its native files in plugins/AasxPluginWebBrowser/ instead of defaulting to the main app directory. 2. AasxPluginWebBrowser.csproj — Target framework updated from net8.0-windows to net8.0-windows7.0, matching the main app and required by CefSharp/WPF under .NET 8. The graceful fallback in BrowserContainer.cs remains as a safety net — if CefSharp still fails for any reason (e.g., missing VC++ redistributable), the app degrades to FakeBrowser instead of crashing. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is a problem with plugin loading that causes crashes on startup. In Visual Studio, a clean build helped fix the crash. However, the current release build, v2025-10-21.alpha of the Package Explorer, crashes as well.
With these changes, problems during plugin loading are handled gracefully, and the application will no longer crash.