Hi all,
I've added a shared remoting interface to WinForm in IE control. Since
adding the DLL, load times have double - it takes ~2 minutes to load. The
DLL is 16K and only contains shared interfaces.
I checked the Fusion binding log (as well as my own custom logging),
initial load takes place almost instantenously - all DLLs are downloaded
right away.
The moment I hit my first remoting line - the code stalls and takes ~2
minutes to complete. I noticed in my fusion binding log that .NET seems to
re-request the DLL because it "already exists in the local cache". I've
cleared my local cache to no avail.
Once everything loads, it runs fast - but the inital load is sooooo slow.
Any ideas why code w/ interfaces + remoting take so long to load?
Thanks.
Spam Catcher - 24 Apr 2006 19:34 GMT
> Hi all,
>
[quoted text clipped - 15 lines]
>
> Any ideas why code w/ interfaces + remoting take so long to load?
The problem seems to be related with IE's TCP IP Stack... I found a
google article and it seems to have fixed the problem.
Basically you put this "fake" code before your remoting code:
Try
Dim loaderPage As String =
System.Reflection.Assembly.GetExecutingAssembly().CodeBase.Replace
(".dll", ".aspx")
Dim request As HttpWebRequest = WebRequest.Create
(loaderPage)
Catch ex As Exception
End Try
code loads instantly... weird.
http://groups.google.ca/group/microsoft.public.dotnet.framework.aspnet/br
owse_thread/thread/4d4c05a62d37467/5299bf58c242a513?
lnk=st&q=Winform+IE+Remoting&rnum=3&hl=en#5299bf58c242a513