WPF 4.0 Chromium WebBrowser

Source code checked in, #20228

Project Collection Service Accounts — Mon, 01 Oct 2012 20:45:27 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #20227

Project Collection Service Accounts — Mon, 01 Oct 2012 20:44:38 GMT

Checked in by server upgrade

New Post: Weird missing assembly error

itbhari — Fri, 22 Jul 2011 10:45:40 GMT

Changing the project framework to DotNet 4 (not the client profile) solved this for me.

New Post: can't compile your source

Koichi — Sun, 03 Jul 2011 21:20:05 GMT

Guys, please follow the blog of Chris Cavanagh.
The Awesomium is offering free indie license now!
http://chriscavanagh.wordpress.com/2011/05/11/awesomium-free-indie-license/

New Post: can't compile your source

kayhustle — Tue, 28 Jun 2011 01:27:30 GMT

I can't get this to work either. I extracted the files specified in the blog. Might be a good idea to just upload the source with all the correct files in there so when people download it, they don't have to waste time trying to figure out what files they need and where to put them.

New Post: can't compile your source

BrentonUnger — Thu, 23 Jun 2011 22:25:08 GMT

I moved the code to compile with the v10 tools, have the proper folder structure, and I'm not able to build. It's just not finding the file, even though it indeed does exist. What are the chances I could get this working? Or should I skip it and just use the Awesomium library?

Patch Uploaded: #9387

lholden — Wed, 11 May 2011 19:10:34 GMT

lholden has uploaded a patch.

Description:
The WebBrowser object is never destroyed.

The delegate added to Application.Current.MainWindow.Closing in the WebBrowser constructor is never removed so a reference to the WebBrowser control from the MainWindow remains. This causes a problem in applications that repeatedly create and destroy WebBrowser objects.

I've attached a fix for the problem. Note that I switched from using delegates in order to quickly create the fix, the same fix should be possible using delegates.

Patch Uploaded: #9001

tdenovan — Sun, 03 Apr 2011 23:29:41 GMT

tdenovan has uploaded a patch.

Description:
This is a patch to bring the awesomium wrapper up to compatibility with awesomium 1.6.1. rc4. RC 4 fixes a bug within awesomium supposedly caused by plugins within Chrome (despite the fact all plugins had been disabled). Nevertheless, incorporating RC4 does fix the bug (it manifested as a popup error message stating that binding_utils had encountered an error).

New Post: Weird missing assembly error

vanp — Wed, 30 Mar 2011 16:22:00 GMT

I was able to get around it but it's really dumb and hackish.

Instead of adding the Cjc.ChromiumBrowser to my solution I've started adding my project to the Demoprogram and it works!

Warning: Don't rename the demo program because then it won't work again.....

New Post: Weird missing assembly error

iv — Wed, 30 Mar 2011 16:12:51 GMT

I'm having the same problem and I'm going round in circles trying to fix it. I now have the demo program and my program in the same project - the demo program works fine when set as the Startup project, mine works fine when set as the startup project. I have set the references in my project to match the demo project exactly. After I have set the references, I add "using Cjc.ChromiumBrowser" - Visual Studio even predicts "Cjc" and "ChromiumBrowser".

YET as soon as I hit compile, it changes its mind and gives me this error. It marks "Cjc" with the red underlining and refuses to predict "Cjc" any more. It's as if it loses the reference completely even though nothing has changed.

I have spent days trying to figure this out. I need some way of rendering HTML in a WPF control, and I can't find any other options out there other than to use Awesomium.

vanp - please tell me you got somewhere with this? I get the feeling these discussion boards have been abandoned.

New Post: Cannot include WebBrowser control in my project

iv — Thu, 03 Mar 2011 11:57:03 GMT

Hi there

First of all thanks for each of your involvement on this project, a full WPF WebBrowser control is badly needed. Personally I need to use (and modify) such a control for viewing HTML documents on a multi-touch screen - I need to support basic WPF manipulations (resize, rotate etc), as well as a few non-standard gestures on the document.

It took me a while but I eventually got the source to compile. The compiled demo application runs. (It would be worthwhile including a readme file with the release describing exactly how to do this; I found the information from many discussions/websites.) I am still however having a great deal of difficulty actually using the control. I have tried a variety of things, none of which have helped. I began by adding the projects Cjc.AwesomiumWrapper and Cjc.ChromiumBrowser to my existing project. I add the Awesomium directory in the correct place. I have tried setting up the references in every way I know how - including adding a direct reference to the missing file itself - but always get the following warning in the designer:

"System.IO.FileNotFoundException Could not load file or assembly 'Cjc.AwesomiumWrapper.dll' or one of its dependencies. The specified module could not be found."

When I rebuild the Cjc.* projects, the references are found in my project and I use the WebBrowser control - but then my project will not run. When I rebuild my project, the references are lost and I get the following error:
"Error 6 The type or namespace name 'Cjc' could not be found (are you missing a using directive or an assembly reference?)"

I expected the difference between .NET 3.5 and .NET 4.0 to be the problem but I have tried every combination of targeted framework, .NET3.5 and .NET4.0, v90 and v100 toolset with no luck.

Though I will need to modify the source code eventually, I have also tried just using the compiled DLLs to be able to use the control in my project. Again no luck.

It seems the goal of this project is a WPF WebBrowser control that can be used like any other WPF control. I appreciate that it is still under development but unless I have really missed the boat it really seems impossible to do at this point! Can anyone help me out getting this control into my project?

New Post: AccessViolationExceptions and OutOfMemoryExceptions

taicho — Tue, 15 Feb 2011 15:18:27 GMT

Hi guys,

Alright so I've tried everything I can think of - I can finally get the Window to load but as soon as it touches the webView I get AccessViolationExceptions and OutOfMemoryExceptions.

Since I don't have Visual Studio 2008 installed (and probably won't ever again) I used the pre-combiled AwesomiumWrapper that Koichi compiled. That got me building finally and allowed me to load the Window, however now I am stuck getting the aforementioned exceptions any time the webView is touched i.e. navigating initially etc... please help! :-)

To clarify - I fail at "webCore.Update()" and "webView.LoadUrl()"...

My Environment:

Win 7 64 Professional

VS2010

Thanks in advance,

Azad

New Post: can't compile your source

Koichi — Mon, 17 Jan 2011 11:52:12 GMT

Alright, to get rid of the missing header files compilation errors, you have to download the required Awesomium SDK and extract the source files into the associated paths for the AwesomiumWrapper to compile successfully.

Since the Awesomium 1.6 RC1 SDK is not listed in the available downloads, you can either get it using the direct link above or merge the current edition of WPF Chromium with the current edition of Awesomium SDK.

Note, that both Visual Studio 2008 and Visual Studio 2010 are still required to be installed on the same machine for a successful compilation of the projects.

New Post: can't compile your source

andersonimes — Fri, 14 Jan 2011 14:57:44 GMT

I think you might have missed the point.

New Post: Weird missing assembly error

vanp — Tue, 11 Jan 2011 20:22:57 GMT

The exact compile error is: "The type or namespace name 'Cjc' could not be found (are you missing a using directive or an assembly reference?)"

I've added the project references and Cjc.ChromiumBrowser and Cjc.Awesomium assembles were both added in the references folder but whenever I try to use the namespace or reference it in xaml it gives me this error. The demo program works fine and I have a copy of Awesomium in the project folder.

In fact, I've compiled the demo program then confirming that it works I've added a new project to the solution while changing the startup program from the Demoprogram to the new project and added the necessary references but still no luck.

What am I missing here? Why can the DemoProgram recognize the Cjc assemblies but anything I make can't?

New Post: what is the snapshot project all about?

sequoyan — Thu, 30 Dec 2010 04:47:14 GMT

figured it out. thanks anyway.

New Post: what is the snapshot project all about?

sequoyan — Wed, 29 Dec 2010 17:07:53 GMT

I don't see any mention of what it does/offers on your site or here.

Thanks for publishing the code, I'm enjoying the investigation of what it offers...

Patch Uploaded: #7242

sdamar — Mon, 01 Nov 2010 15:41:59 GMT

sdamar has uploaded a patch.

Description:
Wrapping ResourceInterceptor functionality for use with c#.

I'm not experience at writing c++-cli code for wrapper, so any feedback will be appreciated. I am concerned that I may have introduced some memory leaks.

New Post: can't compile your source

Koichi — Thu, 28 Oct 2010 17:34:35 GMT

The blog belongs to Chris Cavanagh actually, as well as this project.

New Post: can't compile your source

andersonimes — Fri, 22 Oct 2010 18:59:32 GMT

I get what you are saying here, but there is no readme in the source tree (like people with complicated builds usually do), nor are there instructions on the Codeplex wiki. To be able to figure this out, someone has to:

go to a random article on your blog (the link doesn't even say that it will take you to compilation instructions... just that it contains "more details") OR
endure this self-important post in the discussion group for this project.

Please learn to package your source code in such a way that it is self-documenting or, at the very least, provide good documentation on the project site.