How can we create best architecture in .net MVC with AngularJS ?

Question

1.00/5 (1 vote)

See more:

MVC

C#3.5

AngularJs

How can we create Base of any project with MVC and AngularJS.

Posted 16-Dec-15 0:23am

S.K.Tanwar

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nathan Minier · Answer 1 · 2015-12-16T02:17:00

The best architecture for it is not to use MVC. Use WebAPI instead, and let Angular handle your views. That's the point of it.

Trying to mix the two makes specific delegation of responsibility difficult. MVC takes data from the back-end and renders a view with it via Razor. Angular takes data from wherever and renders a view on the client via HTML. Both do the same thing, just one on the client and the other on the server.

Ultimately it has more to do with which space you're comfortable working in.

If your department has the JavaScript chops for it, using Angular to completely handle your UX is a better solution. It is faster, completely modular, and can use external resources with less effort.

If your comfort levels or policies dictate using more c# than JS, stick with MVC and do not use Angular, since it's almost completely redundant in that scenario.

Just to note: I have a specific project that I've implemented in MVC, MVC/Angular, WebAPI/Angular, and ultimately a custom OWIN implementation/Angular. Of each of these implementations, MVC/Angular had the worst performance, was the most complicated, and took the longest time to code.