Hi.
I've just hit a similar problem. We have a desktop app which is mainly C#. We are now looking to embed web modules into the application and Awesomium seems to have been identified as a good solution.
But I have the same problem as the initial poster here. The webmodule is identified as one giant object. None of the individual controls are shown. I've had a bit of a google about and this seems to be a common problem with Awesomium. I found mention of various automated tools and none of them could interpret Awesomium rendered pages properly.
Speaking to one of the deveopers here he seemed to thin that it used some wierd rendering method rather than simply displaying native HTML, which might explain it.
When I object spy any control in the webmodule, it stop at the top level.
Example below:
Sys.Process("<OUR APPLICATION>").WinFormsObject("ShellForm").WinFormsObject("workspace://Infrastructure/Layout").WinFormsObject("ShellLayoutView").WinFormsObject("toolStripContainer").WinFormsObject("ToolStripContentPanel", "", 1).WinFormsObject("_backgroundPanel").WinFormsObject("workspace://Infrastructure/Primary").WinFormsObject("SingleViewLayout").WinFormsObject("workspace://Infrastructure/Workspace").WinFormsObject("WebModuleFrontPageSection").WinFormsObject("WebBrowser", "").Window("Chrome_WidgetWin_0", "", 1).Window("Chrome_RenderWidgetHostHWND", "", 1)
And thats it. Not much you can do with that except co-ordinates and clicks. Which is not good.
As it stands, I'll have to test it separately in Chrome and then it will have to be manually integration tested into our main application.