<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: Microsoft Script Debugger</title>
	<link>http://ask.metafilter.com/9311/Microsoft-Script-Debugger/</link>
	<description>Comments on Ask MetaFilter post Microsoft Script Debugger</description>
	<pubDate>Tue, 10 Aug 2004 14:38:19 -0800</pubDate>
	<lastBuildDate>Tue, 10 Aug 2004 14:38:19 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>Question: Microsoft Script Debugger</title>
		<link>http://ask.metafilter.com/9311/Microsoft-Script-Debugger</link>	
		<description>&lt;a href=&quot;http://www.microsoft.com/downloads/details.aspx?FamilyID=2f465be0-94fd-4569-b3c4-dffdf19ccd99&amp;displaylang=en&quot;&gt;Microsoft Script Debugger&lt;/a&gt; - Has anyone actually gotten this thing to work properly?  I&apos;ve got some JavaScript (that I didn&apos;t write) that is completely bisbehaving in IE (although it produces no errors...it works fine in FireFox, so my usual line of attack doesn&apos;t work).  I&apos;ve used the View | Script Debugger | Break at Next Statement and then refreshed the page.  It opens the debugger app but doesn&apos;t open any source files and it most certainly doesn&apos;t break.  Has anyone seen this behavior and overcome it?</description>
		<guid isPermaLink="false">post:ask.metafilter.com,2004:site.9311</guid>
		<pubDate>Tue, 10 Aug 2004 14:02:26 -0800</pubDate>
		<dc:creator>mmascolino</dc:creator>
		
			<category>microsoft</category>
		
			<category>windows</category>
		
			<category>script</category>
		
			<category>scripting</category>
		
			<category>debug</category>
		
			<category>debugger</category>
		
			<category>developer</category>
		
			<category>develop</category>
		
			<category>program</category>
		
			<category>programming</category>
		
			<category>javascript</category>
		
	</item> <item>
		<title>By: yerfatma</title>
		<link>http://ask.metafilter.com/9311/Microsoft-Script-Debugger#174781</link>	
		<description>&lt;em&gt;Has anyone actually gotten this thing to work properly?&lt;/em&gt;&lt;br&gt;
&lt;br&gt;
No. If you have a version of Mozilla available, take a look in that. The JavaScript console (under Tools) will give you actual meaningful feedback (as opposed to &quot;Line 1: Object Expected&quot;). If that&apos;s not enough, you can add on the Venkman Debugger to versions of Moz. I know you&apos;re trying to debug an IE issue, but this is my advice as someone who&apos;s spent hundreds of hours debugging JavaScript. IE and it&apos;s debugger are worse than useless.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2004:site.9311-174781</guid>
		<pubDate>Tue, 10 Aug 2004 14:38:19 -0800</pubDate>
		<dc:creator>yerfatma</dc:creator>
	</item><item>
		<title>By: kokogiak</title>
		<link>http://ask.metafilter.com/9311/Microsoft-Script-Debugger#174907</link>	
		<description>Agreed, MS Script debugger is often worse than useless - it has led me down a number of dead-ends before, or worse, just given me a blank stare -  sounds like what you get. Try venkman, or line-by-line hand-tweaking, They will lead you to the root cause.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2004:site.9311-174907</guid>
		<pubDate>Tue, 10 Aug 2004 21:51:01 -0800</pubDate>
		<dc:creator>kokogiak</dc:creator>
	</item><item>
		<title>By: yerfatma</title>
		<link>http://ask.metafilter.com/9311/Microsoft-Script-Debugger#174955</link>	
		<description>I just re-read the question and realize the Firefox debugger won&apos;t help if it doesn&apos;t break in Moz. Venkman might be some help. Otherwise it&apos;s a question of how well-written the JS currently is. If it&apos;s shitty, like a bunch of spaghetti code, you might spend some time turning it into functions/ classes (not sure if it&apos;s big enough to warrant that) to try to lock down where the problem is occurring and then work from there. Plus it&apos;ll be easier to fix/ maintain once you find the problem.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2004:site.9311-174955</guid>
		<pubDate>Wed, 11 Aug 2004 04:22:07 -0800</pubDate>
		<dc:creator>yerfatma</dc:creator>
	</item><item>
		<title>By: mmascolino</title>
		<link>http://ask.metafilter.com/9311/Microsoft-Script-Debugger#174983</link>	
		<description>Thanks for the suggestions.  Before I lost all my hair, I tried doing a magic reboot and the debugger actually works (although to say that it is easy to use or useful would be an understatement).</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2004:site.9311-174983</guid>
		<pubDate>Wed, 11 Aug 2004 06:36:27 -0800</pubDate>
		<dc:creator>mmascolino</dc:creator>
	</item>
	</channel>
</rss>
