Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve refactored my web application into one page (single page app). I’m just wanting some advice on whether serving up the one page index.cshtml with a controller is overkill (I’m not using any razor code that can’t be substituted for normal html/js). Should I just change it to be a index.html page and just serve it as normal?
I’m sure it’s only a minor thing, but want to know what the best practice is here.
No, it’s not an overkill.
Just split your code into 3 parts: logics, HTTP processing, view.
It will be MVC even if all 3 parts are in 1 file.