Hi, I tried out your SampleApplication.exe and it worked great, was able to pull up www.google.com without any issue.
However, if I reference Awesomium.CApi.NET.dll in my .NET 2.0 app and then copy Awesomium.dll, AwesomiumProcess.exe, icudt42.dll and the "locales" folder and run my app using your VB sample code as a guideline, the web control just displays a white box and nothing else ever happens.
Maybe you are missing to start update timer:
WebCoreUpdateTimer.Start(25); // after awe.WebCore.Initialize(init);
Since web core doesn't have it's own message loop, the update timer is needed to dispatch web core's message events.
This .NET wrapper for Awesomium is quite out of date now and won't be maintained, so I don't know if it's a good idea to use it for a new project...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2014-01-31
Thanks, that was exactly what I was missing! I'm hoping to force my clients onto .NET 4.0 in the near future, so my intent is to just rely on this wrapper in the meanwhile.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I tried out your SampleApplication.exe and it worked great, was able to pull up www.google.com without any issue.
However, if I reference Awesomium.CApi.NET.dll in my .NET 2.0 app and then copy Awesomium.dll, AwesomiumProcess.exe, icudt42.dll and the "locales" folder and run my app using your VB sample code as a guideline, the web control just displays a white box and nothing else ever happens.
This is my code:
Any suggestions as to why this would fail to load or display anything when the sample app works fine on the same machine? Thanks.
Hi,
thanks for taking a look into this project.
Maybe you are missing to start update timer:
WebCoreUpdateTimer.Start(25); // after awe.WebCore.Initialize(init);
Since web core doesn't have it's own message loop, the update timer is needed to dispatch web core's message events.
This .NET wrapper for Awesomium is quite out of date now and won't be maintained, so I don't know if it's a good idea to use it for a new project...
Thanks, that was exactly what I was missing! I'm hoping to force my clients onto .NET 4.0 in the near future, so my intent is to just rely on this wrapper in the meanwhile.