Dave, that pretty much mirrors my own experiences :-)

I think that I've always been a big fan of server controls - and in particular the databinding behaviour - since reading the early Dino Esposito books.

The big thing for my development over the past 12 months has been the emergence of a clear "style" of architecture. As such, there's a much cleaner separation of logic throughout the layers of my applications.

Thanks for the post; it's always good to read about shared experiences :-)

I should add... one area where our paths have diverged is that 12 months ago I was writing in C# and VB, whereas today I've dropped C# altogether. What was the catalyst for your move away from VB? Was it employer induced or self-regulated?

Its funny, really. I started writing web apps in 1995 using PHP2, then PHP3. PHP is very C-like. Even in the 80's I had an interest in the more economic syntax of C, but could not get over the malloc/printf/--> hump.

I started in VB.NET because VB syntax was familiar and I needed as much help as possible getting a handle with .NET. After a year I made the switch. I have no prejudice against VB.NET. I LOVE the VS.NET editor support for VB.NET compared to C#.NET support (which is still okay, but not as good as VB.NET to me.) I am also impressed by how many cool developer studs continue to work in VB.NET.

I do like the lesser code factor in C#, if only for aesthetic reasons. Its...uh, prettier. I really don't have any stronger feelings about the differences than that.

I work for a smaller company, so I have the privilege of making those decisions. I'd be interested in why you stayed with VB.NET. (You don't have to be as wordy as my comment here!)

Good talkin' to you.

My reason for choosing VB was probably due mostly to the fact that my employer decreed it :-)

Once that choice was made for me I decided that I'd devote myself 100% to that language rather than splitting my learning across 2,3 or more languages.

To borrow a concept from Ben Elton... I think that, for many developers, VB is the language that they love to hate, then they learn to live with it, finally they hate themselves for loving it. :-)

For me, it just feels good to have the knowledge that you are able to use your language of choice to do anything that you want -- unrestricted. I'm just now starting to feel that sensation myself with VB!

"...devote myself 100% to that language." Absolutely, Zen and the art of VB.NET. "...hate themselves for loving it." Good one! "[getting to the place as a developer]...to do anything that you want -- unrestricted." Man, I want to remember that, as there are always the ongoing choices to be made: to do what I have no experience doing, requiring google, msdn, junkies, code project, etc, etc., or to take the familiar approach, get the job done, and not grow. Thus the d.o.t.d. mentality and why this blog stuff is such a motivator. "What did I LEARN today that I can record on my blog?" or "What did I take time away from banging out code for my employer to learn today for ME?" When there's no d.o.t.d., chances are good there's been just typing going on. Then you die.

> to do what I have no experience doing,
> requiring google, msdn, junkies, code
> project, etc, etc.,

I think that you omitted the most significant (IMHO) resource - the Starter Kits. If I had a single message for developers it would be, forget the shotgun approach of Google and Co. *until* you've uncovered the jewels from the StarterKits.

When I say "Google, MSDN, etc" I wouldn't use a shotgun approach as a description. It's always a very narrow, focused search, which I've found to be unique to .NET. In the past I could read chapters on a subject, say, MSMQ, or, in the case of COM+, several books before getting dirty and have to use the information. In .NET everything has speeded up and I need information on this very particular issue today. Then I code for a while and need a particular bit of info on a particular issue again. This is why Google's Advanced Groups Search Page is my home page.

Would you please be so good to tell me what you referring to in "the Starter Kits." Do you mean the Walkthroughs and Getting Started guides in VS.NET? Thanks.

The StarterKits that I'm referring to are the ASP.NET Starter Kits here:

http://www.asp.net/Default.aspx?tabindex=9&tabid=47

I can guarantee (actual guarantee may not be valid) that any of the fundamental, standard features that a developer would need to develop in a *normal* modern web application can be learned by studying the architecture and tips-n-tricks in those applications.

Features of those apps that make them a good learning tool are:

- they have been developed and scrutinized by experts
- they come in C#, VB and JScript
- they come in either VS (code-behind) or inline version
- they come with 30 page architecture documents
- they have forums to discuss issues

Somehow people are missing the Starter Kits and I'm not really sure why. Too often I see a developer travel down the path of developing a complex solution for something that is abundantly covered in the Starter Kits.

I can say - in all honesty - that I rarely, if ever have to google a solution for 95% of my dynamic, data-driven web application needs because I can fall back on the knowledge that I've gained by having a deep understanding of how the StarterKit applications were built. That's the truth!

What I can agree with though, is that for an MSMQ, COM+ etc., solution, I most certainly would need to ask Mr. Google. But, the StarterKits cover all of my ADO, Server Controls, and report building needs.

Well I certainly cut my .NET teeth (like thousands of other guys) on IBuySpy over a year ago. I've seen these particular packages, but never pursued them as an object of study. Definitely good advice though! Thanks, Darren.