Awesomium migration issues (1.7.5) - Client won't launch WebCore

Problem:

I just upgraded to Awesomium 1.7.5 this week. I am developing WinForms with Awesomium. I used 1.7.1 before and everything was fine. But after I compiled my new exe with the Awesomium update, the client won't launch WebCore for Awesomium.

I've tried everything: giving the client all the DLLs and required files manually, copying the required files with the "copy local" option in Visual Studio 2012, and last but not least, I even installed the entire SDK on the client. But it (the client computer) doesn't launch WebCore, not even once.

So I analyzed the problem and every time the Awesomium process is not created (webview.isProcessCreated). It's funny because the Awesomium process is actually at work (see screenshots below).

After testing, I tried to run samples from Awesomium. I first compiled the Visual Studio examples -> does not start WebCore. Then I went to \ Program Files \ Awesomium Technologies LLC \ Awesomium SDK \ 1.7.5.0 \ wrappers \ Awesomium.NET \ Demos \ WinForms and started Sample.exe -> WebCore did not start at all.

I've tested this on x64 and x86 servers running Windows 7 Enterprise -> no chance.

Even if I reinstall .NET Framework 4.5.1, WebCore doesn't want to start.

What it looks like:

With visual styles enabled (Windows 7):

Visual Styles enabled With visual styles disabled (Windows 7):

Without Visual Styles

So now I don't know how to fix this. Do you know the solution or do I need to revert to an older version of Awesomium?

Edit - what debug.log says

[0104/130436: INFO: (0)] WebCore is now online. [0104/130436: INFO: (0)] Launching Awesomium 1.7.5.0

It is very interesting. The Awesomium process has started and the debug log says that WebCore is running and online.

Edit - Latest working version

I installed all available versions up to 1.7.1 separately and tested each version. The last worker is 1.7.4.2.

+3


source to share





All Articles