This may be quite a simple question, but it's baffled me!
I've deployed our application to a test server quite a few times, and sometimes I get an error when deploying it. Usually the error is saying how a file your aspx is referencing isn't there, and so forth.
Trouble is, it then caches that page (seemingly) and even though I re-copy the files across, it doesn't always fix the problem.
Also, sometimes I find that copying my changes up to the server can take anywhere up to an hour to update. Is this due to the sites tag in the web.config setting caching settings that I need to disable?
Is there anything I can do to switch off caching entirely until the project's ready to go live to the public?
the path for this folder would be C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files or C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files depending on your environment
Hi,
This may be quite a simple question, but it's baffled me!
I've deployed our application to a test server quite a few times, and sometimes I get an error when deploying it. Usually the error is saying how a file your aspx is referencing isn't there, and so forth.
Trouble is, it then caches that page (seemingly) and even though I re-copy the files across, it doesn't always fix the problem.
Also, sometimes I find that copying my changes up to the server can take anywhere up to an hour to update. Is this due to the sites tag in the web.config setting caching settings that I need to disable?
Is there anything I can do to switch off caching entirely until the project's ready to go live to the public?
Thanks for any help!
Karl.