ASP.NET AJAX Discussion and Suggestions

Re: Ann: TraceJS -- logs all JavaScript that Internet Explorer executes (no code change required)

ppychu — Wed, 17 Oct 2007 16:16:21 GMT

I downloaded the zip and unzip.

I double click the tracejs.exe file -- nothing happens.

I executed it at a DOS prompt -- nothing happens.

But I do see the process in task manager.

Should there be a GUI or somehing that will come up when I run it??

Not sure how to use this TraceJS

Can someone please kindly help?

Thanks

Re: Ann: TraceJS -- logs all JavaScript that Internet Explorer executes (no code change required)

dmehers — Tue, 28 Nov 2006 12:02:25 GMT

FWIW I've found the problem and updated the blog entry and associated software. If you have not had VS 2003 installed before then there is a good chance you won't have the Active Scripting Debug API installed, which is why the above error occurred. I've updated the posting and associated software to explain where it can be downloaded.

Re: Ann: TraceJS -- logs all JavaScript that Internet Explorer executes (no code change required)

dmehers — Tue, 28 Nov 2006 07:49:24 GMT

I'm getting some reports of people not being able to run this, getting an error:

System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {0C0A3666-30C9-11D0-8F20-00805F2CD064} failed due to the following error: 80040154.

at TraceJS.Form1.InitializeMachineDebugManager() in c:\Documents and Settings\nikhilko\Desktop\TraceJS\TraceJS\Form1.cs:line 73

If you get this, please let me know.

Thanks,

Damian

Ann: TraceJS -- logs all JavaScript that Internet Explorer executes (no code change required)

dmehers — Mon, 27 Nov 2006 16:01:18 GMT

I've written a small utility in C# which uses the Active Scripting Debugging API to log all JavaScript that Internet Explorer executes. There is no need to instrument your code, since it hooks into IE at a pretty low level.

The tool and the source are available for free: http://damianblog.com/2006/11/23/tracejs/

It can be useful for understanding what is going on inside the ASP.NET AJAX runtime, and also to help understand what is going on in your own code without having to step through in the debugger.

If you do want to trace inside the ASP.NET AJAX runtime then you might want to have the ScriptManager return the ASP.NET AJAX Runtime JavaScript files from the file system instead of from the embedded resources ... I explain how to do that here: http://damianblog.com/2006/11/27/scriptmanager-scriptpath/

Damian