Home/ Questions/Q 7162471
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T13:44:25+00:00

Back in 2006 I’ve created a web site using asp.net 2.0. At that time,

  • 0

Back in 2006 I’ve created a web site using asp.net 2.0. At that time, I had used Web Forms and classic ADO.NET SQL queries to connect to the underlying database. I’ve also used a fair amount of XSLT.

Today, the site still stands (it has gone through various upgrades but it is still based on Web Forms and simple SQL queries) but I believe it really needs to be upgraded as far as its technological infrastructure is concerned.

What is the next step I should take to move forward? A bit of ajax? JQuery maybe? Rewrite it in asp.net mvc? Replace SQL with typed datasets or even ling to sql? And what is the best way to embrace APIs such as twitter’s?

So, can an old dog learn new tricks?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    So why do you believe the site’s infrastructure needs to be upgraded? If the site is running and performing well after 6 years of load and data, then what factors are causing you to think you need to upgrade it?

    • Are there features that you want to implement (or users are asking for) that you can’t implement with the current infrastructure?

    • Is maintenance difficult and brittle, and every time you upgrade, you spend weeks fixing bugs introduced?

    • Are there integrations that you’d like users to be able to do so that they can extend your application’s functionality and/or data to their own applications?

    Those reasons above could be reasons to upgrade, but I can’t really tell you.

    But as far as some of your questions about what to upgrade:

    • a bit of AJAX? It depends on what your current infrastructure looks like, but it’s not too hard to introduce and you can isolate it
      pretty well with a service layer.
    • jQuery? Again, it depends on
      how your pages are structured. If you have a lot of master page
      re-written IDs and very few classes on your DOM elements, using
      jQuery right off the bat may be tough as you’ll have to figure out
      how to get your selectors in line.
    • Replace SQL with Typed
      DataSets?       Please don’t do that. Honestly, if you go with
      Linq-to-SQL or EF, you’ll probably take a slight performance hit
      compared to using ADO.NET with DataReaders (if that’s what you’re
      using).
    • Can an old dog learn new tricks? Always. The learning
      never stops.

    I would just advise not to upgrade just to upgrade. Make sure you have legitimate business reasons for doing so.

    Hope this helps. Good luck!

    • 0