Visual Data's JumpStart DNN ApplicationBuilder generates your application by interpreting the databasemodel that you feed it with.
The benifits of this way of working are substantial, especially when time and money are key reasons in developing DotNetNuke applications..
Also here is a huge improvement in reducing development time. along with testing and maintenance.
Why?
Because all the code that Visual Data's JumpStart DNN ApplicationBuilder produce is consistend and uniform. Always.
The code is self documented and there is also an extended tracelog build in so any software developer can easily maintain the code without first having to study what parts of code might do, or how certain algoritms work.
This makes maintenance especially friendly because your developers always know where to look for the functions in the code.
This makes it also easy for teams of developers and testers, because the consistancy and uniformity of the code makes that they don't need to spend time to read thru the code that other people might have designed and written a long time ago, and nobody can find any documentation anymore.
Another timesaver is the function "ExcelReader".
The ExcelReader is a nifty piece of work that lets the developer and tester use an Excelsheet with tablecontent to fill the tables every time they are renewed.
This makes it very friendly and timeconsuming because there is always a testbase at hand that can be loaded quick and easy, and guarantees a save and solid testbase throughout the development and testing stages.
After implementation of your application the ExcelReader can be used for the formal first filling of the productiontables with the productiondata.
Is the produced code ridgid then?
No, it isn't ridgit at all!
In fact, the Visual Data JumpStart DNN modules are designed to be "Casco" modules. This means that any DotNet developer is able to maintain or extend the application in any way that DotNet supports.