Chris- <assuming prior to default security changes>
Our product managers and such were quite excited about this technology because it easily provided a "unified interface" for products. Whereas some products were simple enough that a Web App would suffice, others were too complex for basic web controls. There were specific reasons the simple ones were required to be Web-based, but being able to add the more complex ones as accesible via the browser made the "single-point of entry application" relatively simple. <after default security changes> We didn't want to dictate security changes on the client so we rearchitected and created a thick client unified interface that hosts the Web App. In short, they aren't much use, anymore. . . Jacob A. Grass -----Original Message----- From: Chris Sells [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 1:15 PM To: [EMAIL PROTECTED] Subject: [DOTNET] What use are WinForms controls hosted in IE? Since web pages are for reach to the least common denominator, what good are WinForms controls hosted in a web page? Not only do they require .NET to be installed on the client, throwing away the reach benefit, they need to be *fully* trusted to fire events, throwing away the sandbox that .NET provides for semi-trusted code. Or, if you stay semi-trusted and avoid firing events or communicating in any way with the hosting page, why be hosted in IE at all? Why not just deploy a WinForms EXE? I don't get it. Is it the ability to flow graphics and text? Chris You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
