Menu
ASP.Net MVC is a server side framework. (An alternative is ASP.Net WebForms: your events are posts to the same page, abstracted to seem like desktop application events.) If you want, you can output data as JSON or XML and use this with a client side JavaScript framework to update your views.
ASP.NET Core MVC is a server-side MVC framework. In a server-side application the client's request to view a page depends on the server delivering the correct content for that specific page (HTML, CSS, files, etc.) to the client. The client then renders this content for the user.
Client-side means that the action takes place on the user's (the client's) computer. Server-side means that the action takes place on a web server. Client-side means that the action takes place on the user's (the client's) computer. Server-side means that the action takes place on a web server.
Before you answer, this question is complicated:
What we are trying to do is NOT CREATE A MESS in our UI by writing a bunch of JavaScript to deal with the same feature in different contexts. I understand that I can use a JavaScript file + object oriented JavaScript, I'm looking for the pattern that makes it all easier.
One solution proposed was to have an MVC model on both the client and server side, where we can encapsulate JavaScript functionality in client side controllers, then use them in different parts of the site. However, this means that we have 2 MVC implementations!
Is this overkill? How would you expand on this solution? What other solutions are there?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With