I am an ASP.NET developer. What is the latest technology in ASP.NET and also the documentation about it?
For MVC it is ASP.NET MVC 2 and for web forms it is ASP.NET 4.0.
I notice MVC has been suggested, but dont forget to checkout Silverlight as well for delivering rich interactive application over the web.
As the previous answers state, MVC is the new thing.
This means that their are now 2 main forms of ASP.NET development: WebForms and MVC
In WebForms, there are only a handful of new things (in VS2010), with support for routing (friendly URLs) the most notable.
That would be ASP.NET 4.0 and ASP.NET MVC 2.0. Documentation? Like ALWAYS, in MSDN.
Related
I am working on a new module into an old legacy ASP.net webForms project.
Currently, I do not have access to the code. The client wants us to make a stand-alone application, for now, once they're happy, they will merge the module into their existing ASP.net web forms application.
I am planning to make this module in asp.net core 2.1 MVC using Entity framework.
Two queries :
1) Would the new ASP.net core MVC 2.1 module be compatible with old ASP.net webforms web app. made in older.Net Framework?
2) Is it feasible to keep the new module made in ASP.net core MVC with the existing modules made in ASP.net Webforms?
Would the new ASP.net core MVC 2.1 module be compatible with old ASP.net webforms web app. made in older.Net Framework?
From a codebase persective, MVC and Webforms are completely different. You can't integrate them into one project. Possibly two projects in one solution
Is it feasible to keep the new module made in ASP.net core MVC with the existing modules made in ASP.net Webforms?
Yes. They would need to be published through different web applications. This could be transparent to the user because all the activity is through URL's
which version of mvc is using in asp.net core 2.0? is is MVC 6 or use different name ?
What is .net 5?
what is .net standard ?
these questions are from an interview.plz help
The .NET Standard is a formal specification of .NET APIs that are intended to be available on all .NET implementations.https://learn.microsoft.com/en-us/dotnet/standard/net-standard .ASP.NET5.0 Is Called ASP.NET Core 1.0 and In the ASP.NET Core 1.0 release, Web API is merged with ASP.NET MVC, termed as MVC 6
They're totally unrelated. "MVC 6" was sort of like a codename for Core when it was still in early stages. ASP.NET MVC and ASP.NET Web Api are totally separate from ASP.NET Core. Now, it's just "Core". There is no "MVC" or "Web Api", because Core controllers do both functions. ASP.NET MVC and ASP.NET Web Api live on and although they will probably eventually be deprecated, they could presumably (though not likely at all) get new releases. At the very least, they'll be patched for the foreseeable future.
ASP.NET Core is a complete rewrite from the ground up. It was originally created simply to be a cross-platform alternative to ASP.NET, and I think the original plan was to keep both ASP.NET and ASP.NET Core as potential development options. However, as ASP.NET Core became more competent, it has pretty fully eclipsed ASP.NET; we now have a cross-platform framework that can run on Windows, Mac and Linux and can do virtually anything the Windows-only framework can. Therefore, why keep the Windows-only framework?
Asp.net Core 2.0 is MVC 6 and The framework is 4.6.1
To start with development you need to have VS-2017 and for 1.X you can start with VS-2015.
Please refer the below link for clear presentation of .NetCore 2.0 so that you can get good knowledge to kick start your development.
Official Asp.Net Core Documentation Url
I have an application in asp.net 2.0 web forms.
I want to migrate it to Asp.net core web forms.
Is it feasible?
I did not see any link on internet for migration of web forms.
Please provide any link or insight for this.
ASP.NET Core doesn't have a web forms part. It's an old model and won't be includeded in the ASP.NET Core according to Microsoft. The new and recommended model is MVC. There is no interoperability between them, because they have a differt architechture and behavior.
You have two opportunities. First: you don't migrate, everything will work as it has been. Second: you re-implement your solution with ASP.NET Core and with MVC architecture.
Have you seen DotVVM?
It is not Web Forms on .NET Core, but:
many concepts in DotVVM are similar to ASP.NET Web Forms (postbacks, server controls, master pages, even the names of the controls and page lifecycle events)
it is easy to learn for ASP.NET Web Forms developers
no cryptic viewstate hidden field
the controls don't produce ugly HTML
the MVVM pattern is used
no need to know or write JavaScript - C#, HTML and CSS is enough to start coding
DotVVM supports both .NET Core and full .NET Framework
can be added to existing ASP.NET Web Forms or MVC applications on .NET Framework
DotVVM is open source
Visual Studio extension with IntelliSense and project templates
Disclaimer: taken from https://github.com/aspnet/Home/issues/1961#issuecomment-323698018
There are some useful resources I'd like to share with the StackOverflow community just in case you are having troubles to decide what to do:
modernization of your existing Web Forms app
migration to MVC or Core
or whether to start a new project on Web Forms, MVC and Core.
Here you go:
Modernizing ASP.NET Web Forms Applications by Tomáš Herceg (Microsoft MVP ) - https://tomasherceg.com/blog/post/modernizing-asp-net-web-forms-applications-part-1
Migrating Old ASP.NET Applications to .NET Core by Edi Wang (Microsoft MVP) - https://edi.wang/post/2018/10/31/migrating-old-aspnet-applications-to-net-core
Choose between ASP.NET and ASP.NET Core (Microsoft docs) - https://learn.microsoft.com/en-us/aspnet/core/fundamentals/choose-aspnet-framework?view=aspnetcore-3.1 - https://learn.microsoft.com/en-us/aspnet/core/migration/proper-to-2x/?view=aspnetcore-3.1
Migrate from ASP.NET to ASP.NET Core (Microsoft docs) - https://learn.microsoft.com/en-us/aspnet/core/migration/proper-to-2x/?view=aspnetcore-3.1
https://www.telerik.com/blogs/review-of-telerik-toolsets-for-aspnet-web-forms-core
Is it possible to call normal ASPX pages with their normal life-cycle in an ASP.NET MVC 2 application? What about web controls and ajax.net toolkit?
Thank you!
You don't need to do anything. Simply create your MVC application and add a new web forms page. Thats it.
Yes.
Deploying ASP.NET MVC on ASP.NET 2.0
Integrating ASP.NET MVC 3 into existing upgraded ASP.NET 4 Web Forms applications
I recommend creating a WebForms project and using this NuGet package:
AddMvc3ToWebForms
I would like to know if it is at all possible to get an MVC3 solution wrapped in a CWAB (Composite Web Application Block) solution built in 3.5?
I'm aware that in IIS, 2.0/3.5 and 4.0 sites can run next to each other (but in different application pools) but because of the CWAB layer I do not have this luxury. I got MVC2 running successfully before but MVC2 is on the 2.0 runtime if what I've read is true.
I would really like to use Razor as well so going back to MVC2 in this scenario is not really an option.
It should be possible. Just set your application pool runtime to 4.0 instead of 2.0.
.NET 4.0 runtime will be able to handle .NET 3.5 assemblies.
Razor requires features in .NET 4.0. However Tom Clarkson has a post called ASP.NET MVC 3 Razor View in SharePoint that talks about a (not-so-pretty) work-around. Basically, generate the view code from the cshtml files in .NET 4 and you can use them in .NET 3.5 (with a modified RazorEngine).
I'm encountering the same issue. The way I'm going to handle it is to write a WCF "front end" to SharePoint (.Net 3.5) and this will allow me to write the MVC app using MVC 3.