Questions & Support

CefSharp is a complex project to support, every updated version of CEF/Chromium brings a new set of features/behaviours/bugs. There are also three variants, WPF/WinForms/Offscreen. Please read this quick guide to help us help you.

NOTE CefSharp is a .NET wrapper for the Chromium Embedded Framework(CEF), many of the questions you have aren't CefSharp specific. The CEF Support Forum might be a better place to ask for help.

When asking a question please include the following:

• What version are you using? (exact version please e.g. 75.1.143, not Latest version as that's relative)
• Are you using WPF/WinForms/OffScreen?
• Are you targeting .Net Core? If yes which version?
• No images of code/exceptions please, if you have a more than a few lines of code then please use Gist, Pastebin, JsFiddle, ControlC or similar. Post a link to your relative resource.
• The CefSharp.MinimalExample is kept up to date with the latest version
  • You can use it for testing purposes
  • Take the project for a spin
  • Can you reproduce the problem with the MinimalExample?
    • Fork to provide a sample of your problem
    • Squash all your changes into a single commit
    • Only include necessary changes to reproduce your problem, don't add code that's not relevant
    • Please don't remove the other examples that aren't relevant, just ignore then and keep your changes Minimal

No images of code

Please no images of code

• It's impossible to copy and paste code from an image
• Images don't scale well on small devices making the code unnecessarily hard to read.

Please use one of the following

• GitHub Gist
• PasteBin
• Fork CefSharp.MinimalExample and push your changes to GitHub.

No Images of Exceptions

Please use the Copy to Clipboard option when running within Visual Studio. Please format your exception to be readable, use the appropriate Code Markdown or use GitHub Gist or PasteBin and provide a link.

Some excellent Resources to get you started if you need some additional guidance.

• Jon Skeet Question Checklist
• How to create a Minimal, Reproducible Example
• Image of an exception
• Image of code
• It's not working

Imagine You’re Trying To Answer The Question

Once you’ve finished writing your question, read it through. Imagine you were coming to it fresh, with no context other than what’s on the screen. Does it make sense? Is it clear what’s being asked? Is it easy to read and understand? Are there any obvious areas you’d need to ask about before providing an answer? You can usually do this pretty well however stuck you are on the actual question. Just apply common sense. If there’s anything wrong with the question when you’re reading it, obviously that will be a problem for whoever’s actually trying to answer it. So fix the problems. Improve the question until you can read it and think, “If I only knew the answer to the question, it would be a pleasure to provide that answer.” At that point, post and wait for the answers to come rolling in.

Jon Skeet does a far better job of summarising the problem in his blog posts, direct excerpt from https://codeblog.jonskeet.uk/2010/08/29/writing-the-perfect-question/#golden-rule