<\/div>\n

Merhaba,<\/p>\n

Uzun zamand\u0131r Asp.NET Core 2 MVC’de klasik Asp.NET MVC’ye nazaran hangi noktalarda de\u011fi\u015fiklik ger\u00e7ekle\u015ftirildi\u011fine dair genel bak\u0131\u015f maksatl\u0131 makale yazmay\u0131 planl\u0131yordum. Bu plan\u0131m do\u011frultusunda \u015fimdi gelin Asp.NET Core 2 MVC’de gelen yenilikleri ve de\u011fi\u015fiklikleri parsel parsel \u00f6zetleyelim.<\/p>\n

Asp.NET Core 2 MVC Projesinin Aya\u011fa Kald\u0131r\u0131lmas\u0131<\/h3>\n

\u0130lk olarak bir Asp.NET Core 2 MVC projesinin nas\u0131l aya\u011fa kald\u0131r\u0131ld\u0131\u011f\u0131na dair t\u00fcm yap\u0131ya de\u011finmemiz gerekmektedir. Asp.NET Core 2 MVC projesi olu\u015fturabilmek i\u00e7in Visual Studio edit\u00f6r\u00fcnde klasik “File” -> “New” -> “Project” kombinasyonu \u00fczerinden “ASP.NET Core Web Appllication” projesini se\u00e7iyoruz.
\n $\"Asp.NET$ <\/a>
\nArd\u0131ndan gelen pencereden “Empty”i se\u00e7erek bo\u015f bir proje olu\u015fturuyoruz.
\n $\"Asp.NET$ <\/a>
\nA\u00e7\u0131lan projenin Solution Explorer penceresinden dosyalar\u0131na g\u00f6z atarsak e\u011fer;
\n $\"Asp.NET$ <\/a><\/p>\n

G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere “Dependencies” ve “Properties” alanlar\u0131yla birlikte “wwwroot” klas\u00f6r\u00fc ve “Program.cs” ve “Startup.cs” dosyalar\u0131 mevcuttur. Bu klas\u00f6r ve dosyalar\u0131 izah etmemiz gerekirse e\u011fer;<\/p>\n

Dependencies Alan\u0131<\/em><\/strong>
\nProjede kullan\u0131lan Nuget vs. mod\u00fcllerinin tutuldu\u011fu aland\u0131r. Klasik Asp.NET MVC’de ki ‘References’ klas\u00f6r\u00fcne denk d\u00fc\u015fmektedir.<\/li>\n

Properties Alan\u0131<\/em><\/strong>
\nProjeyle ilgili temel ba\u015flang\u0131\u00e7 ayarlar\u0131n\u0131n tutuldu\u011fu alan.<\/li>\n

wwwroot Klas\u00f6r\u00fc<\/em><\/strong>
\nProjede kullan\u0131lacak CSS, JavaScript, Image vs. dosyalar\u0131n\u0131n tutulaca\u011f\u0131 klas\u00f6r.<\/li>\n

Program.cs<\/em><\/strong>
\nAsp.NET Core uygulamalar\u0131nda host yap\u0131s\u0131 klasik Asp.NET mimarisine nazaran k\u00f6kl\u00fc de\u011fi\u015fikliklere tabi tutulmu\u015ftur. Bizler “Program.cs” dosyas\u0131n\u0131 Console Application projelerinden tan\u0131yoruz. Asp.NET Core mimarisinde “Program.cs” dosyas\u0131n\u0131n bulunmas\u0131 Asp.NET Core uygulamalar\u0131n\u0131n asl\u0131nda bir Console Application uygulamas\u0131 oldu\u011fu anlam\u0131na geliyor. Bu da ilgili mimarinin executable(\u00e7al\u0131\u015ft\u0131r\u0131labilir) bir alt yap\u0131da oldu\u011funu ve entry pointe(ba\u015flang\u0131\u00e7 noktas\u0131) sahip oldu\u011funu ifade etmektedir. \u0130\u015fte bu ba\u015flang\u0131\u00e7 noktas\u0131 “Program.cs” de ki static Main metodudur.\u015eimdi “Program.cs” s\u0131n\u0131f\u0131nda neler yap\u0131l\u0131yor bakal\u0131m;<\/p>\n
\r\n public class Program\r\n {\r\n public static void Main(string[] args)\r\n {\r\n CreateWebHostBuilder(args).Build().Run();\r\n }\r\n\r\n public static IWebHostBuilder CreateWebHostBuilder(string[] args) =>\r\n WebHost.CreateDefaultBuilder(args)\r\n .UseStartup<Startup>();\r\n }\r\n<\/pre>\n
Dikkat ederseniz Main metodunda “CreateWebHostBuilder” isimli metodu \u00e7a\u011f\u0131rararak bir host in\u015fa etmekte ve bunu \u00e7al\u0131\u015ft\u0131rmaktad\u0131r. \u0130lgili metot i\u00e7erisine g\u00f6z atarsak e\u011fer ba\u015flang\u0131\u00e7 s\u0131n\u0131f\u0131 olarak “Startup” s\u0131n\u0131f\u0131n\u0131 belirtmektedir.<\/li>\n
Startup.cs<\/em><\/strong>
\nProjemizde herbir kullan\u0131c\u0131 ile yap\u0131lan etkile\u015fim neticesinde bir s\u00fcrece girilmektedir. \u0130\u015fte o s\u00fcreci “Startup” s\u0131n\u0131f\u0131nda kontrol edebilmekteyiz. “Startup” s\u0131n\u0131f\u0131 asl\u0131nda bir Middleware \u00f6zelli\u011fi g\u00f6rmektedir. Yap\u0131sal olarak;<\/p>\n
\r\n public class Startup\r\n {\r\n public void ConfigureServices(IServiceCollection services)\r\n {\r\n \/\/Uygulamada kullan\u0131lacak servisleri burada belirterek projeye dahil ediyoruz.\r\n }\r\n\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n \/\/\u00c7al\u0131\u015fma zaman\u0131nda tetiklenen ayar fonksiyonudur.\r\n if (env.IsDevelopment())\r\n {\r\n app.UseDeveloperExceptionPage();\r\n }\r\n\r\n app.Run(async (context) =>\r\n {\r\n await context.Response.WriteAsync("Hello World!");\r\n });\r\n }\r\n }\r\n<\/pre>\n
\u015feklinde bir yap\u0131ya sahiptir.
\nProjemizi aya\u011fa kald\u0131r\u0131rken “Startup” s\u0131n\u0131f\u0131nda a\u015fa\u011f\u0131daki ayarlar\u0131 yapabiliriz.<\/p>\n
\r\n public class Startup\r\n {\r\n public void ConfigureServices(IServiceCollection services)\r\n {\r\n \/\/MVC mod\u00fcl\u00fcn\u00fc projemizde yap\u0131land\u0131ral\u0131m.\r\n services.AddMvc();\r\n }\r\n\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n \/\/Varsay\u0131lan route yap\u0131lanmas\u0131yla MVC'yi kullanabiliriz.\r\n \/\/app.UseMvcWithDefaultRoute();\r\n\r\n \/\/Ya da route yap\u0131lanmas\u0131n\u0131 manuel olu\u015fturmak kayd\u0131yla MVC'yi kullanabiliriz.\r\n app.UseMvc(routes =>\r\n {\r\n routes.MapRoute(\r\n name: "default",\r\n template: "{controller=Home}\/{action=Index}\/{id?}"\r\n );\r\n routes.MapRoute(\r\n name: "About",\r\n template: "about",\r\n defaults: new { controller = "Home", action = "About" }\r\n );\r\n });\r\n\r\n \/\/Uygulamadaki wwwroot klas\u00f6r\u00fcn\u00fcn i\u00e7erisindeki t\u00fcm dosyalara proje genelinden static bir \u015fekilde eri\u015fim izni vermek i\u00e7in UseStaticFiles fonksiyonu ile ilgili dosyay\u0131 eri\u015fime a\u00e7\u0131yoruz.\r\n app.UseStaticFiles();\r\n\r\n \/\/Projede al\u0131nan hatalar\u0131n kullan\u0131c\u0131ya g\u00f6sterilmesini isteyebiliriz.\r\n \/\/app.UseDeveloperExceptionPage();\r\n\r\n \/\/Ya da sadece development esnas\u0131ndaysak kullan\u0131c\u0131lara hata sayfas\u0131n\u0131 g\u00f6sterebiliriz.\r\n if (env.IsDevelopment())\r\n app.UseDeveloperExceptionPage();\r\n\r\n \/\/Aran\u0131lan kaynak bulunamad\u0131\u011f\u0131 durumlarda 404 hatas\u0131n\u0131n kullan\u0131c\u0131ya g\u00f6terilmesini istiyorsak UseStatusCodePages fonksiyonu \u00e7a\u011f\u0131rmam\u0131z yeterlidir.\r\n app.UseStatusCodePages();\r\n }\r\n }\r\n<\/pre>\n
Genel olarak kod \u00fczerine kullan\u0131lan fonksiyonlar\u0131n a\u00e7\u0131klamalar\u0131n\u0131 yapm\u0131\u015f bulunmaktay\u0131m.<\/li>\n<\/ul>\n
Evet… Proje dosyalar\u0131m\u0131z\u0131n ne oldu\u011funu g\u00f6rd\u00fck, alt yap\u0131 olarak MVC olacak \u015fekilde gerekli ayarlamalar\u0131 ger\u00e7ekle\u015ftirdik. \u015eimdi projemizin ana dizinine “Models”, “Views” ve “Controllers” isimlerinde \u00fc\u00e7 adet klas\u00f6r olu\u015fturuyoruz ve Asp.NET Core 2 MVC projemizi bu \u015fekilde aya\u011fa kald\u0131rm\u0131\u015f oluyoruz…<\/p>\n
_ViewImports Dosyas\u0131 \u0130le Global Yap\u0131lanma<\/h3>\n
Klasik Asp.NET MVC’de .cshtml dosyalar\u0131na model tan\u0131mlarken ya modelin bulundu\u011fu namespaceleri tam olarak belirtmemiz gerekmekteydi ya da web.config’den modellerin bulundu\u011fu namespace’i t\u00fcm viewlere global bir \u015fekilde bir kere tan\u0131mlay\u0131p sunmam\u0131z yeterliydi. Asp.NET Core 2 MVC’de art\u0131k web.config dosyas\u0131 bulunmad\u0131\u011f\u0131ndan dolay\u0131 bu i\u015flevi “_ViewImports.cshtml” dosyas\u0131 \u00fcstlenmektedir.<\/p>\n
\r\n@model CoreExample.Web.Models.Employee\r\n\r\n<h2>Employee<\/h2>\r\n<\/pre>\n
Yukar\u0131daki \u00f6rnek .cshtml sayfas\u0131nda oldu\u011fu gibi model tan\u0131mlan\u0131rken modelin bulundu\u011fu t\u00fcm namespaceleri belirtmemiz gerekmektedir. \u015eimdi bu namespace’i t\u00fcm viewlere global olarak tan\u0131mlamak istiyorsak ilgili klas\u00f6re Razor View Imports dosyas\u0131n\u0131 “_ViewImports.cshtml” isminde eklemeniz gerekmektedir.
\n $\"Asp.NET$ <\/a>
\n\u0130lgili dosyan\u0131n i\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi \u015fekillendirirsek;<\/p>\n
\r\n@using CoreExample.Web.Models\r\n<\/pre>\n
Art\u0131k bu namespace global olarak tutulaca\u011f\u0131 i\u00e7in view dosyalar\u0131nda direkt olarak ilgili modeli namespace’i belirtmeksizin \u00e7a\u011f\u0131rabilmekteyiz.<\/p>\n
\r\n@model Employee\r\n\r\n<h2>Employee<\/h2>\r\n<\/pre>\n
Tag Helper Yap\u0131lanmas\u0131<\/h3>\n
Klasik Asp.NET MVC’de ki Html.Helper alt\u0131ndaki t\u00fcm helper metotlar\u0131 gitti yerine tag helperlar geldi.
\nTag helperlar\u0131 kullanabilmek i\u00e7in kullan\u0131laca\u011f\u0131 sayfan\u0131n en \u00fcst sat\u0131r\u0131na a\u015fa\u011f\u0131daki kodu eklemeniz gerekmektedir.<\/p>\n
\r\n@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers\r\n<\/pre>\n
ya da tek tek view dosyalar\u0131na eklemekle u\u011fra\u015fmaktansa “_ViewImports.cshtml” dosyas\u0131na da ekleyebilirsiniz.<\/p>\n
\r\n@using CoreExample.Web.Models\r\n@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers\r\n<\/pre>\n
Bu i\u015flemden sonra tag helperlar\u0131 a\u015fa\u011f\u0131daki gibi kullanabilirsiniz.<\/p>\n
\r\n@model Employee\r\n\r\n<h2>Employee<\/h2>\r\n\r\n<p>\r\n <label asp-for="Name">Name<\/label>\r\n <input asp-for="Name" \/>\r\n<\/p>\r\n<p>\r\n <label asp-for="SurName">Surname<\/label>\r\n <input asp-for="SurName" \/>\r\n<\/p>\r\n<p>\r\n <label asp-for="Age">Age<\/label>\r\n <input asp-for="Age" \/>\r\n<\/p>\r\n<\/pre>\n
G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere tag helperlar \u00fcretecekleri html elemanlar\u0131 kullan\u0131ld\u0131\u011f\u0131 sayfan\u0131n modeline uygun bir \u015fekilde bind etmekte ve hatta e\u015fle\u015ftirilen propertynin tipine g\u00f6re olu\u015fturulacak inputun de\u011feri otomatik belirlenmektedir.(string ise text, int ise number vs.)<\/p>\n
Hatta tag helperlar yaz\u0131m esnas\u0131nda sayfa modelinin memberlar\u0131n\u0131 IntelliSense arac\u0131l\u0131\u011f\u0131yla kar\u015f\u0131m\u0131za getirmektedir.
\n $\"Asp.NET$ <\/a>
\n\u0130\u015fte bu \u00f6zellik harika \ud83d\ude42<\/p>\n
Ayr\u0131ca klasik Asp.NET MVC’de ki Action ya da ActionLink helper metotlar\u0131n\u0131n yerine a\u015fa\u011f\u0131daki gibi “asp-action” ve “asp-controller” tag helperlar\u0131 gelmi\u015ftir.<\/p>\n
\r\n@* Ayn\u0131 Controller'da ise; \/Home\/Page*@\r\n<a asp-action="Page">Page1<\/a>\r\n@*\/Home\/Page*@\r\n<a asp-action="Page" asp-controller="Home">Page2<\/a>\r\n@* \/Home\/Page\/5?name=gencay *@\r\n<a asp-action="Page" asp-controller="Home" asp-route-id="5" asp-route-name="gencay">Page3<\/a>\r\n@* \/Home\/Page\/5?name=gencay *@\r\n<a asp-action="Page" asp-controller="Home"\r\n asp-all-route-data='new Dictionary<string, string>\r\n{\r\n { "name","gencay"},\r\n { "id","5"}\r\n}'>Page4<\/a>\r\n<\/pre>\n
Form Yap\u0131lanmas\u0131<\/h3>\n
Form yap\u0131lar\u0131 art\u0131k html olarak a\u015fa\u011f\u0131daki gibi tasarlanmaktad\u0131r.<\/p>\n
\r\n@model Employee\r\n\r\n<form method="post" asp-action="Save" asp-controller="Employee">\r\n <p>\r\n <label asp-for="Name">Name<\/label>\r\n <input asp-for="Name" \/>\r\n <\/p>\r\n <p>\r\n <label asp-for="SurName">Surname<\/label>\r\n <input asp-for="SurName" \/>\r\n <\/p>\r\n <p>\r\n <label asp-for="Age">Age<\/label>\r\n <input asp-for="Age" \/>\r\n <\/p>\r\n <p>\r\n <button type="submit">Save<\/button>\r\n <\/p>\r\n<\/form>\r\n<\/pre>\n
Form Validations<\/h3>\n
\r\n public class Employee\r\n {\r\n public int Id { get; set; }\r\n [Required(ErrorMessage = "Enter the name field")]\r\n public string Name { get; set; }\r\n [Required(ErrorMessage = "Enter the surname field")]\r\n public string SurName { get; set; }\r\n public int Age { get; set; }\r\n }\r\n<\/pre>\n
\r\n public class EmployeeController : Controller\r\n {\r\n public IActionResult Save() => View();\r\n [HttpPost]\r\n public IActionResult Save(Employee employee)\r\n {\r\n if (ModelState.IsValid)\r\n Content("Kay\u0131t ger\u00e7ekle\u015ftirildi.");\r\n\r\n return View(employee);\r\n }\r\n }\r\n<\/pre>\n
\r\n@model Employee\r\n\r\n<form method="post" asp-action="Save" asp-controller="Employee">\r\n <p>\r\n <div asp-validation-summary="All"><\/div>\r\n <\/p>\r\n <p>\r\n <label asp-for="Name">Name<\/label>\r\n <input asp-for="Name" \/>\r\n <\/p>\r\n <p>\r\n <label asp-for="SurName">Surname<\/label>\r\n <input asp-for="SurName" \/>\r\n <\/p>\r\n <p>\r\n <label asp-for="Age">Age<\/label>\r\n <input asp-for="Age" \/>\r\n <\/p>\r\n <p>\r\n <button type="submit">Save<\/button>\r\n <\/p>\r\n<\/form>\r\n<\/pre>\n
Yukar\u0131da div eleman\u0131nda g\u00f6rd\u00fc\u011f\u00fcn\u00fcz “asp-validation-summary” tag helper\u0131 ile validasyon mesajlar\u0131 h\u0131zl\u0131ca verilebilmektedir.
\n $\"Asp.NET$ <\/a><\/p>\n
View Components<\/h3>\n
Asp.NET Core ile hayat\u0131m\u0131za giri\u015f yapm\u0131\u015f olan yepyeni bir terimdir. Kullan\u0131m olarak Partial View yap\u0131lar\u0131na benzemektedirler lakin i\u015fleyi\u015f olarak ba\u015fl\u0131 ba\u015f\u0131na bir cevherdirler.<\/p>\n
Peki ne i\u015fe yaramaktad\u0131r View Componentler?<\/strong>
\nOlay\u0131 ilk olarak Partial View yap\u0131lar\u0131yla ele alal\u0131m. MVC mimarisinde veri k\u00fcmesi kullanan bir Partial View’i her tetikledi\u011fimizde ilgili partial view controller ile ba\u011flant\u0131s\u0131n\u0131 kuracak ve kullanaca\u011f\u0131 modeli bu ba\u011flant\u0131 \u00fczerinden talep edecektir.
\n\u00d6rne\u011fin;<\/p>\n
\r\n@model IEnumerable<CoreExample.Web.Models.Employee>\r\n\r\n<ul>\r\n @foreach (var employee in Model)\r\n {\r\n <li>\r\n @employee.Name @employee.SurName - @employee.Age\r\n <\/li>\r\n }\r\n<\/ul>\r\n<\/pre>\n
\r\n@model Employee\r\n\r\n@Html.Partial("~\/Views\/Home\/Partials\/_EmployeeList.cshtml", ViewBag.Models as IEnumerable<Employee>)\r\n<\/pre>\n
Burada g\u00f6rd\u00fc\u011f\u00fcn\u00fcz \u00fczere partial view’a modeli controllerdan ViewBag.Models de\u011fi\u015fkenine atayarak getirmekteyiz. \u0130\u015fte View Componentler, partial viewlerin bu controller’a olan ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n\u0131 ortadan kald\u0131rmakta ve talep geldi\u011fi zaman direkt olarak modele gidip gereken veritaban\u0131 i\u015flemlerini hallettikten sonra view’e yans\u0131tmaktad\u0131r. Dolay\u0131s\u0131yla controller ile bir ili\u015fi\u011fi olmayaca\u011f\u0131ndan dolay\u0131 daha h\u0131zl\u0131 ve performansl\u0131 \u00e7al\u0131\u015facakt\u0131r.<\/p>\n
View Componentleri kullanabilmek i\u00e7in projenin ana dizininde “ViewComponents” isminde bir klas\u00f6r eklenerek ard\u0131ndan i\u00e7erisine yap\u0131lacak i\u015flemi ifade eden bir isimde class olu\u015fturulur. \u00d6rne\u011fin; EmployeeViewComponent<\/em>
\n\u0130\u00e7erisinde gerekli i\u015flemler yap\u0131l\u0131r;<\/p>\n
\r\n public class EmployeeViewComponent : ViewComponent\r\n {\r\n public IViewComponentResult Invoke()\r\n {\r\n List<Employee> employeeList = new List<Employee> {\r\n new Employee{\r\n Id = 1,\r\n Age = 26,\r\n Name = "Gen\u00e7ay",\r\n SurName = "Y\u0131ld\u0131z"\r\n },\r\n new Employee{\r\n Id = 2,\r\n Age = 34,\r\n Name = "Mehmet",\r\n SurName = "\u0130lhan"\r\n }\r\n };\r\n\r\n return View(employeeList);\r\n }\r\n }\r\n<\/pre>\n
Burada dikkat etmeniz gereken hususlardan biri ilgili s\u0131n\u0131f\u0131n isminin sonuna “..ViewComponent” ekinin eklenmesidir. Bir di\u011feri ilgili s\u0131n\u0131f\u0131 “ViewComponent” s\u0131n\u0131f\u0131ndan t\u00fcretilmesi gerekmektedir. Ve son dikkat edilmesi gereken husus ise bu View Componentin yapaca\u011f\u0131 i\u015fi geriye “IViewComponentResult” interface tipinde de\u011fer d\u00f6nen “Invoke” isimli metot i\u00e7erisinde yap\u0131lmas\u0131d\u0131r.<\/p>\n
\u015eimdi olu\u015fturulan bu View Componenti kullanal\u0131m.
\nAsp.NET Core View Componentleri \u00e7al\u0131\u015fma zaman\u0131nda a\u015fa\u011f\u0131daki yollarda aramaktad\u0131r;<\/p>\n
\n
Views\/<ControllerName>\/Components\/<ViewComponentName>\/<ViewName><\/li>\n
Views\/Shared\/Components\/<ViewComponentName>\/<ViewName><\/li>\n<\/ul>\n
Biz makalemizde ikinci yolu baz alaca\u011f\u0131z.
\n $\"Asp.NET$ <\/a>
\n\u0130lgili view componenti \u00e7a\u011f\u0131r\u0131rken a\u015fa\u011f\u0131daki gibi Invoke edilmesi yeterlidir.<\/p>\n
\r\n@model Employee\r\n\r\n@await Component.InvokeAsync("Employee")\r\n<\/pre>\n
NuGet – Harici K\u00fct\u00fcphanelerin Y\u00f6netimi<\/h3>\n
Harici paketleri y\u00f6netebilmek i\u00e7in projeye sa\u011f t\u0131klay\u0131p “Edit -ProjeAdi-.csproj” sekmesine t\u0131klay\u0131n\u0131z.
\n $\"Asp.NET$ <\/a>
\nBu i\u015flemden sonra a\u00e7\u0131lan pencerede projede kullan\u0131lan t\u00fcm harici mod\u00fclleri g\u00f6rebilirsiniz. “Dependencies” -> “NuGet” kombinasyonu alt\u0131nda birden fazla k\u00fct\u00fcphane olabilir lakin proje publish edildi\u011finde projeye ait edit dosyas\u0131nda bulunan mod\u00fcller haricindekiler silinecektir.<\/p>\n
npm Configuration File \u0130le Mod\u00fcl Y\u00f6netimi<\/h3>\n
Projeye “package.json” isminde bir “npm Configuration File” dosyas\u0131 ekledi\u011finizde bu dosya \u00fczerinden t\u00fcm mod\u00fcl install ya da uninstall y\u00f6netimini sa\u011flayabilirsiniz.<\/p>\n
\r\n{\r\n "version": "1.0.0",\r\n "name": "asp.net",\r\n "private": true,\r\n "devDependencies": {\r\n "bootstrap": "4.1.3",\r\n "jquery": "3.3.1"\r\n }\r\n}\r\n<\/pre>\n
Projeye entegre etmek istedi\u011fimiz t\u00fcm mod\u00fclleri “devDependencies” alan\u0131na belirttikten sonra tek yapmam\u0131z gereken dosyay\u0131 kaydetmemiz. Gerisini Visual Studio bizim i\u00e7in halledecek ve mod\u00fclleri projeye entegre edecektir. Entegre edilen harici mod\u00fclleri “Dependencies” -> “npm” dizini alt\u0131nda g\u00f6rebilirsiniz.
\n $\"Asp.NET$ <\/a><\/p>\n
Evet.. Bu i\u00e7eri\u011fimizde Asp.NET Core 2 MVC mimarisinde m\u00fchim olan ve ilgimi \u00e7eken yeniliklere ve farkl\u0131l\u0131klara \u00f6zet mahiyetinde de\u011finmi\u015f bulunmaktay\u0131m. Elbetteki sonraki yaz\u0131lar\u0131mda burada de\u011findi\u011fim ya da de\u011finmedi\u011fim bir\u00e7ok konuyu hususi olarak de\u011ferlendirecek ve detayl\u0131 i\u00e7erikler olu\u015fturaca\u011f\u0131z.<\/p>\n
\u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle…
\nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere…<\/p>\n
\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n","protected":false},"excerpt":{"rendered":"
Merhaba, Uzun zamand\u0131r Asp.NET Core 2 MVC’de klasik Asp.NET MVC’ye nazaran hangi noktalarda de\u011fi\u015fiklik ger\u00e7ekle\u015ftirildi\u011fine dair genel bak\u0131\u015f maksatl\u0131 makale yazmay\u0131 planl\u0131yordum. Bu plan\u0131m do\u011frultusunda \u015fimdi gelin Asp.NET Core 2 MVC’de gelen yenilikleri ve...<\/p>\n","protected":false},"author":1,"featured_media":9596,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2656],"tags":[2650,2652,2651,2653,2655,2658,2654,2657],"class_list":["post-9548","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-asp-net-core-2-mvc","tag-_viewimports","tag-asp-net-core-2","tag-asp-net-core-2-mvc","tag-asp-net-core-2-mvc-projesi-olusturma","tag-form-validations","tag-npm-configuration-file","tag-tag-helper","tag-view-components"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/comments?post=9548"}],"version-history":[{"count":39,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9548\/revisions"}],"predecessor-version":[{"id":9597,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9548\/revisions\/9597"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/9596"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=9548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=9548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=9548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Form Yap\u0131lanmas\u0131<\/h3>\nForm yap\u0131lar\u0131 art\u0131k html olarak a\u015fa\u011f\u0131daki gibi tasarlanmaktad\u0131r.<\/p>\n