CODEWITHSUNDEEP
asp.netdebugging
nandin
nandin

Reputation: 2575

ASP.NET application behaves differently between production servers

Our asp.net app is running on 10 web servers, after we deployed the new release today, we noticed that some servers work, some do not.

The one not working has no exception, it just behaves the old way, it looks like still runing on old assemblies.

I have checked the assembly in bin folder between good and bad servers, the size, timestamp are all same, the code are same as well in reflector.

What else can I do? can you help to shed some lights?

thanks!

Upvotes: 0

Views: 330

Answers (3)

Aristos
Aristos

Reputation: 66641

To be absolute that the updates will reflected sure Use this procedure when you make the update.

  • Open/Create the app_offline.htm file on the root.
  • Update/copy the new files and binaries. Even if you just add an empty line on web.config your site will be restarted and updated
  • Delete/Rename the app_offline.htm file

You can do even now, open the app_offline.htm, add an empty line on web.config and saved so system note that at least one update have been done, close the app_offline.htm and your sites will be update with the minimum cost.

Upvotes: 0

Bobby D
Bobby D

Reputation: 2159

IIS/.net cache a the application in %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files (depending on the version of .net you are running, of course). You may want to delete the cached version of your application and reset iis (iisreset.exe) to see if that clears up your problem.

Here is a handy post on the subject.

Upvotes: 0

Kyle Trauberman
Kyle Trauberman

Reputation: 25684

Execute the command iisreset on those servers that are affected. This should force IIS to reload the assemblies into memory.

Upvotes: 1

Related Questions