I started playing with Spark in an ASP.NET MVC project. However I have an existing ASP.NET project that I can't port over to ASP.NET MVC, and was wondering if there is a way to use Spark with ASP.NET?
Yes, Spark View Engine is awesome. And when you've tried it, there is no going back.
Spark requires either ASP.NET MVC or Castle Monorail, so I guess mixing MVC and WebForms would be the only way to start using Spark in a WebForms-project..
Start by combining WebForms and MVC (with Spark) in the same project. Then start migrating .aspx/code-behind into .spark/controls, file by file.
Remember, this refactoring could be pretty costly/time-consuming in a large project.
Plugging ASP.NET MVC into an existing ASP.NET application
Related
I have a huge application which was developed in vb.net.
Our goal to convert this application to C# micro services, but in incremental manner.
So what ever new functionality that we are going to add to the existing application, we are planning to create them as a separate Micro Service with micro front end UI.
Since these are small api's with UI, I am trying to understand whether we can implement this API + UI in a single ASP.NET MVC project as a web component.
I tried 2 options:
Created an ASP.NET MVC application and added angular to same project. Is this better way to mix MVC and Angular in a single project?
I tried creating a sample ASP.NET MVC application with razor ui. But didn't understand how I can use this as a microfrontend component.
I am good in ASP.NET MVC and C#, but not that great in Angular. So planning to create microfrontend component in ASP.NET MVC razor.
Is it possible to do this? As I have to use this micro ui component in vb.net, I need this to be generated as js file to use further.
I'm going to create a new web application for my company and I would like doing it with Asp MVC technology.
So, can you please tell me the difference between an Asp.Net Core MVC and an Asp.Net Framework MVC application?
Both do about the same things, but NET Core is newer, faster, multiplatform, easier to test, open source and will become the only one in the long run. See https://devblogs.microsoft.com/dotnet/introducing-net-5/.
Some stuff (ie Blazor Server) is only available on Core.
Speaking of MVC the only difference I recall is Framework having 2 controllers (one for views and one for API) which has become a single one in Core.
See also https://learn.microsoft.com/en-us/aspnet/core/fundamentals/choose-aspnet-framework?view=aspnetcore-3.1
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
I have a large legacy web application written in a combination of classic asp and asp.net webforms. The client has agreed to rewrite the application and we have decided to use MVC4 but of course we don't have the time to stop support on the legacy application to build the new application.
Is there a way to put an new MVC4 wrapper application around the existing/legacy application so that parts of the legacy application can be ported to the new environment piece by piece?
this is pretty old question, but I ran across it so thought I'd try and help out. You can still use the .aspx pages within MVC4 by modifying the routing functionality of MVC. this link should help you get started: http://weblogs.asp.net/scottgu/archive/2009/10/13/url-routing-with-asp-net-4-web-forms-vs-2010-and-net-4-0-series.aspx
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).