One popular way to create a rich web experience is using DHTML with XMLHTTP to draw the UI instead of constantly hit the server again. Debugging this process, however, can be quite tedious as a View Source will only show the text sent from the server.
Here's the URL file, you can save to your favorites and use it from there:
Feel free to make a plugin that loads this in a favorite text editor.
Jeremy just posted about VB.NET vs C# in the enterprise, so I thought I'd share the standard language at my employer.
Prior to .NET, the overwhelming majority of development was in VB. Even the large, mission-critical (what used to be mainframe-driven) systems were VB-based. Don't get me wrong, it's still a rather intense enterprise architecture based on Microsoft DNA. You know, COM servers, messaging servers, etc, and so on. But, everything up to the database (which was Oracle) was VB6 and earlier.
Anyone want to take a guess as to which language was chosen for .NET, especially with hundreds of developers rather well-versed in VB? If you guessed like me, then you'd be wrong. The .NET standard language chosen was C#.
I was surprised with that decision. But, the reassigning makes sense. There is a world of difference between VB6 and .NET; oo-programming, interfaces, you know, all the features of a "real" modern platform. The idea was, if they put developers in a language they're comfortable with, then they'll try to use the language in the same way. And as we all know ... procedural, VB6-style coding in .NET is just a bad idea.
C# forced all of the legacy VB developers to think in a totally different way and gave the perception that .NET was a whole new platform instead of just an upgrade. Me personally ... I still prefer my VB.NET ;-).