Lol "classic asp.net mvc". It depends on what the client wants obviously but we've found mvc suits best for most projects we work on.
On Sunday, 2 April 2017, Greg Keogh <gfke...@gmail.com> wrote: > Folks, I've been reading the results of search for things like "SPA vs > ASP.NET" and "why use SPA" etc etc. I have come to the conclusion that JS > driven SPAs are not all they're cracked up to be, and the cons outweigh the > pros. I'd even go so far as to say that SPAs are a fad, and even worse, > that they're the misguided use of languages (JS) and hacks (async http) in > inappropriate ways. > > I'm going to write a demo ASP.NET MVC app for the boss, and it will be a > hybrid that a lot of articles hint that is the best way to go. JS scripting > will be involved, but only in libraries that use it internally, and I'll > only use it to create popular UI illusions like menus and dialogs. So after > all my pondering and reading it looks like going back to a classic ASP.NET > MVC based hybrid is best for me. > > *Greg K* >
