MORPH
SIGN IN SIGN UP
cefsharp / CefSharp UNCLAIMED

.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

0 0 0 C#
Normal View History Raw
Maintenance - Fixed formatting, file encoding, and copyright year (#2504) * Applied formatting * Fixed file encoding + Updated copyright year * Updated License * Fixed more file encoding * Copyright notice now shows the year the file was created
2018-09-10 02:41:13 +02:00
// Copyright © 2013 The CefSharp Authors. All rights reserved.
Add license disclaimer to rest of solution files (hopefully got them all now)
2014-06-25 12:00:58 +10:00
//
// Use of this source code is governed by a BSD-style license that can be found in the LICENSE file.
Move Enums into their own folder (again not changing the namespace as to avoid breaking the public API, at least for now) Add copyright disclaimer to JavascriptResponse Remove Kernel32.OutputDebugString calls and replace with Debug.WriteLine Removed ScriptException and ResponseAction - unused classes Rename CefCursorType to CursorType - wasn't exposed as part of the public API so can rename
2017-03-21 09:32:27 +10:00
using System.Diagnostics;
Add Initial IRenderProcessHandler.OnContextCreated/Released implementation (#2697) * WinForms/WPF - Dispose of IFrame after calling LoadUrl * BrowserProcess - Add initial implementation of IRenderProcessHandler.OnContextCreated/OnContextReleased - IV8Context.Execute is the only method to be implemented so far (execute script without returning a result) - Wrappers for CefFrame and CefBrowser have yet to be imported yet, still need to determine if they should be included individually or reference to CefSharp.Core added * BrowserProcess - Add wrappers for Browser and Frame Ultimately we should probably remove the CefSharp.BrowserSubprocess.Core project and move all the code into a folder/namespace within CefSharp.Core This would allow us to share the a lot of existing code, major refactor required * CefSharp.Common.props - Add CefSharpBrowserProcessCore32/64 properties Make creating your own custom browser process easier * BrowserProcess - Remove example and add comments about creating your own custom version
2019-03-20 20:33:10 +10:00
using CefSharp.RenderProcess;
remaining stuff that i desired to put in on changeset
2014-03-09 14:11:37 +01:00
WIP on #159, trying to drastically refactor the subprocess (in C#, which is debuggable and hence a HUGE plus in what we are trying to achieve...). Will also consider using the C API for CEF, since I think it actually will suit us better.
2013-10-29 22:29:52 +02:00
namespace CefSharp.BrowserSubprocess
{
Add Initial IRenderProcessHandler.OnContextCreated/Released implementation (#2697) * WinForms/WPF - Dispose of IFrame after calling LoadUrl * BrowserProcess - Add initial implementation of IRenderProcessHandler.OnContextCreated/OnContextReleased - IV8Context.Execute is the only method to be implemented so far (execute script without returning a result) - Wrappers for CefFrame and CefBrowser have yet to be imported yet, still need to determine if they should be included individually or reference to CefSharp.Core added * BrowserProcess - Add wrappers for Browser and Frame Ultimately we should probably remove the CefSharp.BrowserSubprocess.Core project and move all the code into a folder/namespace within CefSharp.Core This would allow us to share the a lot of existing code, major refactor required * CefSharp.Common.props - Add CefSharpBrowserProcessCore32/64 properties Make creating your own custom browser process easier * BrowserProcess - Remove example and add comments about creating your own custom version
2019-03-20 20:33:10 +10:00
/// <summary>
/// When implementing your own BrowserSubprocess
BrowserSubprocess - Refactor to support .Net Core (#2891) * BrowserSubprocess - Refactor to support .Net Core - Added BrowserSubprocessExecutable for use with .Net Core (no WCF) - Added WcfBrowserSubprocessExecutable for use with the existing CefSharp.BrowserSubprocess.exe which supports WCF (conditionally) * Add additional comments and minor code simplification
2019-10-02 12:25:34 +10:00
/// - For Full .Net use <see cref="WcfBrowserSubprocessExecutable"/>
/// - For .Net Core use <see cref="BrowserSubprocessExecutable"/> (No WCF Support)
Add Initial IRenderProcessHandler.OnContextCreated/Released implementation (#2697) * WinForms/WPF - Dispose of IFrame after calling LoadUrl * BrowserProcess - Add initial implementation of IRenderProcessHandler.OnContextCreated/OnContextReleased - IV8Context.Execute is the only method to be implemented so far (execute script without returning a result) - Wrappers for CefFrame and CefBrowser have yet to be imported yet, still need to determine if they should be included individually or reference to CefSharp.Core added * BrowserProcess - Add wrappers for Browser and Frame Ultimately we should probably remove the CefSharp.BrowserSubprocess.Core project and move all the code into a folder/namespace within CefSharp.Core This would allow us to share the a lot of existing code, major refactor required * CefSharp.Common.props - Add CefSharpBrowserProcessCore32/64 properties Make creating your own custom browser process easier * BrowserProcess - Remove example and add comments about creating your own custom version
2019-03-20 20:33:10 +10:00
/// - Include an app.manifest with the dpi/compatability sections, this is required (this project contains the relevant).
/// - If you are targeting x86/Win32 then you should set /LargeAddressAware (https://docs.microsoft.com/en-us/cpp/build/reference/largeaddressaware?view=vs-2017)
/// </summary>
WIP on #159, trying to drastically refactor the subprocess (in C#, which is debuggable and hence a HUGE plus in what we are trying to achieve...). Will also consider using the C API for CEF, since I think it actually will suit us better.
2013-10-29 22:29:52 +02:00
public class Program
{
Move Create method to where it's actually used and remove an unused instance variable
2014-08-27 14:23:08 +10:00
public static int Main(string[] args)
WIP on #159, trying to drastically refactor the subprocess (in C#, which is debuggable and hence a HUGE plus in what we are trying to achieve...). Will also consider using the C API for CEF, since I think it actually will suit us better.
2013-10-29 22:29:52 +02:00
{
BrowserSubprocess - Refactor to support .Net Core (#2891) * BrowserSubprocess - Refactor to support .Net Core - Added BrowserSubprocessExecutable for use with .Net Core (no WCF) - Added WcfBrowserSubprocessExecutable for use with the existing CefSharp.BrowserSubprocess.exe which supports WCF (conditionally) * Add additional comments and minor code simplification
2019-10-02 12:25:34 +10:00
Debug.WriteLine("BrowserSubprocess starting up with command line: " + string.Join("\n", args));
Lots of work towards #159.
2013-11-06 22:52:18 +01:00
BrowserSubprocess - Refactor to support .Net Core (#2891) * BrowserSubprocess - Refactor to support .Net Core - Added BrowserSubprocessExecutable for use with .Net Core (no WCF) - Added WcfBrowserSubprocessExecutable for use with the existing CefSharp.BrowserSubprocess.exe which supports WCF (conditionally) * Add additional comments and minor code simplification
2019-10-02 12:25:34 +10:00
//Add your own custom implementation of IRenderProcessHandler here
IRenderProcessHandler handler = null;
Bug fix: handle type=crashpad-handler Cherry-pick of #2449 which was approved by Alex. I was seeing instances of the subprocess being spawned this way when running the CefSharp.Wpf.Example project. Debugging showed me that no such argument was being passed to the process. This PR works around the issue by opting out from getting the parent process ID for such processes.
2018-07-11 05:45:16 +03:00
BrowserSubprocess - Refactor to support .Net Core (#2891) * BrowserSubprocess - Refactor to support .Net Core - Added BrowserSubprocessExecutable for use with .Net Core (no WCF) - Added WcfBrowserSubprocessExecutable for use with the existing CefSharp.BrowserSubprocess.exe which supports WCF (conditionally) * Add additional comments and minor code simplification
2019-10-02 12:25:34 +10:00
//The WcfBrowserSubprocessExecutable provides BrowserSubProcess functionality
//specific to CefSharp, WCF support (required for Sync JSB) will optionally be
//enabled if the CefSharpArguments.WcfEnabledArgument command line arg is present
//For .Net Core use BrowserSubprocessExecutable as there is no WCF support
var browserProcessExe = new WcfBrowserSubprocessExecutable();
var result = browserProcessExe.Main(args, handler);
Move Enums into their own folder (again not changing the namespace as to avoid breaking the public API, at least for now) Add copyright disclaimer to JavascriptResponse Remove Kernel32.OutputDebugString calls and replace with Debug.WriteLine Removed ScriptException and ResponseAction - unused classes Rename CefCursorType to CursorType - wasn't exposed as part of the public API so can rename
2017-03-21 09:32:27 +10:00
Debug.WriteLine("BrowserSubprocess shutting down.");
Maintenance - Fixed formatting, file encoding, and copyright year (#2504) * Applied formatting * Fixed file encoding + Updated copyright year * Updated License * Fixed more file encoding * Copyright notice now shows the year the file was created
2018-09-10 02:41:13 +02:00
Remove CefSubProcess.cpp - having such trivial cpp files seems silly Convert CefRenderProcess into a cpp class - this should theoretically allow users to add CefSharp.BrowserSubprocess.Core as a reference then use their own process to spawn it Move CefRenderProcess and CefSubProcess into CefSharp.BrowserSubprocess namespace - otherclasses should really be moved as well Only use our custom subProcess when type is render, for gpu and plugin processes the standard implementation is just fine Remove CefSubProcess Rename CefAppWrapper to CefSubProcess
2016-05-16 18:52:35 +10:00
return result;
Move Create method to where it's actually used and remove an unused instance variable
2014-08-27 14:23:08 +10:00
}
WIP on #159, trying to drastically refactor the subprocess (in C#, which is debuggable and hence a HUGE plus in what we are trying to achieve...). Will also consider using the C API for CEF, since I think it actually will suit us better.
2013-10-29 22:29:52 +02:00
}
}
Reference in New Issue Copy Permalink