Question

We have a 2.x ASP.NET application, running on Windows Server 2k8R2.

We had to make a couple of changes and when we posted them to production the new changes are not working. When I check the physical page on the production server all of the new code is there, however the old code is still executing.

Something seems cached and I don't know where to check to un-cache it? I quickly restarted IIS but I can't bring server down for a long period of time until later tonight. I would like to figure out why this is happening so I can reset it now and also avoid it in the future. Any idea?

Was it helpful?

Solution 2

I don't know what is causing the problem but I did find a fix. When I touch the web.config it recycles everything. So I edited by web.config, just added some black space and saved it. Once I did this my page refreshed properly. This allowed me to keep running the server. If I edit web.config multiple times it will lock up and I'll have to restart IIS (learned this the hard way a while back) but for a one time update so I can keep running until I can recycle later at night, it worked great.

OTHER TIPS

It's the same as refreshing the application pool. Do that instead, it's much faster!

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top