http://www.microsoft.com/downloads/details.aspx?FamilyID=2f465be0-94fd-4569-b3c4-dffdf19ccd99&displaylang=en
...make sure in IE you enable script debugging by going to Tools > Options > Advanced > uncheck both "disable script debugging" options > Apply > restart IE > Now you can use the above debugger via View > Script Debugger > Open
NOTE: If VWD script debugging is working for you, installing the above tool displaces it. I am an ASP.NET developer, so I actually had to un-install the script debugger from above, then re-install VWD to get it back working again (current new job place has no full VS licenses as of now so I have to use VWD). Also, if you DO have the full VS.NET (2003 or 2005), don't even bother with the above link, you can debug js via those with no problems as Jerod pointed out.
On 6/7/06,
Jerod Venema <[EMAIL PROTECTED]> wrote:
IIRC, ie will pop up the "debug" option when you turn on script
debugging. At that point, you can tell it to debug with VS, and it
*should* load everything up for you. At least, that's worked for me in
the past....
FWIW.
-Jerod
On 6/6/06, Maninder, Singh <[EMAIL PROTECTED]> wrote:
>
>
> I keep getting some front page extensions not installed on the server or
> something similar.
> _______________________________________________
> Rails-spinoffs mailing list
> Rails-spinoffs@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
>
>
>
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
