Can generated ASP.net applications be maintained without ASPRunner.NET?

Making some really minor changes - yes. Maintaining - definitely not, it defeats the whole purpose of code generator tools.

Let me give you a simple analogy. ASPRunner.NET can be considered a burger-making machine. You feed it ground beef from one side, it adds more ingrediaents, spices, presses the burger and grills it. You receive a juicy, grilled to perfection delicious burger from the other side. You can add some salt or pepper to it but this is pretty much it. If you decide to change your process and make a turkey burger instead of a beef one you have to start by feeding the machine ground turkey.

This is just how things work.

Necessity is the mother of invention if they are bright enough to be developers they should be bright enough to use Xlinesoft software surely...??

Thanks for the helpful reply from admin and the snarky ;) reply from Dalkeith. It's not a matter of not being able to use ASPR. It's a matter of their workflow. I suspect they will eventually migrate all of my ASPR apps to conventional dev platforms afte I leave. I just wanted to know the best approach and now I know. They need to learn to use this tool as long as my apps are in production. Thanks.

—Pete

I have the same type of question. What if a situation arises, like what happened to Iron Speed Designer. I know "what if's" are generally futile to ask but it is a legit question that people may have at the beginning of their journey with ASPNETRUNNER. Iron Speed's situation appeared to come from litigation and not because the company just decided to close shop.

It would be reassuring to know that the build code could be edited without the use of the tool if the something ever happened and we could survive for a long while until another solution path was found. I know that tool itself could just be used until it was no longer compatible with the OS it runs on, or the frameworks that it uses are not supported anymore, which would probably be a very long time anyway. Also, scenarios do arise where we develop an app and want to sell that app to another party. Right now, they'd be required to purchase the tool (which I love, by the way and would encourage them to do so). But some of these prospective clients will want to source and manage that code using traditional methods because they have the same apprehension being brought up here.

Everything about this tool is absolutely amazing though. But creating the ability for the built code to be edited and maintained without the tool (and the source code for the special dlls if the tool were ever ceased) would bring a higher level of security to the developers using the tool, for sure. Also, with that being said, I still want the tool to be around for the next several decades, at least!! We need to do all we can to support and promote this product.