G
Guest
We have been using IE hosted winforms control for a while now and have a fair
bit of experience getting them to work. We have recently begun to adapt our
ASP.NET application so that it will work securely over https. However, we are
having problems getting hosted .NET winforms controls to work.
We are hosting the app on a windows server 2003 box running IIS6 with all
the latest service packs. When accessed over http everything is well behaved.
When accessed using https and an X509 client certificate created by
certificate services running on the same machine, the application crashes IE
with read/write errors on the first load. Once the user control is cached
(second, third load, etc) it seems to word ok.
I have stripped everything down so that I am just requesting a page with a
single user control:
<html>
<head>
<title>test</title>
</head>
<body>
<object id="MyUserControl" VIEWASTEXT
classid="/Test.dll#Test.TestControl">
</object>
<form id="Form1" method="post" runat="server">
All ok.
</form>
</body>
</html>
Where TestControl is the most basic user control VS.NET 2003 can create,
which I have strong named and added the AllowPartiallyTrustedCallers
attribute.
IIS has no http compression and caspol is off on the client.
Again, this page works and loads the control over http, but when accessed
over https IE either disappears completely or bombs out with memory access
errors. Second / time all is ok (until i clear the browser cache / GAC
download cache!). There appears to be nothing useful in the IE host log.
Does anybody know of any problems that might cause user controls not to work
over ssl or any related issues that would cause IE to behave like this?
bit of experience getting them to work. We have recently begun to adapt our
ASP.NET application so that it will work securely over https. However, we are
having problems getting hosted .NET winforms controls to work.
We are hosting the app on a windows server 2003 box running IIS6 with all
the latest service packs. When accessed over http everything is well behaved.
When accessed using https and an X509 client certificate created by
certificate services running on the same machine, the application crashes IE
with read/write errors on the first load. Once the user control is cached
(second, third load, etc) it seems to word ok.
I have stripped everything down so that I am just requesting a page with a
single user control:
<html>
<head>
<title>test</title>
</head>
<body>
<object id="MyUserControl" VIEWASTEXT
classid="/Test.dll#Test.TestControl">
</object>
<form id="Form1" method="post" runat="server">
All ok.
</form>
</body>
</html>
Where TestControl is the most basic user control VS.NET 2003 can create,
which I have strong named and added the AllowPartiallyTrustedCallers
attribute.
IIS has no http compression and caspol is off on the client.
Again, this page works and loads the control over http, but when accessed
over https IE either disappears completely or bombs out with memory access
errors. Second / time all is ok (until i clear the browser cache / GAC
download cache!). There appears to be nothing useful in the IE host log.
Does anybody know of any problems that might cause user controls not to work
over ssl or any related issues that would cause IE to behave like this?