Classic ASP
-
Matthew Faithfull wrote:
I'd code all the year round even if I didn't get paid for it
I've got some clients that would like your pay rate :-D
only two letters away from being an asset
Put me in touch. I work on a no spec no fee basis. You don't spec any requirements and just gaurentee to install anything I write and you get an endless stream of free software with random amounts of maintainence, no documentation and no gaurentee of any specific functionality :laugh: It's a bit like a governemnt IT project only 100% less expensive.
Nothing is exactly what it seems but everything with seems can be unpicked.
-
Douglas Troy wrote:
We have clients that are still running *nix systems in their offices with a COBOL based medical billing software package.
Bah! Pretty-boys and their high-level languages. At the company I work for, some of our most core systems are still in S/390 assembler. Yeah that's right. And they run on a mainframe that up until a year or so ago used 31-bit cpus! VSAM, QSAM, DASD, LPAR, ... I had a full head of hair when I started this job 5.5 years ago. At least we don't have any AS/400's running RPG code.
-- Russell Morris Morbo: "WINDMILLS DO NOT WORK THAT WAY!"
Russell Morris wrote:
At least we don't have any AS/400's running RPG code.
I didn't know you could play an RPG on an AS/400!! Must be all text based ... ;P
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
All of our web based applications in production are written in classic ASP with VB6 and COM+. The obvious question: why? The answer: the were written before .NET was ready for prime time and they work. If it ain't broken.... It is easier/faster to maintain existing applications than it is to rewrite them. Of our base of 5 staff people that would look at this code, only 3 have had the opportunity to work with .NET; when all are comfortable with .NET and can support applications written in it during off-hours, then the application will be rewritten - if there is a business need to do so. Tim
Tim Carmichael wrote:
If it ain't broken....
Completely understandable
Tim Carmichael wrote:
It is easier/faster to maintain existing applications than it is to rewrite them.
Not necessarily. Some apps become difficult to maintain when the technology is no longer supported or skilled people to work on them are not available. They also become difficult to maintain when other application that use them or are relied upon for them have changed and upgraded.
only two letters away from being an asset
-
Russell Morris wrote:
At least we don't have any AS/400's running RPG code.
I didn't know you could play an RPG on an AS/400!! Must be all text based ... ;P
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTLDouglas Troy wrote:
I didn't know you could play an RPG on an AS/400!! Must be all text based ...
:laugh: Worse - it's record based ;P
-- Russell Morris Morbo: "WINDMILLS DO NOT WORK THAT WAY!"
-
I had a requirement come across my desk from a recruiter in the office. The client has 50-60 applications that they need people to maintain and fix VB6, COM+, Classic ASP. These are line of business, enterprise applications that are critical to their operation. This is not a job posting. I'm just wondering if anyone else out there is still using such antiquated technology. The sad thing is that when asked, they said they were planning, some time, to upgrade to more modern technology, .NET Framework 1.1 !!!
only two letters away from being an asset
I'll do it for double rate! Just leaving a contract where I used ASP Classic up until a few weeks ago mixed in with the newer .Net project work. Many companies simply can't afford the investment and pain of upgrading apps that may work perfectly well for the task. If it ain't broke, don't fix it!
-
Douglas Troy wrote:
I didn't know you could play an RPG on an AS/400!! Must be all text based ...
:laugh: Worse - it's record based ;P
-- Russell Morris Morbo: "WINDMILLS DO NOT WORK THAT WAY!"
What's the LRECL ??? I just gotta knowwwwww ...:laugh:
-
Mark Nischalke wrote:
This is not a job posting. I'm just wondering if anyone else out there is still using such antiquated technology.
I believe there are 3 people in India, 2 in the States, 4 in all of Europe and Chris Maunder in Canada who use Classic ASP. Everyone else is using ASP.NET now :-)
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com linkNishant Sivakumar wrote:
I believe there are 3 people in India, 2 in the States, 4 in all of Europe and Chris Maunder in Canada who use Classic ASP.
Who is the other one in the States, I would like to get to know him/her. :)
-
I had a requirement come across my desk from a recruiter in the office. The client has 50-60 applications that they need people to maintain and fix VB6, COM+, Classic ASP. These are line of business, enterprise applications that are critical to their operation. This is not a job posting. I'm just wondering if anyone else out there is still using such antiquated technology. The sad thing is that when asked, they said they were planning, some time, to upgrade to more modern technology, .NET Framework 1.1 !!!
only two letters away from being an asset
I've never had a dev job where I wasn't programming in C#. I can't fathom accepting a gig which required me to touch VBScript, VB6, COM+, etc. That's just not my style. My girlfriend just left a company which used classic ASP, and now works for a firm which only uses ASP.NET 2.0. She said that moving to .NET (and away from ASP) has been wonderful.
:josh: My WPF Blog[^] FYI - Bob is a scarecrow who keeps Chuck Norris away from CodeProject.