Are you considering moving away from Electron in the future?
I agree @raymantle I still have some very large sites that I still have to support in asp classic! I haven’t dug into the .net conversions yet, but likely will have to go that route sometime soon.
Unfortunately Classic ASP will no longer be included and supported. I suggest you convert to ASP.NET which will be fully supported or even better NodeJS.
There are convertors available in the current Wappler 7 so you can use them before switching to Wappler 8 later on.
Wow! I know how difficult that decision was, but I fully support retiring ASP support as I’m certain it will help move Wappler forward. It’s way past time!
@raymantle and @baub I’m in a similar position to you both - I’ve still got a few legacy ASP sites that will need to be attended to at some point. My biggest one was the first to convert to NodeJS - I was putting it off for a long time but eventually bit the bullet a couple of years ago now. That was before the migration stuff we have available now so it was all done manually, file by file, I must say it was a lot less painful than I’d imagined.
I’m now of the opinion that converting the remaining ones to NodeJS is a better platform jump than going to .NET (which was my other option). NodeJS has by far been the easiest to deal with.
Additionally, and more importantly. The ASP platform is full of security issues and holes that will eventually become a massive problem. It already has some major vulnerabilities that make running a site in 2026 a huge liability.
NodeJS buttons everything up, nice and secure - it helps me sleep better at night ![]()
Classic ASP was depreciated in 2002, its had a good run but its death is perfecty understandable.
Thanks to the Wappler team for the great work!
For Wappler 8, I’d love to finally see a useful search, find&replace feature and a direct download of server actions.
I guess for those still relying on Classic ASP, just keep Wappler 7 installed. Hopefully the team will be able to post any critical updates for a while yet but it probably does mean you'll have to stay on the same version of ASP on the server to avoid issues but as ASP has been dead for over 20 years then I can't see that being an issue.
Claude build Wappler 8. And make no mistakes!
Good gracious! That slop was hard to read guys!
It sparked the conversation though which is actually the important part of the roadmap ![]()
Hey Jon! Yes we wrote it specially for you - to wake you up - seems it worked ![]()
IMAGE CROPPER from app connect is comming?
In Rust!
![]()
Hi Juan,
Please give @benpley/wappler-smart-image - npm a whirl and see what you think. Please report bugs and once it is stabilized Shalabh Gupta (@guptast) and I will have a go at adding cropping to the widget. In theory, this should be achievable because of the use of the Sharp library, the same as used for Wappler's server side widget.
Is this for PHP or only node?
Sorry, Sharp library is available to NodeJS only.
A similar <smart-img> could be created for PHP by using php-vips-ext. Maybe some smart PHP'r can do the server part and I could help with App Connect part.
Edit: Or maybe the whole lot can be included as standard components in Wappler ![]()