<\/div>\n

Merhaba,<\/p>\n

Web yaz\u0131l\u0131mlar\u0131, genellikle kullan\u0131c\u0131larla etkile\u015fim a\u00e7\u0131s\u0131ndan olduk\u00e7a yo\u011fun bir yap\u0131 arz etmektedirler. Kullan\u0131c\u0131lar web sitesinden bir istekte bulunabilmekte ve bu iste\u011fe kar\u015f\u0131l\u0131k server taraf\u0131ndan uygun cevaplar \u00fcretilip g\u00f6nderilmektedir. Ve t\u00fcm s\u00fcre\u00e7 bu \u015fekilde cereyan etmekte, teknoloji ve yap\u0131lar ne kadar yenilenip g\u00fc\u00e7lendirilsede t\u00fcm mesele bu esasta seyr etmektedir.<\/p>\n

Biz yaz\u0131l\u0131mc\u0131lar ise bu s\u00fcre\u00e7te bazen yap\u0131lan isteklere kar\u015f\u0131l\u0131k verilecek cevaplara m\u00fcdahale ederek varl\u0131\u011f\u0131m\u0131z\u0131 g\u00f6stermek yahut arada farkl\u0131 i\u015flemler ger\u00e7ekle\u015ftirerek s\u00fcrecin gidi\u015fat\u0131na farkl\u0131 y\u00f6n vermek isteyebiliriz. Do\u011fal olarak bu iste\u011fimize kar\u015f\u0131l\u0131k yaz\u0131l\u0131m d\u00fcnyas\u0131nda bir kavram bizlere e\u015flik edecek ve yap\u0131sal olarak belli kurallarla gayemiz do\u011frultusunda bizlere hizmet edecektir.<\/p>\n

\u0130\u015fte kullan\u0131c\u0131 iste\u011fi ile o iste\u011fe kar\u015f\u0131l\u0131k \u00fcretilen cevap aras\u0131na girmemizi ve bu noktada hert\u00fcrl\u00fc i\u015fi y\u00fcr\u00fctmemizi sa\u011flayacak olan bu kavram Middleware(Ara Katman) olarak adland\u0131r\u0131lmaktad\u0131r. Middleware yap\u0131lar\u0131 mant\u0131k olarak request ile response aras\u0131na girip i\u015flem yapmam\u0131z\u0131 sa\u011flamakla birlikte, birden fazla olma durumlar\u0131nda s\u0131ral\u0131 ad\u0131mlar e\u015fli\u011finde i\u015flenmekte ve son middleware i\u015flemide bitti\u011fi an ilgili response kullan\u0131c\u0131ya g\u00f6nderilip s\u00fcre\u00e7 sona erdirilmektedir.<\/p>\n

Peki middleware nas\u0131l kullan\u0131l\u0131r?<\/strong> sorusuna kar\u015f\u0131l\u0131k genel bir cevap vermemiz gerekirse e\u011fer kullan\u0131lan programlama dilleri aras\u0131nda farkl\u0131l\u0131k g\u00f6stermekle birlikte, ayn\u0131 \u00e7at\u0131 alt\u0131nda bulunan birden fazla teknoloji aras\u0131nda bile kullan\u0131m fark\u0131 s\u00f6z konusu olabilmektedir. \u00d6rne\u011fin; Node.js mod\u00fcl\u00fc olan Express.js’de middleware yap\u0131s\u0131n\u0131n nas\u0131l kullan\u0131ld\u0131\u011f\u0131na dair Express.js \u2013 Middleware(Ara Katman) Nedir? Nas\u0131l Kullan\u0131l\u0131r?<\/a> ba\u015fl\u0131kl\u0131 makalemizi kaleme alm\u0131\u015ft\u0131k. Bu i\u00e7eri\u011fimizde ise Asp.NET Core 2 mimarisinde middleware yap\u0131lar\u0131n\u0131n nas\u0131l kullan\u0131ld\u0131\u011f\u0131na dair bir incelemede bulunaca\u011f\u0131m\u0131z i\u00e7in ara katman mant\u0131\u011f\u0131n\u0131n iki farkl\u0131 platform aras\u0131ndaki fark\u0131n\u0131 rahatl\u0131kla de\u011ferlendirebilirsiniz.<\/p>\n

\u015eimdi fazla uzatmadan Asp.NET Core 2 mimarisinde middleware yap\u0131s\u0131na ufaktan giri\u015f yapmaya ba\u015flayal\u0131m \ud83d\ude42<\/p>\n

Asp.NET Core 2’de Middleware Yap\u0131s\u0131<\/h3>\n
Asp.NET Core 2’de middleware yap\u0131lar\u0131 projenin “Startup” s\u0131n\u0131f\u0131 i\u00e7erisindeki “Configure” isimli metot taraf\u0131ndan bar\u0131nd\u0131r\u0131lmaktad\u0131r. Bu metot, yap\u0131lan iste\u011fe kar\u015f\u0131l\u0131k verilecek cevaplara istinaden ara katman olarak \u00e7al\u0131\u015fmakta ve \u00f6ncelik olarak belli ba\u015fl\u0131 i\u015flemleri ger\u00e7ekle\u015ftirmektedir. Zaten \u015fu ana kadar Asp.NET Core projelerinde ilgili metot i\u00e7erisinde kulland\u0131\u011f\u0131m\u0131z \u00e7o\u011fu fonksiyon asl\u0131nda bir middleware g\u00f6revi g\u00f6ren yap\u0131lard\u0131.<\/p>\n
\r\n.\r\n.\r\n.\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n if (env.IsDevelopment())\r\n app.UseDeveloperExceptionPage();\r\n\r\n app.UseStaticFiles();\r\n app.UseExceptionHandler("\/Error\/Index");\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 });\r\n }\r\n.\r\n.\r\n.\r\n<\/pre>\n
Yukar\u0131daki kod blo\u011funda oldu\u011fu gibi;<\/p>\n
\n
UseStaticFiles<\/em><\/strong>,<\/li>\n
UseExceptionHandler<\/em><\/strong>,<\/li>\n
UseDeveloperExceptionPage<\/em><\/strong> ve hatta<\/li>\n
UseMvc<\/em><\/strong><\/li>\n
.vs .vs<\/li>\n<\/ul>\n
bir middleware yap\u0131s\u0131nda fonksiyonlard\u0131r. Evet… sonuncu olan “UseMvc” fonksiyonuda bir middleware’dir. \u0130lgin\u00e7tir ama \u00f6yledir. MVC; yap\u0131sal olarak sade ve sadece bir tasar\u0131m desenidir. Klasik Asp.NET MVC bu tasar\u0131m desenini \u00f6z\u00fcmseyerek mimariyle b\u00fct\u00fcnselle\u015ftirmi\u015ftir. Her ne kadar kullan\u0131\u015fl\u0131 ve harika bir tasar\u0131m deseni olsada bir yakla\u015f\u0131mdan ibaret olmas\u0131, hi\u00e7 yoktan tercih edilebilir olmas\u0131n\u0131 gerektirmekteyken klasik Asp.NET MVC kay\u0131ts\u0131z \u015farts\u0131z MVC yakla\u015f\u0131m\u0131n\u0131 altyap\u0131 olarak zorunlu tutmay\u0131 tercih etmi\u015ftir. Asp.NET Core mimarisi ise MVC tasar\u0131m desenini tercihimize b\u0131rakarak biz geli\u015ftiricilere se\u00e7me \u00f6zg\u00fcrl\u00fc\u011f\u00fc sa\u011flamaktad\u0131r. Dolay\u0131s\u0131yla “UseMvc” metodu bir middleware olarak proje aya\u011fa kald\u0131r\u0131l\u0131rken komple sistemin genel yakla\u015f\u0131m\u0131n\u0131 belirleyecek tarzda tasarlanm\u0131\u015ft\u0131r.<\/p>\n
\u00d6zel Middleware Olu\u015fturma<\/h3>\n
Asp.NET Core 2’de middleware yap\u0131s\u0131 olu\u015fturmak i\u00e7in yapmam\u0131z gereken tek \u015fey “Startup” s\u0131n\u0131f\u0131na kodlar\u0131m\u0131z\u0131 uygun bir \u015fekilde yerle\u015ftirmektir. “Hocam, uygun bir \u015fekilde yerle\u015ftirmekten kast\u0131n nedir?<\/em>” diye sorarsan\u0131z e\u011fer onun cevab\u0131n\u0131 yaz\u0131m\u0131z\u0131n devam\u0131nda “short circuit(k\u0131sa devre)” konusunu ele al\u0131rken verece\u011fim. \u00d6rne\u011fin; projemiz a\u00e7\u0131l\u0131rken Dependency Injection ile database s\u0131n\u0131f\u0131 olarak tan\u0131mlanan “DbContext” t\u00fcrevi s\u0131n\u0131f\u0131m\u0131z\u0131 middleware’de elde edip, varsa migrationlar\u0131 migrate edelim.<\/p>\n
\r\n public class Startup\r\n {\r\n public IConfiguration Configuration { get; set; }\r\n\r\n public Startup(IConfiguration configuration)\r\n {\r\n Configuration = configuration;\r\n }\r\n\r\n public void ConfigureServices(IServiceCollection services)\r\n {\r\n services.AddDbContext<DatabaseContext>(options => options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")));\r\n services.AddMvc();\r\n }\r\n\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n if (env.IsDevelopment())\r\n app.UseDeveloperExceptionPage();\r\n\r\n app.UseStaticFiles();\r\n app.UseExceptionHandler("\/Error\/Index");\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 });\r\n\r\n #region Custom Middleware\r\n DatabaseContext context = app.ApplicationServices.GetRequiredService<DatabaseContext>();\r\n context.Database.Migrate();\r\n #endregion\r\n }\r\n }\r\n<\/pre>\n
E\u011fer bu \u015fekilde middleware’i yazarsan\u0131z a\u015fa\u011f\u0131daki hatayla kar\u015f\u0131la\u015f\u0131rs\u0131n\u0131z.
\n $\"Asp.NET$ <\/a>
\nHatan\u0131n metinsel halide a\u015fa\u011f\u0131daki gibi olacakt\u0131r;<\/p>\n
System.InvalidOperationException: ‘Cannot resolve scoped service ‘MiddlewareCore.Models.Context.DatabaseContext’ from root provider.’<\/strong><\/em><\/p><\/blockquote>\n
Bu hatay\u0131 iki farkl\u0131 y\u00f6ntemle \u00e7\u00f6zebilirsiniz;<\/p>\n
\n
Scope olu\u015fturarak;<\/em>
\nUygulama servislerine eri\u015febilmek i\u00e7in scope olu\u015fturabilir ve ard\u0131ndan ilgili scope \u00fczerinden servisi talep edebilirsiniz.<\/p>\n
\r\n.\r\n.\r\n.\r\n #region Custom Middleware\r\n using (var serviceScope = app.ApplicationServices.CreateScope())\r\n {\r\n DatabaseContext context = serviceScope.ServiceProvider.GetRequiredService<DatabaseContext>();\r\n context.Database.Migrate();\r\n }\r\n #endregion\r\n.\r\n.\r\n.\r\n<\/pre>\n<\/li>\n
\n“Program.cs” s\u0131n\u0131f\u0131nda “ValidateScopes” \u00f6zelli\u011fine “false” de\u011ferini vererek;<\/em><\/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 .UseDefaultServiceProvider(option => option.ValidateScopes = false);\r\n }\r\n<\/pre>\n<\/li>\n<\/ol>\n
Her iki y\u00f6ntemden biri uyguland\u0131\u011f\u0131 taktirde uygulama tetiklenirken middleware devreye girecek ve \u00f6nceden dahil edilmi\u015f “DbContext” t\u00fcrevi nesneyi elde ederek, \u00fczerinden migrate i\u015flemini ger\u00e7ekle\u015ftirecektir.<\/p>\n
Middlewarelerin Register Edilme S\u0131ras\u0131<\/h3>\n
Yukar\u0131daki sat\u0131rlarda short circuit(k\u0131sa devre) konusuna at\u0131fta bulunmu\u015f, olas\u0131 bir sorunuza istinaden cevab\u0131m\u0131z\u0131 sonraya saklam\u0131\u015ft\u0131k. \u0130\u015fte \u015fimdi o sorunun cevab\u0131n\u0131 verece\u011fimiz sat\u0131rlara gelmi\u015f bulunmaktay\u0131z. (soruyu hat\u0131rlam\u0131yorsan\u0131z “\u00d6zel Middleware Olu\u015fturma” alt ba\u015fl\u0131\u011f\u0131n\u0131n ilk paragraf\u0131na h\u0131zl\u0131ca g\u00f6z at\u0131n\u0131z.)<\/span><\/p>\n
E\u011fer ki, birden fazla middleware ile \u00e7al\u0131\u015facaksan\u0131z bu middlewarelerin yaz\u0131lma s\u0131ras\u0131 olduk\u00e7a \u00f6nem arz etmektedir. Bunun nedeni; kimi middleware’ler short circuit(k\u0131sa devre) yaparak direkt i\u015fleyi\u015fi neticelendirmekte, kimileri ise i\u015flevlerini bitirdikten sonra bir sonraki middleware’e i\u015fleyi\u015fi aktarmaktad\u0131rlar. S\u00f6z gelimi a\u015fa\u011f\u0131daki \u00f6rne\u011fi incelerseniz anlat\u0131lmaya \u00e7al\u0131\u015fan\u0131 daha net izah etmi\u015f olaca\u011f\u0131z;<\/p>\n
\r\n.\r\n.\r\n.\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n if (env.IsDevelopment())\r\n app.UseDeveloperExceptionPage();\r\n\r\n app.UseStaticFiles();\r\n app.UseExceptionHandler("\/Error\/Index");\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 });\r\n }\r\n.\r\n.\r\n.\r\n<\/pre>\n
Yukar\u0131daki \u00f6rnek kod blo\u011funda; “UseDeveloperExceptionPage<\/em>“, “UseStaticFiles<\/em>“, “UseExceptionHandler<\/em>” ve “UseMvc<\/em>” middleware’leri kullan\u0131lmaktad\u0131r. Lakin dikkat ederseniz “UseDeveloperExceptionPage<\/em>” middleware’i \u00e7a\u011fr\u0131l\u0131rken “IsDevelopment<\/em>” kontrol\u00fc yap\u0131lmakta yani development modundaysak bu middleware’i \u00e7al\u0131\u015ft\u0131r\u0131lmaktad\u0131r. Bu kontrol\u00fcn nedeni; “UseDeveloperExceptionPage<\/em>” middleware’inin short circuit(k\u0131sa devre) bir middleware olmas\u0131ndan kaynaklanmaktad\u0131r. E\u011fer ilgili fonksiyon tetiklenirse i\u015flevsel a\u00e7\u0131dan s\u00fcreci neticelendirece\u011finden dolay\u0131 di\u011fer fonksiyonlara ak\u0131\u015f\u0131 sa\u011flamayacakt\u0131r. Dolay\u0131s\u0131yla “UseDeveloperExceptionPage<\/em>” fonksiyonu k\u0131sa devre \u00f6zelli\u011finden dolay\u0131 kontroll\u00fc bir \u015fekilde kullan\u0131lmaktad\u0131r. Di\u011fer fonksiyonlar\u0131m\u0131z ise kendi i\u015flevsellikleri bittikten sonra ak\u0131\u015f\u0131 sonland\u0131rmay\u0131p bir sonraki middleware’e aktaraca\u011f\u0131ndan dolay\u0131 direkt olarak kullan\u0131labilmektedirler. \u0130\u015fte bu mant\u0131ktan dolay\u0131 middleware’lerin register edilme s\u0131ralar\u0131 b\u00fcy\u00fck \u00f6nem ta\u015f\u0131maktad\u0131r.<\/p>\n
Run Metodu<\/h3>\n
Run metodu yukar\u0131da ele ald\u0131\u011f\u0131m\u0131z short circuit olay\u0131n\u0131 yapmam\u0131z\u0131 sa\u011flayan bir yap\u0131ya sahiptir. \u00d6rne\u011fin a\u015fa\u011f\u0131daki kod blo\u011funu inceleyiniz;<\/p>\n
\r\n.\r\n.\r\n.\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n app.Run(async context => await context.Response.WriteAsync("Middleware 1."));\r\n app.Run(async context => await context.Response.WriteAsync("Middleware 2."));\r\n }\r\n.\r\n.\r\n.\r\n<\/pre>\n
$\"Asp.NET$ <\/a>
\nG\u00f6rd\u00fc\u011f\u00fcn\u00fcz gibi Run metodu iki kere kullan\u0131ld\u0131\u011f\u0131 halde ekrana sadece “Middleware 1.” sonucunu yazd\u0131rm\u0131\u015f ve k\u0131sa devre ile t\u00fcm ak\u0131\u015f\u0131 sonland\u0131rm\u0131\u015ft\u0131r.<\/p>\n
Use Metodu<\/h3>\n
Run metoduna nazaran, devreye girdikten sonra s\u00fcre\u00e7te s\u0131radaki middleware’i \u00e7a\u011f\u0131rarak ard\u0131ndan o middleware’\u0131n i\u015flevi bittikten sonra geriye d\u00f6n\u00fcp devam edebilen bir yap\u0131ya sahiptir.<\/p>\n
\r\n.\r\n.\r\n.\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n app.Use(async (context, next) =>\r\n {\r\n Debug.WriteLine("Middleware ba\u015flad\u0131.");\r\n\r\n await next.Invoke();\r\n\r\n Debug.WriteLine("Middleware sonland\u0131r\u0131l\u0131yor.");\r\n });\r\n\r\n app.Run(async context =>\r\n {\r\n Debug.WriteLine("K\u0131sa devre | short circuit yap\u0131l\u0131yor.");\r\n await context.Response.WriteAsync("--- Short Circuit ---");\r\n });\r\n }\r\n.\r\n.\r\n.\r\n<\/pre>\n
Yukar\u0131daki kod blo\u011funu incelerseniz e\u011fer “Use” fonksiyonu i\u00e7erisinde “next.Invoke()” komutu ile bir sonraki middleware’i yani “Run” fonksiyonunu \u00e7a\u011f\u0131rmaktad\u0131r. “Run” fonksiyonunun i\u015flevi bitti\u011fi vakit compiler kald\u0131\u011f\u0131 noktaya geri d\u00f6n\u00fcp devam edecektir.<\/p>\n\n\n\n\n\n
\u00c7\u0131kt\u0131<\/th>\n Output<\/th>\n<\/tr>\n<\/thead>\n
$\"Asp.NET$ <\/a><\/td>\n $\"Asp.NET$ <\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
“Use” metoduyla ilgili bir ba\u015fka \u00f6rnek ele alal\u0131m;<\/p>\n
\r\n.\r\n.\r\n.\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n app.Use(async (context, next) =>\r\n {\r\n Debug.WriteLine("1. Middleware ba\u015flad\u0131.");\r\n await next.Invoke();\r\n Debug.WriteLine("1. Middleware sonland\u0131.");\r\n });\r\n\r\n app.Use(async (context, next) =>\r\n {\r\n Debug.WriteLine("2. Middleware ba\u015flad\u0131.");\r\n await next.Invoke();\r\n Debug.WriteLine("2. Middleware sonland\u0131.");\r\n });\r\n\r\n app.Use(async (context, next) =>\r\n {\r\n Debug.WriteLine("3. Middleware ba\u015flad\u0131.");\r\n await next.Invoke();\r\n Debug.WriteLine("3. Middleware sonland\u0131.");\r\n });\r\n }\r\n.\r\n.\r\n.\r\n<\/pre>\n
$\"Asp.NET$ <\/a><\/p>\n
Map Metodu<\/h3>\n
Bazen middleware’i talep g\u00f6nderilen path’e g\u00f6re filtrelemek isteyebiliriz. Bunun i\u00e7in “Use” ya da “Run” fonksiyonlar\u0131nda if kontrol\u00fc sa\u011flayabilir ya da “Map” metodu ile de bu i\u015flemi ger\u00e7ekle\u015ftirebiliriz.<\/p>\n
\r\n.\r\n.\r\n.\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n app.Use(async (context, next) =>\r\n {\r\n Debug.WriteLine("Use middleware tetiklendi.");\r\n await next.Invoke();\r\n });\r\n\r\n app.Map("\/example", internalApp =>\r\n internalApp.Run(async context =>\r\n {\r\n Debug.WriteLine("\/example middleware tetiklendi.");\r\n await context.Response.WriteAsync("\/example middleware tetiklendi.");\r\n }));\r\n }\r\n.\r\n.\r\n.\r\n<\/pre>\n
Yukar\u0131daki \u00f6rnek kod blo\u011funu incelerseniz e\u011fer “\/example” path’ine gelen talepler neticesinde “Map” fonksiyonunun ikinci parametresinde tan\u0131mlanan middleware devreye sokulacakt\u0131r.<\/p>\n\n\n\n\n\n\n
<\/th>\n Path : “\/”<\/th>\n Path : “\/example”<\/th>\n<\/tr>\n<\/thead>\n
Output<\/strong><\/td>\n $\"Asp.NET$ <\/a><\/td>\n $\"Asp.NET$ <\/a><\/td>\n<\/tr>\n
\u00c7\u0131kt\u0131<\/strong><\/td>\n $\"Asp.NET$ <\/a><\/td>\n $\"Asp.NET$ <\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
G\u00f6r\u00fcld\u00fc\u011f\u00fc \u00fczere middleware’in path’e \u00f6zel tetiklenmesini “Map” fonksiyonu sayesinde ger\u00e7ekle\u015ftirmi\u015f bulunmaktay\u0131z.<\/p>\n
MapWhen Metodu<\/h3>\n
“Map” metodu ile sadece requestin yap\u0131ld\u0131\u011f\u0131 path’e g\u00f6re filtreleme yap\u0131labilirken, “MapWhen” metodu ile ise herhangi bir \u015fart ile filtreleme i\u015flemi ger\u00e7ekle\u015ftirebiliriz.<\/p>\n
\r\n.\r\n.\r\n.\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n app.Use(async (context, next) =>\r\n {\r\n Debug.WriteLine("Use middleware tetiklendi.");\r\n await next.Invoke();\r\n });\r\n \r\n app.MapWhen(x => x.Request.Method == "GET", internalApp =>\r\n {\r\n internalApp.Run(async context => await context.Response.WriteAsync("MapWhen Middleware"));\r\n });\r\n }\r\n.\r\n.\r\n.\r\n<\/pre>\n
Yukar\u0131daki kod blo\u011funu incelerseniz e\u011fer “GET” tipinde olan t\u00fcm requestlerde bu middleware tetiklenecektir.<\/p>\n
\u00d6zel Extension Middleware Olu\u015fturma<\/h3>\n
\u0130lk olarak middleware g\u00f6revini g\u00f6recek s\u0131n\u0131f\u0131m\u0131z\u0131 in\u015fa edelim.<\/p>\n
\r\n public class HelloMiddleware\r\n {\r\n readonly RequestDelegate _next;\r\n public HelloMiddleware(RequestDelegate next)\r\n {\r\n _next = next;\r\n }\r\n public async Task Invoke(HttpContext context)\r\n {\r\n Debug.WriteLine("Hello 1");\r\n await _next.Invoke(context);\r\n Debug.WriteLine("Hello 2");\r\n }\r\n }\r\n<\/pre>\n
Ard\u0131ndan bu s\u0131n\u0131f\u0131 kullanan extension metodumuzu yazal\u0131m.<\/p>\n
\r\n static public class HelloMiddlewareExtension\r\n {\r\n public static IApplicationBuilder UseHello(this IApplicationBuilder builder)\r\n {\r\n return builder.UseMiddleware<HelloMiddleware>();\r\n }\r\n }\r\n<\/pre>\n
\u015eimdi ise olu\u015fturdu\u011fumuz middleware’i kullanal\u0131m.<\/p>\n
\r\n.\r\n.\r\n.\r\n public void Configure(IApplicationBuilder app, IHostingEnvironment env)\r\n {\r\n app.UseHello();\r\n\r\n app.Run(async context => await context.Response.WriteAsync("Run middleware"));\r\n }\r\n.\r\n.\r\n.\r\n<\/pre>\n\n\n\n\n\n
\u00c7\u0131kt\u0131<\/th>\n Output<\/th>\n<\/tr>\n<\/thead>\n
$\"Asp.NET$ <\/a><\/td>\n $\"Asp.NET$ <\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Evet, g\u00f6rd\u00fc\u011f\u00fcn\u00fcz gibi as\u0131l custom middleware’i bu \u015fekilde olu\u015fturmu\u015f bulunmaktay\u0131z.<\/p>\n
Okudu\u011funuz i\u00e7in te\u015fekk\u00fcr ederim.<\/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, Web yaz\u0131l\u0131mlar\u0131, genellikle kullan\u0131c\u0131larla etkile\u015fim a\u00e7\u0131s\u0131ndan olduk\u00e7a yo\u011fun bir yap\u0131 arz etmektedirler. Kullan\u0131c\u0131lar web sitesinden bir istekte bulunabilmekte ve bu iste\u011fe kar\u015f\u0131l\u0131k server taraf\u0131ndan uygun cevaplar \u00fcretilip g\u00f6nderilmektedir. Ve t\u00fcm s\u00fcre\u00e7 bu \u015fekilde...<\/p>\n","protected":false},"author":1,"featured_media":9596,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2668,2656],"tags":[2652,2674,2676,2667,2670,2672,2666,2673,2675,2523,2669,2665,2671],"class_list":["post-9671","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-asp-net-core-2","category-asp-net-core-2-mvc","tag-asp-net-core-2","tag-asp-net-core-2-map-function","tag-asp-net-core-2-mapwhen-function","tag-asp-net-core-2-middleware","tag-asp-net-core-2-run-function","tag-asp-net-core-2-use-function","tag-kisa-devre","tag-map-metodu","tag-mapwhen-metodu","tag-middleware","tag-run-metodu","tag-short-circuit","tag-use-metodu"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9671","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=9671"}],"version-history":[{"count":33,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9671\/revisions"}],"predecessor-version":[{"id":9715,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9671\/revisions\/9715"}],"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=9671"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=9671"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=9671"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}