How to use AngularJS framework with Asp.net MVC "Areas"?
I am developing an application with having large user base and large database tables (i.e. around 5 Millions of row for 8/10 tables). So, I had plan to use AngularJS for handling data manipulation and UI (within .cshtml page). I had a knowledge on how to develop Asp.net MVC web application with AngularJS app, but my application has multiple Asp.net MVC "Areas". I am using asp.net MVC5. I have a following questions.
Is it good to have a AngularJS framework for my application requirement?
What is the efficient way to use AngularJS framework with Asp.net MVC "Areas"?
Thanks!
If you are dealing with large datasets, as per suggestions found below ReactJS would be a good fit.
If you have to choose AngularJS because of its full stack of functionality available in the framework, you may very well go with isolated mini SPAs in your areas
Links:
http://blog.backand.com/angularjs-vs-react/
https://www.codementor.io/reactjs/tutorial/reactjs-vs-angular-js-performance-comparison-knockout
Related
I have gone all over internet however still confuse in choosing MVC or WEBform pattern of ASP.NET Framework.
i have an application which is Developed on Webform model, does it really require to move it to MVC?
Webform is quiet stable, why should we go for MVC?
I mean what parameters we need to consider before moving webform model project to MVC?
any help or redirection will be highly appreciated.
Thanks!
As mentioned in the comments, there is nothing special that forces you to move into MVC.
If you’re going to start a new project consider using MVC. Here are few points which you could get benefited while using ASP.NET MVC :
Asp.Net MVC is a lightweight and follow MVC (Model, View, Controller) pattern based development model.
Asp.Net MVC has html helpers.
Asp.Net MVC does not support view state. Asp.Net MVC has route-based URLs means URLs are divided into controllers and
actions and moreover it is based on controller not on physical
file.
Asp.Net MVC follow customizable syntax (Razor as default)
In Asp.Net MVC, Views and logic are kept separately.
Asp.Net MVC has Layouts for consistent look and feels.
Asp.Net MVC has Partial Views for code re-usability.
Asp.Net MVC is lightweight, provide full control over markup and support many features that allow fast & agile development. Hence it
is best for developing interactive web application with latest web
standards.
Asp.Net Web MVC is Open Source.
ASP.NET Web Forms is a part of the ASP.NET web application framework. It is one of the three different programming models you can use to create ASP.NET web applications, the others being ASP.NET MVC and ASP.NET Web Pages.
I have read above lines in asp.net site. My understanding is A web page may refer to a html document retrieved from server and A Web Form is a thing in ASP.NET Application used to generate a HTML document(in dynamic manner)
But definition of web forms said by asp.net site confused me. OK I can understand MVC is a programming model used to create ASP.NET Web application.
What is a Web Form ? and What is a Web page ?
How Web page is a programming model to create ASP.Net web application
ASP.Net is Microsoft's technology stack for building dynamic web sites.
Within that stack, they support 3 different ways of generating a web page.
Web Forms is the oldest - it's been around since ASP.Net was born. It's tightly coupled into Visual Studio, and has "drag and drop" page building. Most people who care about how their HTML is constructed dislike Web Forms, because the "drag and drop" components can make it hard to generate semantic, valid HTML - though the latest version is a lot better.
ASP.Net MVC is an alternative to Web Forms - and it's a pretty decent MVC framework.
Web Pages is another alternative; it's more of a scripting/templating solution, similar to PHP. It doesn't have the overhead/safetynet of a proper framework behind it (like MVC), and it uses RAZOR to support the view engine.
For any non-trivial new projects, ASP.Net MVC is the industry standard.
I've tried to mix up WebForm and MVC in the same application, but so far I've failed miserably. It looks like I'm missing some steps some how some where. I'm really tired.
I wonder if just it's bad prectice to have 3 projects in a solution: The first one for the Model, the second one for the Webform, and the last one for the MVC.
Thanks for helping
If you have two separate projects one for MVC and one for classic WebForms it's like you have two distinct web applications. Those two should be deployed separately in different virtual folders in IIS.
On the other hand you have the possibility to mix classic WebForms and ASP.NET MVC in the same project.
Usually people have some legacy WebForms application that they want to migrate in ASP.NET MVC. But due to the sheer amount of code this cannot be done at once so you would create a new ASP.NET MVC application and import the existing legacy WebForms inside it which could be directly used. Then you could progressively update legacy code to the MVC pattern.
But from personal experience I find it dirty mixing classic WebForms with ASP.NET MVC. My hands just feel dirty. What I do is that I would keep legacy WebForms as a separate application and start replacing different sections of it with a new ASP.NET MVC application and the two of them would communicate only through standard HTTP techniques (usually GET and POST verbs).
I am a ASP.net Web Form Developer , I simply want to know that is it possible to develop a mini ERP solution in ASP.net MVC ?
I have already developed such in ASP.net Web Forms but our company wants to re-write to whole app from scratch for bigger scale with increased modules and functionalities.
So can we go with ASP.net MVC this time rather than Web Forms?
Thanks in advance.
Yes it is possible. Everything you could do in WebForms could be done with MVC. After all ASP.NET MVC is based on the ASP.NET engine.
I've got two questions about Asp.Net MVC areas. I have only a shallow understanding of areas from what I've heard about them in various podcasts but I think I understand fairly well what they're supposed to be used for. Now my question is if I could also use them to enable me to gradually switch from development in Asp.Net webforms with VB to Asp.Net MVC with C#.
Can I mix areas of different languages in one application, for example one area is a C# project and another is a VB.Net project.
Could I use the areas feature to incorporate MVC into an existing webforms application? Lets say I have a Asp.Net webforms application but I want any new "pages" to be written using MVC, could I create a new MVC project and then "jack it in" as an area into the existing webforms application?
In response to your questions:
Yes. If it's a separate assembly, then it won't matter if it's in c# or VB.net.
I'd say yes - it will help to keep your MVC stuff separate, but of course you will need the basic bootstrap stuff in your base webforms project. Good idea.
I've recently started introducing MVC into an older webforms site, and it's well worth the effort.