I think the guys in the .NET Framework team has this thing about vanity. Yeah! I call it code vanity. Not that its bad.. but its just funny how code has been getting beautiful. more beautiful and even more beautiful as the evolution of .NET goes forward. And it's a great thing too!

I remember seeing this last year when i was trying to put my hands wet with WPF. It's a pretty good five day course courtesy of Karsten Januszewski which you can complete just by reading and applying the things that you can find out from his set of useful links. A pretty good primer to WPF if you ask me(although i think there are sveral new articles in the past few months that i believe should be added to the list).

Learn from Karsten Januszewski here.

Hahaha! I did it! It took me 2 years to beat the Nobel prize winner with the same lastname as mine in the google search results for the keyword Rull but i finally did it :P

btw, the 3rd site on the list the site of my uncle ;)

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.

This is the first part our series about ADO.NET which is part of our Back To The Basic Series which is a series designed to teach beginners about the benefits of ADO.NET and to show how easy it is to use the ADO.NET in a short 10 to 15 minute video using Tagalog as the medium.  Our idea is to start from small demo application and build from there by adding new functionalities and refactoring the sample application on each part of the series.

On this demo you'll learn the basics of creating a connection to SQL Server, using a Universal DataLink to automatically generate your connection string to a database server, populating a DataSet using a SqlDataAdapter and assigning a DataSet to our GridView control.

>> Click here to view the video <<

Comments and suggestions are welcome! :)