IIS Enable content expiration and .Net objects

[Mario Hébert]

I have a simple C# object(class) that I reference in a <OBJECT
classid="mydll.dll#nmsp.Ctrl"> tag of an HTML page generated by ASP.net.

In a case where the Enable content expiration isn't checked for my website,
i can call a public method of the object via javascript and it's working.
When the Enable content expiration(immediately) is effective for my website,
i always have a javascript error telling me that the object or the method
doesn't exist...

Someone knows something about this problem?

As a test, i setted the content expiration to off and rebuild my component.
The javascript still working.... I setted the content expiration on to
immediately and tested the component without recompiled it...It still
working. But, if a rebuild it in the website when the content expiration is
on, and try to use it in javascript, i've got the error....

Notice that the assembly is in the root of my website and i'm using IIS 5.1

Mario

 

[lb]

....just noticed this behaviour too.
another way to test this is to simply rename the dll making sure the
new name is reflected in the HTML - with content expiration on the
object wont load - when set to off it will load properly.
(simply switching the expiration on/off in iis manager wont show the
problem ie. guess once its cached it stays cached)