ASP.NET Woes

I might have mentioned in the past a case where asp.net does not use the latest code no matter what you try, and the only way I made it work was to compile in debug mode, deploy those dlls and reload the site.

Well, I found out one more case today. This can happen if you massively change web.config also.

No matter what you try, if your codebase is big enough, it will not use the latest configuration. You can try iisreset, reboot or even deleting the temporary internet files from the .NET folders within the system folder.

The only way to get this to work is to set debug="true" in the web.config file and even then, it takes some time for this to take effect.

Comments

Popular posts from this blog

Tutorial: Using Google Cloud Storage from C# and .NET

Late 2008 Macbook only giving 1.5 gb/s speed with 6 gb/s Intel SSD?

Enable Visual Studio to use more than 2GB of memory