Skip to main content

How to get windows.external to work when using Awesomium.NET

Image
By
Note: There is an updated version of this post right here (with source code and all stuff)

I been doing some experiments with the Awesomium web browser framework, and after a lot of failing attempts, I finally got windows.external calls working.

Awesomium is a windowless port of Chromium/WebKit. For WinForm developers, an alternative way to embed web pages in your winforms or WPF apps without having to use the WebBrowser control.

For a long time, I been using the IE embedded browser to show reports (webpages) in winform apps, with let say…, acceptable results ;), but the thruth is there is a lot of goodness out there into the wild with better support for css, html 5, etc. So I decided to install Awesomium.NET and give it a try.

While the API is pretty intuitive, I had some trouble trying to call C# methods from Javascript, a fairly easy thing to do with the classic webbrowser control.

This is how things work when using embedded IE Browser

C# code
html code


And this is how to do it when using Awesomium.NET.

C# code

Html code

Aside for this pitfall, this framework is great, it is easy to use, well documented and it comes with a bunch of working samples (for both, WinForms and WPF apps). Highly recommendable.

In this post I'm using Awesomium 1.7.0 RC3. I know the API has change from previous releases and were a lot of bug fixes (some of them related to javascript interop). If you are running on a previous version of the framework, the code seen above may not work.




Labels:

Comments

  1. AnonymousAugust 28, 2013 at 5:16 PM

    Please share this code...

    ReplyDelete
    Replies
    1. AmirallesAugust 29, 2013 at 1:24 PM

      Here it goes ;) http://www.alemiralles.blogspot.com.ar/2013/08/how-to-get-windowsexternal-to-work-when.html

      Delete

Post a Comment

Popular posts from this blog

Moving to Medium

By
It's been a long time since I want to give medium a try, and finally, I made some time to do it. To get started on the new platform, I'll be doing series on "Getting programming concepts, languages and tools". If it sounds interesting to you, please take a look at the first post  Getting AWK  and spread the word if you like it. I'm not going to migrate old entries to the new web site. They will remain here safe and sound! As usual, thanks for reading!
Post a Comment
Read more

How to show excel files inside the .NET Webbrowser Control

By
If you are reading this, chances are you been banging your head against the wall for a couple of hours (or even days) trying to show excel files inside the WinForms webbrowser control. Possible reasons you ended up in here: You had working code that got broke after upgrading from Win 7. Your code doesn’t work the same way between machines running different (newer) versions of IE. A download box pops up every time your app tries to show an excel file inside the webbrowser control (you wanna show the actual content). You just have no clue on how to get excel working into the .NET embedded webbrowser control. You are trying to implement IInternetSecurityManager and don’t know where to start. (Or how don’t know how to delegate calls to your security manager). Among many other, maybe….. Yes, COM is a PITA, so is ActiveX and IE (Embedded or full for that matter). And no, showing excel files inside the webbrowser control shouldn’t be that hard, but sometimes we have
3 comments
Read more

Migrating an ASP.NET MVC 4 app from Azure websites to WinHost

By
About a week ago I've to migrate an ASP.NET MVC 4/EF5 application from Azure websites to WinHost. While the process was really smooth, there were some caveats related to database connections that I want to share with you. Create and setup the ftp profile on VS and configure the connection string was really easy, WinHost provide you those values and there is nothing special here. But once you deploy your website and try to see it online, you may get the “yellow screen of dead” with the message: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)" Assuming you wrote the connection string properly, this happens because you cannot use the default connection name in your web.c
2 comments
Read more