Making the jump from Classic ASP to ASP.Net – Which language to choose?

I’ve been developing using some flavour of VB/VBA/VBScript for about ten years, and I’m very used to the way it works, but I’m realising it’s time to move on.  Technologies have changed, and even though my Classic ASP applications perform perfectly well, they don’t fit in with the direction my organisation wants to move in.  I’ve been putting things off way too long, and it’s time I moved on, too, before I find myself way too behind the times.

So, with that in mind, I’ve explored a little and found I have two options (from a Microsoft and ASP.Net point of view) – to go with VB.NET or shift over to C#.  In this article I want to discuss my decision and why I came to it.

Coming from a generally VB-based background, the obvious draw for me is to move across to VB.Net.  I know it’s nothing like what I’m used to, but it’s pretty close and probably not that much of a learning curve (apart from being better at OOP stuff), but is it the right decision to make?

Turns out it possibly isn’t.

Do a search on for questions asked about C# and VB.Net and here’s what you get:-


for C#, as opposed to a similar search for VB.Net:-


Wow.  I mean, wow…  That’s ten times the amount of questions about C# than about VB.Net.  Now, what does that mean?  Does it mean C# is ten times more difficult than good ol’ VB?  I don’t think so.  Look at the amount of followers for each.  Here’s the number of followers on StackOverflow for C#:-


And here’s the same statistic for VB.Net:-


Again, ten times the number of C# followers.  To me that says how many people are interested in the technology and want to read about it.

I decided to do more research, so I jumped to GitHub and looked at their language specific pages.  I started with C#.  It’s worth noting here that on the languages pages it doesn’t mention the number of repositories, but it does tell you where the chosen language sits in terms of popularity.  I digress, here is the result for C#:-


And here’s the result for VB (unfortunately, Github doesn’t seem to split VB into sub-languages, but in this case it doesn’t matter):-

vbgitHmmm…speaks for itself again, doesn’t it?  Let’s try something else though, as I’m still not convinced.  What jobs are out there?  I opted to look at and search for both ‘C#’ and ‘’.  Here’s what I got for C#:-


And for VB.Net?


Finally, following a search on programmer salaries, I came across a very simple looking search on where you can search by keyword and you get an average salary (in dollars) for jobs matching that keyword.  I couldn’t resist.  Here’s the result for c#:-


and the salary for VB.Net:-


Not a massive difference, but the results still speak for themselves, I think.

Still not completely convinced about the overwhelming evidence provided to me by my ‘scientific’ research, I spoke to a seasoned developer colleague of mine yesterday and asked him which I should go for, and his reaction was along the lines of “you know how Classic ASP is now?  That’s what VB.Net will be in about 5 years..”.

Now I know that might be a somewhat subjective statement (the  guy develops using C#), but I got the point…

Based on these findings, I’ve decided to try to learn C#.  From both a personal and professional standpoint, I think it’s the right thing to do. I know it’s going to be a challenge,  especially moving from a scripting/procedural language like VBScript to a more Object Oriented language such as C#.

I’ve started today, and hope to post more on my experiences as I go on.

I’d be interested to see what you guys think about my decision, and my rather non-scientific methodologies in reaching that decision.  I’m also aware there are other web technologies out there, but my hand is somewhat forced by the organisation I’m working in.  I still intend to learn some PHP at some point, but not yet.

Leave a Reply

Your email address will not be published. Required fields are marked *