Let's try and get #159 working. I had to comment out this part (which was also highly non-functional...) earlier because it caused stability problems, since CEF starts up more than 1 child process sometimes (which caused problems). I think we might have to distinguish between different process types here, which is why we start fiddling around with the arguments. Perhaps there are other, better ways to detect the current process type though.
Set up a horrible hack, inspired by http://stackoverflow.com/questions/12640878/force-visual-studio-to-rebuild-dependent-projects, to be able to "just press F5" and run the WPF Example.
Added logging of the startup command line, which can be seen with e.g. DebugView.
More work on #159. Quite far from getting it working. We cannot really use the CefBrowser object on the "wrong" thread, even though we are in the render process. Time to roll up our sleeves and start doing some CefPostTask() work I think...
A futile attempt to try and get debugging of the subprocess working. It doesn't seem so easy to get Visual Studio to accept this one, unfortunately.