Keith Rull

I've been working with alot of Ajax lately(this includes code and laundry :P) and just realized that i've been doing some unecessary code after reading this article. I think I got hooked so much with the Ajax-hoopla that I forgot that not everything should be done via Ajax.

Below is an outline of what Jack Herrington suggested.

• Polling on a timer when you don't need to
• Not inspecting the return results in the callback
• Passing complex XML when HTML would be better
• Passing XML when you should pass JavaScript code
• Doing too much on the server

Read more about this article here.

*Update: I did some research and found out that Michael Schwarz, the creator of Ajax.NET has also a great list of things to avoid in his article Top 10 Mistakes When Using Ajax. Great read.

I was running a test on my Web Server today when a friend of mine IMed me about an interesting question about .NET. He was a new programmer for this company and the old developer that he replaced was running production(oh my) applications right of his desktop. The IT manager was getting worried because they dont have a list of applications that the old guy did because the old developer didnt do any turnover(he was fired =)) and alot of the apps that he did were essential to the business(the company was a small accounting firm). So my friend asked me if theres a way to figure out which applications are running using managed code so that they could check the application and move it to a more secure and dependable server.

In part 2 of our Back To The Basics Series, Keith discusses how to pass parameters to your inline SQL Statements, read a connection string from the web.config and the use of a static class for utilities. He also refactored(a little bit) our original solution to make the code more manageable.