Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1883
  • Last Modified:

IIS Express Cache

I'm developing an ASP.Net Application using Visual Studio Pro 2013.  When I try to debug some JavaScript code the debugger displays cached code.  I found a workaround by changing the name of the JavaScript code file and changing all references in the aspx files.  The is tedious and can be error prone.  Is their and simpler way to deal with this???  I would like for the code break to show the code in the current state.

Thanks
0
Ray Turner
Asked:
Ray Turner
2 Solutions
 
Dan McFaddenSystems EngineerCommented:
I believe the browser is doing the caching of the .js file.  Have you tried purging the IE browser cache (all items), do a build and then debug?

If that doesn't really work, I would do:

1. clear browser cache
2. clear the appropriate ASP.NET temp directory
2a. like = C:\Windows\Microsoft.NET\Framework64\vX.X.X\Temporary ASP.NET Files
2b. like = C:\Windows\Microsoft.NET\Framework\vX.X.X\Temporary ASP.NET Files
3. rebuild app
4. restart IIS Express
5. debug
6. try in IE

Dan
0
 
LordWabbitCommented:
4. Restart IIS Express

it will resolve the problem, also fixes caching of css files.

I find that while developing writing the code 'inline' with the html and then moving the working tested code to a .js is a lot simpler than restarting IIS express all the time.
0
 
Ray TurnerSenior ConsultantAuthor Commented:
Thanks!  You both confirmed what other colleagues have told me.  It doesn't hurt to get a 2nd (and a 3rd) opinion.
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now