Windows Form w/Internet Explorer
Has something changed between .Net Framework 1.1 and 2.0 concerning the ability to use Windows forms in IE.
In 1.1 I wrote a class library and then used it via the <OBJECT> tag in IE. I could access the public methods and properties of the DLL via javascript as well as using the <PARAM> tag. I wrote the same DLL in 2.0 and now I can only use the <PARAM> tag to access properties and methods, not javascript.
For instance my class library has a property, LabelText, that modifies the text of a Windows Form Label hosted in IE. Assuming my <OBJECT> tag has an id of myObject I could modify the text by the following BLOCKED SCRIPT
document.getElementById('myObject').LabelText = "Some Text";
That doesn't seem to work using 2.0.
Any thoughts?
I'm accessing the properties of my Windows Form control using javascript as you are and am having the same problem under version 2.0. Does anyone know how it should be done?
Here's something related...
I thought that assemblies compiled under 1.1 would continue to run under 1.1. Why do ours start running under 2.0 if 1.1 is still installed? I can tell because I need to adjust 2.0 security. Maybe it has to do with the fact that IE is hosting. Does anyone have a definitive answer?
II have a solution aiming at this scripting issue. It also solves the first time client side .NET framework installation issue, and provides a full trust mode to work around permission exceptions for smart clients easily.
It may run different controls on a web page with different versions of .NET framework runtime. For example, if you have a control compiled under v1.1.4322 and not compatible with 2.0, you may still run it under v1.1.4322 .NET framework runtime, even if the client side installed the 2.0 runtime.
Take a look at http://en.ezlag.com/site/335/lagloadernet.aspx
I was having similar problems with a control that worked fine under 1.1 not getting it's parameters under 2.0. Javascript and param tags still work, but the timing is a little different. My control was expecting the parameter values to be available for the load event. When my control is running under 2.0, these parameters aren't yet set. Placing the initialization code in the 'set' portion of the property eliminated any race condition there might have been and solved my problem.
