Anilr,
Let me be clear about what I am trying to do.
Let's suppose that caching ISAPI is enabled for a particualt web app. on the IIS 5.1. If I place a .dll in the GAC and then call it from that web application in ASP.NET 2.0, then all is fine.
However, if I go to rebuild that .dll from within ASP.NET 2.0 to return a different hard coded string, and then replace the original .dll in the GAC, (effectively replacing the oringinal .dll with the same assembly version and build), IIS does not see the different string when I call the .dll because it caches the .dll. That is why I use: "cscript.exe adsutil.vbs set w3svc/1/root/myWebApp/cacheisapi 0" (without quotes), to disable the ISAPI cache. When this is done, and IIS is reset, IIS 5.1 does not cache the .dll in the GAC anymore. This means that when no matter how "many" times I rebuild my .dll in ASP.NET 2.0 with different hard coded strings to return and place that new .dll in the GAC, (with the same assembly version and build), the new string will always show when that .dll is being called from any app. This is becuase caching is turned off at the ISAPI level.
I have tried this scenario dozens of times, and it certainly resolves the issue of replacing the same .dll in the GAC, (with the same assembly version and build), and still getting the new hard coded string, simply becuase the Cache ISAPI was turned off for that particular website.
If I were to leave the cache ISAPI on, then IIS caches the .dll and will never retrieve the new string, even after I rebuild my ASP.NET 2.0 .dll and replace it in the GAC with same assembly and version.
I could use a differenct assembly and build version, instead of turning off the ISAPI cache to resolve it, however I would like to use the same (assembly and build version).
So the question I pose to you is: how do I turn off ISAPI cache in IIS7, as "cscript.exe adsutil.vbs set w3svc/1/root/myWebApp/cacheisapi 0" (without quotes), does nothing for me in IIS 7?
thanks ahead of time, theadmirableone