embedded winforms in IE wont cache

G

Guest

I have a problem. The issue is that my embedded winforms in IE will not cache no matter how hard i try. They seem to goto the download assembly cache but they dont load from there like the framework documentation has stated. I have tried versioning, strong naming, and everything else i can think of.

Any response, esspecially from MS would be great! I would like to know if this is a bug that is expected to be fixed in the .NetFramework, or is there a work around till the bug gets fixed.

Thanks!!!!! :)

Here is some of the previous posting that i had made, followed by MS Response ****:

Hi Bryan,

It's really good to hear someone having the same problem (sorry to say) - precisely the same problem is KILLING my released

application stone dead because of performance issues over low bandwidth connections. I AGREE, the controls are NOT being

loaded from the download cache when available, and the documentation (I am certain) INCORRECTLY says this will happen. I

have based many months of development based on this concept, believing the documentation and suspecting it is me misreading

the signs or doing something wrong. I now no longer believe this to be the case. Can someone out there at Microsoft help?

This is a real cry for help you're hearing here. Why are IE hosted controls not being loaded from the download cache when

no newer versions are available on the server?

Please find attached similar posting (unanswered) from myself on the sister windowsforms.controls newsgroup:

Subject: IE hosted control and the download cache 1/16/2004 3:47 AM PST

Hi,

Should my IE hosted Windows Control be invoked from the download cache after it's first use?

It appears that my Windows Control is being downloaded every time from the Web Server. My understanding is that every time

a Windows Control is invoked from within an HTML <Object> tag, that the CLR first checks on the server to see if there is a

new version of the assembly is available. If there is not, then the last downloaded assembly will be invoked from the

download cache, if one exists. However, it appears that my control is being download every time, and as available bandwidth

narrows, the control takes a REALLY long time to download/invoke, even though I told my managers (perhaps mistakenly!) that

they will only experience this the first time they invoke a new version of the component from the web server.

I had read that there may be a connection between strong naming an assembly and the download cache, so that versioning can

work correctly, however I've just added a stong name to my assembly (by adding [assembly: AssemblyKeyFile(@"....snk")] to

AssemblyInfo.cs) but it appears to have made no difference.

Should I be doing more to get my control invoked from a users download cache whenever possible?

Many thanks,
Richard Sheridan


----- bryan wrote: -----

The problem is that when we embed a usercontrol in a html page the control is noty cached on the client as specified by numerous MSDN articles. I have tried everything i can find on trying to cache winform dll's in the assembly download cache. Is there something im doing wrong? Please Help! Our company is riding its entire future programming on .net. If anypne has any good sample code on something that works, or perhaps a fix, please let me know.

Is this a bug that will be fixed in framework 2.0? I hope so because we have a lot in our company riding on it.

Thanks, Bryan


Print | Copy URL of

*** and what MS said ********
have you examined the download cache? (gacutil /ldl ) You may have
multiple versions of your assembly there. If they list (0.0.0.0) as the
version then you have your answer: you haven't attached a version number to
your assembly:

eg,
[assembly:AssemblyVersion("x.y.z.w")]

Be sure to specify a full version, no *'s.
 
P

Paul Hetherington

I have the same issue. As long as IE remains open the NTD uses what is in
the download cache. As soon as IE is closed and restarted. It redownloads
the assemblies even if they havn't changed.

-Paul
 
G

Guest

Exactly, our company is betting alot on this working. Hopefully MS will propose a fix.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top