VSCODE Terminal Does Not Recognise Command

If you run the terminal in VSCode on Windows, and the command is not recognised, make sure that the Path environment variable includes the following path: C:\Users\user.name\AppData\Roaming\npm. Also, make sure that this entry is at the beginning of the list because your path list can be too big for the VSCode Terminal to handle. This can be determined by typing echo %PATH% in your terminal window, and comparing it with the external cmd.exe window.


Debugging Websites

When faced with problem websites that do not render as they should in different browsers, there are three sets of debugging tools that are at your disposal. The tools are FireBug which is a FireFox plugin, the IE9 Developer Tools, and Google Chrome’s Developer Tools. Each set of tools has its own set of useful features.

I will leave it up to you to investigate each set of tools and their features. Personally, I like FireBug for the way it displays the DOM and various types of errors, Google Chrome for the way you can inspect elements and step through JavaScript, and IE9 for the Layout feature to help you find formatting issues.

Another thing to be aware of is that Opera does not like empty strings. To get round this, place a space inside the double quotes.

When developing new websites that simple work in all different browsers with graceful degradation, I suggest using Google Chrome Frame and HTML5 Boilerplate.

Debugging JavaScript in VS2010

In order to debug JavaScript using Visual Studio 2010, make sure that you have Internet Explorer set as your default browser, and that you have both the internet options “Disable script debugging (Internet Explorer)” and “Disable Script Debugging (Other)” unticked. Within VS2010 under the Tools->Options->Debugging->Just-In-Time entry make use that “script” is ticked.

Also, other sources have stated that “When Silverlight debugging is enabled, it disables ASP.NET debugging.”