Soldato
Hey all,
I have an internal site at work that is backed by an MS SQL backend, the SQL server contains tables that are filled up by some scripts that run periodically, there is no user input it is view only data (nor would I want users to be able to input data into the tables).
The site is currently using C# ASP.NET with webforms, some javascript and CSS styles for the frontend. I am 90% of the time calling data using Stored Procedures which accept input parameters, and allows for paging the results - I can return thousands of rows
On my pages I am generally calling data using TableAdapters to link my Stored Procedures, with ObjectDatasources binding to the TableAdapters, and then binding the ObjectDatasources to Gridviews so that the user can see the results. The ObjectDataSource allows for paging results automatically which is nice, along with the Gridview paging bars.
Question is can I do similar with MVC here, and easier? I have been playing with some of the MVC tutorials but I am struggling to see how to do what I want in MVC vs how I am doing it now in webforms, a lot of what the tutorials have done so far has been for things like code first databases, or focusing on how users can input data, validate it etc.
The demo stuff I am working with is too small compared to my live data, and my queries are often spanning more than one table so I am a little lost/confused on how MVC is meant to work with this and Entity Framework.
I have an internal site at work that is backed by an MS SQL backend, the SQL server contains tables that are filled up by some scripts that run periodically, there is no user input it is view only data (nor would I want users to be able to input data into the tables).
The site is currently using C# ASP.NET with webforms, some javascript and CSS styles for the frontend. I am 90% of the time calling data using Stored Procedures which accept input parameters, and allows for paging the results - I can return thousands of rows
On my pages I am generally calling data using TableAdapters to link my Stored Procedures, with ObjectDatasources binding to the TableAdapters, and then binding the ObjectDatasources to Gridviews so that the user can see the results. The ObjectDataSource allows for paging results automatically which is nice, along with the Gridview paging bars.
Question is can I do similar with MVC here, and easier? I have been playing with some of the MVC tutorials but I am struggling to see how to do what I want in MVC vs how I am doing it now in webforms, a lot of what the tutorials have done so far has been for things like code first databases, or focusing on how users can input data, validate it etc.
The demo stuff I am working with is too small compared to my live data, and my queries are often spanning more than one table so I am a little lost/confused on how MVC is meant to work with this and Entity Framework.