Monday, October 29, 2012 9:16 AM
in case to implement advanced functions for my embedded device, i have to include the webbrowser-control into my C#-application, that
Debugging this application with VS2005 and the Pocket PC 2003 SE-VGA-Emulator works perfect without any problem.
Can someone give me a tip, how can I solve this problem?
Thx in advance,
Monday, October 29, 2012 3:52 PM
I'm sorry that my answer is a big foggy. If it were me, I'd look at the source for IESAMPLE and identify anything that is being done to configure the WebBrowser control that I am not doing in my application. It occurs to me that Internet settings might be available to disable script processing.
It was not clear from your message that opening your page in WEC7 in the browser correctly processes the script. Does it?
Tuesday, October 30, 2012 7:34 AM
thank you for answering. I will describe the problem a bit more precisely now.
I also had tested to change the internet-security options of the embedded system to enable everything, but this does not help.
Maybe you can help me to understand the problem a bit more to find at last an solution for this. So correct me please if i'm wrong.
If i include a the browser-control from "System.windows.forms.webbrowser" into an application, the application will use the browser of the system this application is currently running and is using the internet-security options activated on this system.
Is "hacking" the code of IESAMPLE only the last chance?
And if this is true, can you addvice me a site where i can find further information about it?
- Edited by Peter Kowal Tuesday, October 30, 2012 7:40 AM
Tuesday, October 30, 2012 3:32 PM
Yes, the .NET Compact Framework WebBrowser control uses the actual native code control in the OS. It's just a wrapper as with TextBox, ListBox, etc.
It sounds like you're saying that yes, IESAMPLE ***ON YOUR TARGET DEVICE*** works, but your application does not. If so, you don't have to modify IESAMPLE, you just have to figure out what it is doing that your application is not doing.
Wednesday, October 31, 2012 9:52 AMPaul,
thank you for supporting me. That was very usefull for me to set my focus onto the right part of the possible sources of error. Once together I have to investigate the target device now and possibly I also have to contact the manufacturer of this system for a targeted search. In case of our upcoming bank holiday weekend, it will take some time. Last not least, I will post in this thread the results what i figured out , so it maybe helps otherones with the same prob. But don't expect the results for this week, please.