Posted by Robert Half Technology on Tuesday, December 30, 2014 - 08:00 | Follow me
When building a website, the last thing you want to discover is that the site doesn’t download quickly or correctly, or has bad links. If you’re constructing in Microsoft Internet Explorer (IE), fixing coding is simply a matter of learning how to debug with Microsoft Developer Tools.
Designer Nick Pettit points out in his debugging HTML and CSS post on the Treehouse blog that each problem is unique and will have its own debugging issue to solve. There are also what he calls basic “sanity checks” developers can turn to, such as checking for syntax errors and display problems, and searching for cross-browser issues.
As Rob Gravelle, designer and founder of Gravelle Web Designs, explains at HTMLGoodies.com, Microsoft Developer Tools for Internet Explorer are similar to Firefox’s tools. Their purpose is to help debug JScript code, the version of ECMAScript that runs on IE. He adds, “Code that runs perfectly in Firefox may or may not encounter problems in IE.” This is important, Gravelle says, because codes across different browsers don’t always match up. That’s why a website will look fine on one browser but not another. If you’re using IE11 (which you should be for security reasons), accessing Microsoft Developer Tools is as easy as pushing the F12 button on your PC keyboard. (You can also go to IE’s menu bar and select “F12 Developer Tools” on the “Tools” menu.)
How the tools work
IE12 is expected to arrive soon. Will Microsoft build on its IE11 developer enhancements? It’s likely that developers can expect to see new features such as deep linking and open-source programming opportunities. It also looks like IE12 may be even more developer-friendly than past versions of IE. W
What are your favorite debugging tricks using Microsoft developer tools? Please share your tips in the comments section. Looking for some tips for debugging Microsoft.NET framework for mobile? See this post.