Gustav Brock
Gustav at cactus.dk
Mon Feb 6 08:11:46 CST 2012
Hi Shamil Good question. >From time to time I think about a "back-office" engine producing predefined reports from materialized data. Then the web client could just produce the parameters and the name of the report, send these to the queue at the engine, and the report could be picked from a link, saved as a PDF, or somehow else. Problem is that this may not be what users expect if they are used to a desktop app where reports normally pop up in a new window. However, reports with aggregated data - as most reports have - could be produced faster or at least without waiting time for the user. And the client could be anything, even a phone app. /gustav >>> Salakhetdinov Shamil <mcp2004 at mail.ru> 06-02-2012 14:22:41 >>> Hi Gustav -- Yes, "not completely dead" - for CMS like DotNetNuke classical ASP.NET and ASP.NET MVC would be in use for quite some time but for business applications I'd "bet" on pure HTML forms, JavaScript, AJAX, (RESTFul(?)) web services... Although I have no clear idea what reporting solution to use for such a "pure HTML forms" based business applications: should that "pure HTML Forms" app be still driven by classical ASP.NET engine to be able to use MS ReportViewer Control for reporting? Thank you. -- Shamil 06 февраля 2012, 15:10 от "Gustav Brock" <Gustav at cactus.dk>: > Hi Shamil > > Not completely dead, as he admits in the last paragraph, but the Knockout site is certainly interesting with a lot of stuff to investigate. > Thanks! > > /gustav > > >>> Salakhetdinov Shamil <mcp2004 at mail.ru> 05-02-2012 21:34 >>> > Hi All -- > > FYI: "ASP.Net WebForms and MVC are Dead to Me" > By Joe Brinkman on 2/1/2012 12:19 PM > > http://www.theaccidentalgeek.com/post/2012/02/01/ASPNet-WebForms-and-MVC-are-Dead-to-Me.aspx > > Thank you. > > -- Shamil