Transferring from Classic ASP to PHP? .NET?

Hi all…!

First off, thanks for being a great bunch, I’ve been developing web serivces for a long time but still manage to learn something new here every day.

Well, I’ve a lot of work to do - one of our main websites is huge, been running on a Windows server (2012) with IIS8 and classic ASP driven from a MySQL backend (not a fan of MSSQL), there are also a few PHP elements running alongside it (for RSS feeds / Forums etc). It’s been running perfectly through different iterations since 1997.

As we all know, Classic ASP is now getting a bit long in the tooth and is slowly dying out - hence my interest in Wappler (as it also allows deployment to mobile also etc). I’m looking to move the whole platform over to either PHP/MySQL, or .NET/MSSQL (although I’d much prefer .NET / MySQL if that’s at all possible).

Now, I’m perfectly happy coding with VBScript but the .NET environment is a bit off putting for me, PHP I’m more happy with, there’d still be a big learning curve but not as much as I feel there would be with .NET.

I do realise though that the .NET choice would be a better option for the Windows server we are on.

I’m therefore in a bit of a conundrum - Has anyone out there been in a similar situation?

I"m in the same ballpark. Have done classic asp forever. Cause I’m old. LOL. Looking at how to migrate a lot of sites that I have already built.

1 Like

Thanks for pitching in @baub
Are you on a recent iteration of Windows server? Or an older one?

Both. I will probably just start switching over to asp.net. Some of my sites are kind of using both really. You can config a newer windows server to do both. Some of the functionality of the action scripts like image resizing and stuff like that actually use the asp.net functionality.

I think our sever (2012R2) can do both. I’m a complete noob with .NET. How did you find the learning curve?

@TMR
It doesn’t matter if you are using ASP, PHP or ASP.NET - in Wappler everything is the same. You don’t need any ASP.NET coding knowledge, as the code is being generated by Wappler …

1 Like

There really isn’t one if its a new site. I guess it just depends on whether you have admin access to the server for config, or if its a shared hosting platform might be a bit different. But not really any problems. I guess I’m just too last to type the extra x on the end of .asp. LOL

1 Like

@Teodor this is one of the major advantages with Wappler, the flexibility is immense.

@baub we own the server so have full access, that’s always been a major advantage for us. I know what you mean about the additional ‘x’ :sunglasses:

@teodor my issue is if I have connection scripts that are using classic asp, how do I just convert everything over to .aspx?

I will have to rewrite all the scripts? Or just the database connection script?

Hello, did you come to a solution? I’ve seen your post now and I found I’ve the same problem. Web portal with 5000 pages in Asp classic and willing to change to new technology.
If there was a way to change all the pages in extension aspx and then change them little by little …
Anyone has a suggestion (ok… I know do it from scratch would be the best but also 50.000 euros worth minimum is a lot).
thanks

1 Like

As far as I can see you can run classic ASP and ASPX pages on the same site and the same server. We are looking at running our main site as-is then slowly rewriting all the asp pages to aspx pages - hopefully we wont have too much downtime doing it that way…

Hello.
After 28 years developing and maintaining systems in Classic ASP and VB6, I’m in the very same dilema.
The extra ‘X’ after ASP will cost me the last hair on my head.
I’m migrating all my sites to Java Script.
This year I started migrate sites, using Classic ASP in the server side to work with MS SQL and JS in front end. Using beautifull XML HTTP Request technology.
What dou you guys think about that merge?

Regards,
Edson.

1 Like

What framework are you using fo your JS…? I don’t want you to lose any more hair (I’m in the same situation) but have you tried NodeJS with Wappler? It’s more integrated and less of a learning curve. We have a lot of ASP inventory in various types of sites - large and small - so we are picking out what we think is the best transition for each.

Larger sites (our main one is massive) we went to .NET as it meant a lot less downtime. Smaller sites we have running with PHP (although there are less of those) and some are redeployed with NodeJS. We are happy with them all because using Wappler as a tool to create them means there’s little difference.

Hi, I've found your topic.
I've a web app developed in asp and time is ticking. Unfortunately the db is ms access.
could you give me suggestions for the best migration process and technology?
My will is to open the app to other consultants in 5 languages.
Would love to find a way of simulating the migration in a new tech and little by little convert the web site into the new tech.
I was expecting a AI tool to ease the migration but so far nothing.

any suggestion welcome
3.000 asp pages

tanks to whom will spend some time with this.
Alex- Mario

I'll pitch in with the experience we've had so far.

We originally had sites in NodeJS, Classic ASP, PHP and .NET - after trying NodeJS on some of the more complex sites we decided to port everything over to NodeJS - its just so much easier once you get your head around the way the file-system works.

Some of our original DB tables were first compiled in 1997 - We never relied on MS Access as it doesn't cope very well with lots of simultaneous users, we use either MySQL or MariaDB (which is very similar to MySQL). We tried MSSQL but it just wasn't as good as the ones we are using.

You should be able to export your MSAcess db using any other ODBC connection, there's plenty info online for this, here's the first hit from a random search:
https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-examples-tools-with-access-export.html

We also have thousands of pages, all easily handled by NodeJS templating system which was very effective.

Whatever server model you choose, it'll be very unlikely you'll be able to do little bits at a time - you'd be better biting the bullet and creating a new site in its entirety then deploying it when ready.

We've run Classic ASP side by side with .NET on the same website, and whilst it all worked more or less fine, It was a nightmare to update and would have been quicker overall to do a full site rebuild in .NET - instead of that though we went full NodeJS and havent looked back, it's more powerful, faster, easier to maintain and has more features than the others.

Thankyou so much
I am the programmare but also the ceo nowaday. I am evaluating to here somebody for the months needed to rewrite all the web app.

Really uncertain about the best solution

1 Like

Let me know if you have any specific questions and I'll do my best to help.

My first is to understand what language and rdms use to minimize the effort of re-engeneering then I'll have to find a freelance to hire (another energy consuming task).
thanks for your time and answers.
Alex

1 Like