Damian's Blog .NET from Geneva, Switzerland

1. 

   Ethem Azun
   February 25th, 2007 - 11:23

   Hi Damian,

   that was a great ajax intro! I found especially the extenders part to be very informative.

   Thanks,

   Ethem

   PS: I couldn’t stop shouting over and over “no! there! cutoff!”
2. 

   Kenneth
   February 25th, 2007 - 12:16

   You might consider changing the size of the downloads. It states GB and not MB

   Cheers
3. 

   dmehers
   February 25th, 2007 - 14:47

   Thanks Ethem — I’d like to say that typos are my way of getting getting audience participation

   Kenneth — good catch — I’ve changed the text to say MB instead of GB — might have put some people off!
4. 

   Edward Zeh
   February 25th, 2007 - 16:42

   Hi Damian.

   I just watched your presentation. It was a good
   introduction into the AJAX control kit. I also
   liked the free tool “Fiddler”, which I will use the
   next time when I develop a web-application. But the
   most useful thing I lernt from your presentation is the dot in http://localhost./xy, which forces the http-request to travel over the TCP/IP stack and that’s why
   fiddler is able to show the request.

   But there is one thing I would like to ask you.
   Is there a way to debug JavaScript-Code ? As far as
   I know Visual Studio can debug JavaScripts. Is there
   any other tool you can recommend to debug javascript ?
   In my opinion it is very time-consuming without debugger
   to find bugs in JavaScript.

   Thank you in advance for your answer.

   Edward
5. 

   Kenneth
   February 25th, 2007 - 21:45

   Edward,

   In Firefox you can install FireBug, an extension. You can, in your javascript, write: console.log(‘test’);, which outputs ‘test’, to the console window. Very cool tool. Check: http://www.getfirebug.com/

   Cheers,
   Kenneth
6. 

   dmehers
   February 26th, 2007 - 05:55

   Hello Edward,

   As Kenneth suggests, Firebug is good. I also use Visual Studio. It is handy sometimes to insert “debugger;” into your JavaScript to force the debugger to pop up when you need it.

   One handy technique is to define an HTML TEXTAREA in your page with the ID “TraceConsole”. Then in your code you can use Sys.Debug.trace(“some message”) to log messages, which go to the TEXTAREA (and the console on FireFox). http://ajax.asp.net/docs/overview/ASPNETAJAXDebuggingAndTracingOverview.aspx

   Another technique I’ve used, especially for situations where the running the debugger is likely to change the behaviour of the program I’m debugging, is to use my “tracejs” program which uses the debug API to trace all JavaScript code that executes: http://damianblog.com/2006/11/23/tracejs/ It has a massive performance impact though, so its only something I use “surgically”.

   Regards,
   Damian
7. 

   Edward Zeh
   February 27th, 2007 - 23:16

   Thank you very much for all the suggestions.

   Especially the link to the website is very useful.

   http://ajax.asp.net/docs/overview/ASPNETAJAXDebuggingAndTracingOverview.aspx
8. 

   Ali
   August 22nd, 2007 - 06:24

   Thanks for the presentation.
   Showing how someone can creat AJAX Control Extenders was very nice.

   PS: The voice was not clear, but not too bad.

Leave a comment Cancel reply