This is a generic question. Nevertheless it's still a mystery and needs explanation...
Recently our application was deployed in production with latest code. It's an ASP.NET MVC 3
application using WCF
as service and SQL Server
for DB. The deployment is automated process and the elevation from DIT, SIT, Stage to Prod is automated too.
After deployment, while testing we found the application in production is not behaving the same way it behaved in other environment. There were functionality mismatch. DIT, SIT and Stage are working as expected but Prod won't. We checked the Dlls in all prod servers they are the latest set. I debugged in DEV and found it working as expected.
Unable to find explanation, we did IISRESET
in all prod servers and guess what!.. It started working as expected, no issues till now ... :)
- Is there a good explanation why IISRESET solved the issue?
- Is IISRESET mandatory after a deployment?. My understanding is even config/dll change will force application recycle and latest dlls will be picked..
- Is there any other steps we could have taken? Time was a constraint, we need get the prod boxes up ASAP.