ASP.NET Web App Code Not Updating On Production Server

Question

5.00/5 (1 vote)

See more:

Has anyone had a situation where code changes work perfectly on one server but not another? I have a situation where I made a few ASP.NET codebehind changes and everything tested fine. QA signed off on the changes, we move the changes to production and now nothing. The web app in production does not error or crash, it just ignores the changes. I've been told that the Test and Production servers and IIS versions are identical.

Any suggestions where I should start looking? I've verified that the aspx and dll files are moved and the correct version. We've tried restarting IIS and rebooting the server. Nothing is working.

Posted 24-Nov-10 7:57am

Don Burton

Add a Solution

3 solutions

Solution 2

HI,
You didn't mentioned you are uploading compiled files or uncompiled files?
If you are uploading uncompiled files, then the problem you posted might occurs due to temporary files under framework. Workaround is rename your web.config files for time being, try to browse the site. Obviously your site will give error, now restore the web.config file. This can do the trick, idea is force engine to re-compile the site again and it will wipe out temporary files.

I hope this will help.

Posted 24-Nov-10 9:00am

Shahriar Iqbal Chowdhury/Galib

Solution 3

Try to re-save web.config on production.
Just change something and re-save it.
It will clear the cache, restart the application, etc...

Good luck.

Posted 24-Nov-10 13:51pm

Ed Guzman

Comments

Uwe Keim 25-Nov-10 1:37am

That did not always work for me. In fact, I sometimes experience that any white-space change in web.config is ignored, so I end up adding comments with random numbers.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Uwe Keim · Accepted Answer · 2010-11-24T08:28:00

Happens to me, from time to time, too. Especially with resource file changes (resx) that are dynamically compiled.

What helped me is to delete the contents of the "Temporary ASP.NET files" folder. Try IISRESET if some child folders are locked. Also ensure you delete the ones for Framework and Framework64, too.

You finde the folder somewhere similar as in c:/windows/microsoft.net/v4.xxx/... (sorry, can't find backslash on that MacBook).

Cheers
Uwe