SSI-like feature in ASP.NET / ASP.NET MVC
After countless hours researching (creating a few demo projects, viewing webinars etc..) I feel like MVC .net works great for 90% of the web application types out there, but not for mine.
Basically I have a dashboard application where I'm displaying large amounts of information in many different graphs / charts (all on the same screen). If I change the state of a control on the page, say a date range, I would like all of the graphs / charts to update accordingly.
Most of the examples of post backs in MVC involve a form submission (we don't have any forms on our dashboard) or it involves navigation from view to view (which I don't want to do either). The closest thing I can relate what we need to would be an MVVM framework but we won't be moving to Silverlight for a few months.
Am I thinking of MVC wrong, am I missing such a simple example that the major bloggers / tutorials don't cover it? Any thoughts?
1:how do i load thousands of rows in my asp.net mvc project from database into slickgrid?ASP.NET MVC: Why is `ToMvcHtmlString` not public?
If your chart/graph controls are classic ASP.net controls then it might be best to stick with a classic ASP.net application. Some of the ASP.net controls don't job too well with MVC..
MVC is supposed to ease your development. If it doesn't, dont use it by force. Stick to WebForms if they fit your requirements better..
The dashboard app as you describe it doesn't sound like ASP.NET MVC would be a BAD choice.. Charts - you must use the Microsoft Charting controls with ASP.NET MVC - here's how
.. Forms & Views - I must imagine you'd wrap those datepickers in form tags. Each grid or chart would have a collection or member variable of any kind on the ViewModel. Create a partial view for each grid, send the appropriate data to it as the ViewModel, and simply
to build a
to display your tabular data as you see fit..
As others have said, MVC is not necessarily better than WebForms, and you should use what is best for your project needs. Don't use MVC just for the reason this it is the latest and greatest.. With this said, for the reason this ASP.NET MVC and Webforms use the same runtime environment, you could create an ASP.NET MVC project and use Webforms within this project when needed. That way, you must receive advantage of both worlds..
into my code base eased quite a few pains this I foresaw. I would highly recommend anyone looking into MVC to check out those two tools (even though Ninject isn't exclusively MVC).. Thanks again.. D^t.