Howdy!
First let me thank you for the development effort on this solution!
We have a web based app deployed that's pretty typical: data management, some reporting tools, label generation, etc. (it's for asset management)
While the original spec called for "web based" the users are occasionally in situations where they don't have connectivity (either direct, or wireless), *but* need access to the application. Originally we intended just to use a custom spreadsheet but it lacked some reporting/printing capabilities and data entry control (without getting into an incredibly complex, macro driven worksheet). Then I started down the path of a standalone desktop/client framework - this was OK, except it required maintaining a completely separate codebase (and moving between the two was giving me a headache :)
Then I stumbled on your solution which would allow me to repurpose the web code, and just make a few tweaks to bundle in a different DAL/DB (I'm using SQL CE). Anyway, it's a huge time saver and keeps me in web based methodologies which are my strong suite anyway. I dynamically generate the required CE support file, wrap it up into the ZIP with the web code, and they download, unzip and run from their desktop ... awesome!
OK, enough of my life story, here's my problem:
On my dev notebook running Vista/32 the Seamless works, but the Simple does not. The simple opens the browser and points to a non responding server.
On two XP Pro machines, the Simple works, but the Seamless does not. The seamless opens the app, shows the loading panel, but never gets any further (and never times out).
The client machines for the time being will all be XP, and the simple works, so it's not a complete deal breaker. However, I do like the Seamless better because it contains the browser into a "desktoplike" experience, and removes anything that looks like a browser that might confuse the user.
Any ideas about this?