I have a site that is built in classic ASP and I want to start converting it to ASP.NET. Can I mix and match. I would start a new project and have folders dedicated to the ASP.NET pages locally, but would push to a development server that has the ASP code. I know there is some overlap in Wappler directories so not sure if this would work. Hope this makes sense, let me know if you need more clarification to answer.
Thanks, Ken
I’m gonna bump this versus starting a new thread.
I’ve got a classic asp site that is HUGE. I have both older dmxzone extensions and html data bindings in usage. I need to start migrating to wappler and also move to asp.net. Server is configured to run asp.net so that isn’t issue. Rebuilding the site from scratch isn’t really an option.
Can i just create new pages with asp.net and create and it will coexist with the older pages? I"m worried about the wappler default folders overwriting any folders that are already existing in the site?
Inside Wappler, probably not. Using Visual Studio, yes. We used to do it all the time.
You might be able to create your project in ASP.NET server model, then add some pages with the asp extension and test it out.
I feel your pain - I’m in the exact same situation too. In addition, we are using MySQL instead of MSSQL so there’s an added complication. Personally, I’m slowly getting drawn to the fact I’m going to have to re-write the entire site as I can only see constant hassle trying to iron out any bugs we get along the way.
I’m planning to edit on a live server in a duplicate domain then eventually port the whole lot over in one swoop. A bit of a scorched earth policy but the only way to end up with a stable and scalable site moving on. Our ASP Classic ASP / DMXzone extensionscombo is very old skool and not scalable, better ditching the lot and starting from scratch.
Will see if we can finally start working on those server model converters
But still they will give you just a head start and you will still have to check everything and perform some manual conversion as well.
My thoughts were if the existing extensions can co-exist with the wappler stuff I could just use wappler on new pages or as I convert them?
But some sort of a converter would be cool too.
Thanks for all your hard work that you and the team do!
Converting the server model is about all the server actions, their urls en also the pages that call them.
So everything needs to be renamed.
App Connect components on the pages will remain the same.
If you have much older DMXzone extension pre app connect, you will have to convert them manually to app connect versions first.
yeah I could copy the entire site to a new testing domain. Do the conversions and stuff there and get it working, then move it back. I do have a lot of old dmx stuff in there. I can’t remember what they were called its been so long. HTML data bindings? I guess pre app connect. there is some app connect on there too. And the site is bootstrap 3, so there will be a lot of conversion to happen.
@george would you have any kind of time frame on “server model converters” ? I’m just trying to come up with a game plan for this website that I need to convert. Don’t know if that would be sometime soon or 6 months? Just looking for a timeline so I can figure out the ongoing plan. I’m getting used to how awesome wappler is that going that far back to modify existing HTML data components is killing me. My brain doesn’t go that far back. LOL.
Well it’s not a top priority but I think we should get it done in the next few months
Understood on priority. Just looking at game plan here and scheduling.
Hello George, thanks for your support. Any news about the migration tool from asp to asp.net? thanks