ASP.NET MVC by default ships with two view engines: Web Forms and Razor. When we are creating a new ASP.NET MVC application both are being included in the application startup. Even when you are working with Razor only ASP.NET MVC resolves named views by searching for files that match the Web Forms view engine's naming convention at first. What can we do to change that and reduce the time needed to return a view to the end user? Let's have a look!
dotnetomaniak.pl - Artykuły z tagiem ASP.NET WebForms
![[EN] How to coolify your (web) application - First Steps | blog.kateo.pl]()
ASP.NET WebForms
Main menuMain pageAboutContact Share article via: You've read lot of articles about advanced C# constructions, new features, frameworks, etc. and at the end you are opening your solution and you start looking... and thinking... what is wrong the hell? Why my project is so f* boring? I'd like to change something. I want to have the cool application, which I want to be proud of and compare this solution with the ones I've read about. If this situations happened before this article is for you...
Źródło:
blog.kateo.pl
Dziel się z innymi:
Sztuka programowania 3504 dni, 2 godziny, 34 minuty temu 144 źrodło rozwiń
Polecamy
Najaktywniejsi w tym miesiącu
Nadchodzące wydarzenia
.Net
.net core
architektura
ASP .NET
asp.net
Asp.Net Core
ASP.NET MVC
Azure
C#
C# .NET
certyfikacja
certyfikat
cloud
csharp
daj sie poznac 2017
Daj się poznać
Daj Się Poznać 2017
dajsiepoznac
DDD
docker
dotnet
dsp2017
egzamin
Entity Framework
F#
git
JavaScript
jQuery
konferencja
Linq
mvc
MVVM
Narzędzia
performance
podcast
praca
programowanie
SharePoint
Silverlight
SQL
sql server
TDD
testy
Visual Studio
WCF
Windows
windows phone
WPF
Wzorce projektowe
Xamarin