Architectural approach for converting web app to Umbraco
Hello,
I'd like to ask how the pros would handle converting a pretty simple CRUD web app to umbraco. It's a flat file of about 3000 records that have about two dozen fields each. It's currently a simple .NET app using DataGrids as the main viewing control, which I'm not crazy about (I'm more comfortable in XSLT than .NET) but it's fine for the client.
Would you:
a. Just leave the data in its own tables and implement the datagrid as a usercontrol on the public website, with access controlled by membergroups
b. Import all records as umbraco nodes, managed through the backend (probably using AutoFolders or the like to ensure that any one node list isn't too huge), and build the presentation with XSLT. I'm a little worried about sluggish performance in the backend with this many nodes.
Architectural approach for converting web app to Umbraco
Hello,
I'd like to ask how the pros would handle converting a pretty simple CRUD web app to umbraco. It's a flat file of about 3000 records that have about two dozen fields each. It's currently a simple .NET app using DataGrids as the main viewing control, which I'm not crazy about (I'm more comfortable in XSLT than .NET) but it's fine for the client.
Would you:
a. Just leave the data in its own tables and implement the datagrid as a usercontrol on the public website, with access controlled by membergroups
b. Import all records as umbraco nodes, managed through the backend (probably using AutoFolders or the like to ensure that any one node list isn't too huge), and build the presentation with XSLT. I'm a little worried about sluggish performance in the backend with this many nodes.
Andrew
Oops, wrong forum, please delete...
is working on a reply...