Flush the user cache, reset settings for TFS and VS

https://blogs.msdn.microsoft.com/willy-peter_schaub/2010/09/15/if-you-have-problems-with-tfs-or-visual-studio-flush-the-user-cache-or-not/

Delete the contents from the following folders
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\Team Foundation
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VisualStudio
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VSCommon
Go to the Visual Studio IDE folder in command prompt and Run the following command “devenv /resetuserdata” from the Visual Studio IDE folder.
Typical location for 64 bit: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
Typical location for 32 bit: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE

Some response from server despite IIS already stopped

When IIS is stopped on a server, it’s expected that every requests to the server afterwards will return status 0.

If the status code is anything aside from 0, that means that another service is running on the same port in the same server. For testing, make sure those are stopped.

One such service I encountered recently was the SQL Server Reporting Services. If it runs while IIS is turned off 404 will be returned instead of 0.

Strategy to debug Javascript

Make sure you read the relevant API docs.

Use Chrome’s developer tools, Firebug, or IE’s, and Visual Studio debugger, they are awesome.

Use console.log and alert in code when necessary when tracing code is difficult.

Run JS scripts from JS console.

Don’t be afraid to trace through third party’s frameworks and libraries when necessary.

 

Chrome DevTools was disconnected from the page, IE error out of stack space

This issue, according to the stackoverflow answers seem to stem from the webpage having.

  • Infinite recursion(likely)
  • Infinite loop(not likely?)

The same issue will make IE display an error: “SCRIPT28: Out of stack space”

If you can debug and find out the infinite recursion, maybe it’s possible to fix this issue.

500.19 – Internal Server Error – The requested page cannot be accessed because the related configuration data for the page is invalid

Today I faced this error while trying to run a web application.

It turned out that it was occurred in a REST request to the server to retrieve a JSON file. I tried to solve this issue by first opening IIS and check the declared MIME types under the web application, then it complained that there is a duplicate entry in the web.config file.

It turned out that if the web.config file contains a declaration for the MIME type .json and under the application in IIS the MIME type is also declared, IIS will complain. I solved the issue by removing the MIME type declaration from the web.config file.