G
Guest
Hi,
I'm trying to minimize the load time of a winform hosted in ie.
This winform calls a webservice.
It needs to download the XmlSerializers.dll, when doing this it start
probing in some wrong places (but not on the directory where the original dll
was downloaded).
If it didn't find an assembly containing the serialization info it
constructs reflecting on the assembly.
I found that the unwanted probing goes away adding in the html page where
the assembly is loaded a
<link rel="Configuration" href="myAssembly.htm" />
with this file containing only the envelope configuration tags:
<configuration>
<runtime>
</runtime>
</configuration>
(the Application base became the directory where the assembly was downloaded).
Anyway I see that the file is downloaded 2 times per assembly no matter if
the file is the same.
Why is this happening?
Is the correct way to handle this situation?
I'm trying to minimize the load time of a winform hosted in ie.
This winform calls a webservice.
It needs to download the XmlSerializers.dll, when doing this it start
probing in some wrong places (but not on the directory where the original dll
was downloaded).
If it didn't find an assembly containing the serialization info it
constructs reflecting on the assembly.
I found that the unwanted probing goes away adding in the html page where
the assembly is loaded a
<link rel="Configuration" href="myAssembly.htm" />
with this file containing only the envelope configuration tags:
<configuration>
<runtime>
</runtime>
</configuration>
(the Application base became the directory where the assembly was downloaded).
Anyway I see that the file is downloaded 2 times per assembly no matter if
the file is the same.
Why is this happening?
Is the correct way to handle this situation?