Home >> Experience >> Legacy

Legacy Applications

Our experience dates back to Classic ASP. If you are still using Microsoft's older legacy application framework then you've come to the right place for a facelift.

It is now almost 20 years that the Web has been around. Wow! Many folks still have their Web operations built with Microsoft's old development technology - Classic ASP. Hey - if it ain't broke don't fix it. Right?

There is nothing wrong with a Classic ASP application if it is working properly and performing all of its duties in harmony. The larger problem is finding someone with experience working with Classic ASP. Many developers on the market today weren't even in high school when you were having your Website built. We were already in the biz.

Taking over a Classic ASP Website is not a major big deal but there are some important items and misconceptions we would like to point out regarding Classic ASP applications:

1. Logins on a Website are monitored by what we call session variables. Session variables cannot be cross referenced. In other words, a login session set in Classic ASP cannot be read in .NET. However; there are secure ways to make this work without requiring two different logins.

2. We are often asked, "Can you convert my Website to Classic ASP?"

Technically, there is no way of converting a Website from Classic ASP to .NET. Classic ASP is a scripting language and .NET is an object oriented programming language. They are two different beasts.

What is the difference? Imagine if you were proof reading a book. Would you rather do it line by line or would you rather use spell checker? The answer is obvious.

A scripting language is interpreted line by line like a person manually proof reading a book - line by line. Any errors in logic must be painstakingly hunted for and may be missed only to re-appear at a later time.

An object oriented programming language is compiled - like spell checker in Microsoft Word. Push a button and 99% of the errors will be found before runtime.

3. We do encourage clients adding new features to Classic ASP applications to do so in .NET. It just makes too much sense and there are too many benefits.

4. Classic ASP was shelved by Microsoft around 2001. By all indications they will continue to support it on new releases of Windows Server for a few more years. We have seen estimates dating out to 2016.

5. Classic ASP applications (sometimes) have security flaws in their database integration especially if they are very old. Inline SQL statements were popular back then. Inline SQL statements are embedded directly in the Classic ASP pages are they are dangerous! Stored procedures are far more secure - especially in this day and age - but it took a while for stored procedures to become popular. If we find this then we will go over it with you.

6. If your Web server is very old and you wish to move to a newer Windows server then you may have a few minor hurdles to cross to get Classic ASP to run on it. Still on a legacy system? We have the experience and know-how to move you forward.

Home     About Us     Experience     Technologies     Sum of the Parts     Beyond the Code     Clients     Contact Us     Sitemap

© 1997 - 2020 TConsult Web Dev Inc.