<\/div>\n
Merhaba,<\/p>\n
Bu i\u00e7eri\u011fimizde Asp.NET Core 2 MVC’de migration yap\u0131s\u0131n\u0131n nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 inceleyece\u011fiz. \u0130lk olarak migration altyap\u0131s\u0131n\u0131n kurulumunu ger\u00e7ekle\u015ftirecek, ard\u0131ndan migration olu\u015fturacak, s\u00fcre\u00e7te migrationlar \u00fczerinde d\u00fczenleme i\u015flemleri ger\u00e7ekle\u015ftirecek ve t\u00fcm bu i\u015flemlerin neticesinde migration yap\u0131lar\u0131n\u0131n tetiklenmesi i\u00e7in komut sat\u0131r\u0131ndan veya \u00f6zel olarak tasarlayaca\u011f\u0131m\u0131z bir middleware \u00fczerinden olmak \u00fczere iki farkl\u0131 yoldan nas\u0131l \u00e7al\u0131\u015f\u0131laca\u011f\u0131n\u0131 inceleyece\u011fiz.<\/p>\n
\u015eimdi gelin hi\u00e7 vakit kaybetmeden altyap\u0131m\u0131z\u0131 olu\u015fturmayla ba\u015flayal\u0131m.<\/p>\n
Migration Altyap\u0131s\u0131n\u0131n Olu\u015fturulmas\u0131<\/h3>\n
Her\u015feyden \u00f6nce migration taraf\u0131ndan otomatik generate edilmesi i\u00e7in bir tablo temsil edecek olan entitymizi ve DbContext s\u0131n\u0131f\u0131m\u0131z\u0131 in\u015fa ederek i\u015fe ba\u015flayal\u0131m.<\/p>\n
\r\n    public class Employee\r\n    {\r\n        public int Id { get; set; }\r\n        public string Name { get; set; }\r\n        public string SurName { get; set; }\r\n        public int Age { get; set; }\r\n    }\r\n<\/pre>\n\r\n    public class DatabaseContext : DbContext\r\n    {\r\n        public DatabaseContext(DbContextOptions options)\r\n            : base(options)\r\n        { }\r\n        public DbSet<Employee> Employees { get; set; }\r\n    }\r\n<\/pre>\nOlu\u015fturdu\u011fumuz “DatabaseContext” s\u0131n\u0131f\u0131 bizim “DbContext” s\u0131n\u0131f\u0131m\u0131z olacakt\u0131r. Dolay\u0131s\u0131yla bu s\u0131n\u0131f tipinden olabilecek t\u00fcm taleplere kar\u015f\u0131l\u0131k bir nesne d\u00f6nd\u00fcrebilmek i\u00e7in “Startup” s\u0131n\u0131f\u0131n\u0131n “ConfigureServices” metodunda a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 ger\u00e7ekle\u015ftiriyoruz.<\/p>\n
\r\n.\r\n.\r\n.\r\n        public void ConfigureServices(IServiceCollection services)\r\n        {\r\n            #region DbContext\r\n            services.AddDbContext<DatabaseContext>(option => option.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")));\r\n            #endregion\r\n            services.AddMvc();\r\n        }\r\n.\r\n.\r\n.\r\n<\/pre>\nBurada dikkat ederseniz e\u011fer generic olan “AddDbContext” metodu sayesinde “DatabaseContext” s\u0131n\u0131f\u0131n\u0131n bir “DbContext” oldu\u011funu belirtmi\u015f bulunmaktay\u0131z ve veritaban\u0131 i\u015flemlerinde t\u00fcm taleplere kar\u015f\u0131l\u0131k ilgili s\u0131n\u0131ftan bir instance g\u00f6nderilmesine dair bildiride bulunmaktay\u0131z. Ayr\u0131ca g\u00f6nderilecek bu instance’da “UseSqlServer” fonksiyonu arac\u0131l\u0131\u011f\u0131yla Sql Server kullan\u0131laca\u011f\u0131 belirtilmekte ve server ba\u011flant\u0131s\u0131 “Configuration.GetConnectionString” komutu ile de “appsettings.json” dosyas\u0131nda “DefaultConnection” isminde kay\u0131tta tutulan provider ile sa\u011flanmas\u0131 s\u00f6ylenmektedir.<\/p>\n
“appsettings.json” dosyas\u0131; klasik Asp.NET mimarisindeki “web.config” dosyas\u0131na denk olan, Asp.NET Core ile d\u00fcnyam\u0131za giren bir dosyad\u0131r. Proje i\u00e7erisinde varsay\u0131lan olarak gelmeyen “appsettings.json” dosyas\u0131n\u0131 “App Settings File” isminde aratarak ismini de\u011fi\u015ftirmeksizin direkt olarak eklemeniz ilgili dosyay\u0131 projeye entegre etmeniz i\u00e7in yeterli olacakt\u0131r. “appsettings.json” dosyas\u0131n\u0131n i\u00e7eri\u011fide a\u015fa\u011f\u0131daki gibi olacakt\u0131r;<\/p>\n
\r\n{\r\n  "ConnectionStrings": {\r\n    "DefaultConnection": "Server=.;Database=ExampleDb;Trusted_Connection=True;Integrated Security=True;"\r\n  }\r\n}\r\n<\/pre>\nG\u00f6r\u00fcld\u00fc\u011f\u00fc gibi, “ConnectionStrings” \u00f6zelli\u011fi alt\u0131nda tan\u0131mlanan “DefaultConnection” \u00f6zelli\u011fi, o anda ba\u011flant\u0131 kuraca\u011f\u0131m\u0131z database bilgisinin provider\u0131n\u0131 tutmaktad\u0131r.<\/p>\n
Bu noktaya kadar yapt\u0131\u011f\u0131m\u0131z t\u00fcm \u00e7al\u0131\u015fma migration altyap\u0131s\u0131 i\u00e7in gerekli olan \u00e7o\u011fu hususu bar\u0131nd\u0131rmaktad\u0131r. \u015eimdi migration yap\u0131lar\u0131n\u0131 projeye entegre edebilmek i\u00e7in “Microsoft.EntityFrameworkCore.Tools.DotNet<\/em>” k\u00fct\u00fcphanesini projemize eklememiz gerekmektedir. Bu i\u015flem i\u00e7in projeye sa\u011f t\u0131klay\u0131p “Edit -ProjeAdi-.csproj” sekmesine t\u0131klay\u0131n\u0131z ve a\u015fa\u011f\u0131da oldu\u011fu gibi ilgili paketi ekleyiniz.<\/p>\n
\r\n<Project Sdk="Microsoft.NET.Sdk.Web">\r\n\r\n  <PropertyGroup>\r\n    <TargetFramework>netcoreapp2.1<\/TargetFramework>\r\n  <\/PropertyGroup>\r\n\r\n  <ItemGroup>\r\n    <Folder Include="Views\\Shared\\" \/>\r\n    <Folder Include="wwwroot\\" \/>\r\n  <\/ItemGroup>\r\n\r\n  <ItemGroup>\r\n    <PackageReference Include="Microsoft.AspNetCore.App" \/>\r\n    <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.1.1" \/>\r\n    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.3" \/>\r\n  <\/ItemGroup>\r\n\r\n<\/Project>\r\n<\/pre>\nE\u011fer ki, projeye entegre etmeye \u00e7al\u0131\u015ft\u0131\u011f\u0131m\u0131z paketin son versiyon bilgisini bilmiyorsan\u0131z \u015fu adresten<\/a> bak\u0131p teyit edebilirsiniz.<\/p>\n
Migration Olu\u015fturma\/Ekleme<\/h3>\nT\u00fcm bu i\u015flemleri yapt\u0131ktan sonra art\u0131k projemizde migrations yap\u0131lar\u0131n\u0131 olu\u015fturabiliriz. Bu i\u015flem i\u00e7in projenin dizininde komut sat\u0131r\u0131n\u0131 a\u00e7arak a\u015fa\u011f\u0131daki prototipte olan komutu yazman\u0131z yeterlidir.<\/p>\n\r\ndotnet ef migrations add [migration ad\u0131]\r\n<\/pre>\n<\/a>
\nBu i\u015flemi yapt\u0131ktan sonra projemize Solution Explorer penceresinden bakarsak e\u011fer “Migrations” isminde bir klas\u00f6r\u00fcn eklendi\u011fini g\u00f6rmekteyiz.
\n<\/a>
\n\u0130lgili klas\u00f6r i\u00e7erisinde ilk etapta biri migration bir di\u011feri ise “Startup” s\u0131n\u0131f\u0131nda DbContext olarak belirtti\u011fimiz s\u0131n\u0131f\u0131n Snapshot s\u0131n\u0131flar\u0131 gelmektedir. Bu s\u0131n\u0131flar i\u00e7erisine s\u0131ras\u0131yla g\u00f6z atarsak e\u011fer;<\/p>\n
\u0130lk olarak migration s\u0131n\u0131f\u0131m\u0131z\u0131 inceleyece\u011fiz;<\/p>\n
\r\n    public partial class initial : Migration\r\n    {\r\n        protected override void Up(MigrationBuilder migrationBuilder)\r\n        {\r\n            migrationBuilder.CreateTable(\r\n                name: "Employees",\r\n                columns: table => new\r\n                {\r\n                    Id = table.Column<int>(nullable: false)\r\n                        .Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),\r\n                    Name = table.Column<string>(nullable: true),\r\n                    SurName = table.Column<string>(nullable: true),\r\n                    Age = table.Column<int>(nullable: false)\r\n                },\r\n                constraints: table =>\r\n                {\r\n                    table.PrimaryKey("PK_Employees", x => x.Id);\r\n                });\r\n        }\r\n\r\n        protected override void Down(MigrationBuilder migrationBuilder)\r\n        {\r\n            migrationBuilder.DropTable(\r\n                name: "Employees");\r\n        }\r\n    }\r\n<\/pre>\nOlu\u015fturulan migration s\u0131n\u0131f\u0131nda sistem “Startup” s\u0131n\u0131f\u0131 i\u00e7erisinde tan\u0131mlanm\u0131\u015f “DbContext” s\u0131n\u0131f\u0131 i\u00e7erisinde “DbSet<T>” tipinde tablo olarak tan\u0131mlanm\u0131\u015f t\u00fcm s\u0131n\u0131flar\u0131 yakalamakta ve “Up” metodu i\u00e7erisinde generate etmektedir. Burada dikkat edilmesi gereken nokta “Up” metodu de\u011fi\u015fiklikleri uygulamak i\u00e7in kullan\u0131l\u0131rken, “Down” metodu ise yap\u0131lan t\u00fcm de\u011fi\u015fiklikleri geri almak i\u00e7in kullan\u0131lmaktad\u0131r.<\/p>\n
Snapshot s\u0131n\u0131f\u0131na g\u00f6z atarsak e\u011fer;<\/p>\n\r\n    [DbContext(typeof(DatabaseContext))]\r\n    partial class DatabaseContextModelSnapshot : ModelSnapshot\r\n    {\r\n        protected override void BuildModel(ModelBuilder modelBuilder)\r\n        {\r\n#pragma warning disable 612, 618\r\n            modelBuilder\r\n                .HasAnnotation("ProductVersion", "2.1.3-rtm-32065")\r\n                .HasAnnotation("Relational:MaxIdentifierLength", 128)\r\n                .HasAnnotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn);\r\n\r\n            modelBuilder.Entity("CoreMigrations.Models.Entities.Employee", b =>\r\n                {\r\n                    b.Property<int>("Id")\r\n                        .ValueGeneratedOnAdd()\r\n                        .HasAnnotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn);\r\n\r\n                    b.Property<int>("Age");\r\n\r\n                    b.Property<string>("Name");\r\n\r\n                    b.Property<string>("SurName");\r\n\r\n                    b.HasKey("Id");\r\n\r\n                    b.ToTable("Employees");\r\n                });\r\n#pragma warning restore 612, 618\r\n        }\r\n    }\r\n<\/pre>\nburada model ile ilgili t\u00fcm yap\u0131lar in\u015fa edilmektedir.<\/p>\nMigrationlar\u0131 Migrate Ederek Veritaban\u0131na Yans\u0131tmak<\/h3>\nEvet… T\u00fcm altyap\u0131m\u0131z\u0131 kurduk. Migrationlar\u0131m\u0131z\u0131 olu\u015fturduk. \u015eimdi olu\u015fturulan migrationlar\u0131 migrate ederek veritaban\u0131na yans\u0131tal\u0131m. Bu i\u015flem i\u00e7in biri komut sat\u0131r\u0131ndan bir di\u011feride programatik olmak \u00fczere iki farkl\u0131 yol mevcuttur. Bizler her iki yoluda inceleyece\u011fiz;<\/p>\n
\u0130lk olarak komut sat\u0131r\u0131nda migrate i\u015flemini g\u00f6relim.<\/p>\n
Projemizdeki migrationlar\u0131 migrate edebilmek i\u00e7in komut sat\u0131r\u0131ndan a\u015fa\u011f\u0131daki prototipte bulunan komutu \u00e7al\u0131\u015ft\u0131rmam\u0131z yeterlidir.<\/p>\n\r\ndotnet ef database update\r\n<\/pre>\n<\/a>
\nBu i\u015flemden sonra SQL Server’a g\u00f6z atarsak e\u011fer a\u015fa\u011f\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcnde oldu\u011fu gibi veritaban\u0131m\u0131z\u0131n olu\u015fturuldu\u011funu ve i\u00e7erisine ilgili tablonun eklendi\u011fini g\u00f6rece\u011fiz.
\n<\/a>
\nHatta dikkat ederseniz e\u011fer ilgili tablonun “Id” kolonuna otomatik bir \u015fekilde primary key constrainti eklenmekte ve belirtilen t\u00fcm ayarlar kolonlara yans\u0131t\u0131lmaktad\u0131r.<\/p>\n
Migrate i\u015fleminin programatik olarak ger\u00e7ekle\u015ftirilmesini istiyorsan\u0131z e\u011fer “Startup” s\u0131n\u0131f\u0131 i\u00e7erisindeki “Configure” isimli metotta a\u015fa\u011f\u0131daki \u00e7al\u0131\u015fmay\u0131 ger\u00e7ekle\u015ftirmemiz yeterli olacakt\u0131r.<\/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.UseMvcWithDefaultRoute();\r\n            app.UseStaticFiles();\r\n\r\n            using (var serviceScope = app.ApplicationServices.CreateScope())\r\n            {\r\n                \/\/Uygulaman\u0131n kulland\u0131\u011f\u0131 DatabaseContext s\u0131n\u0131f\u0131ndan bir \u00f6rnek al\u0131yoruz.\r\n                DatabaseContext context = serviceScope.ServiceProvider.GetRequiredService<DatabaseContext>();\r\n                \/\/DbContext'i migrate ediyoruz.\r\n                context.Database.Migrate();\r\n            }\r\n        }\r\n.\r\n.\r\n.\r\n<\/pre>\nKodumuzu bu \u015fekilde in\u015fa ettikten sonra projeyi derleyip \u00e7al\u0131\u015ft\u0131rman\u0131z ilgili migrationlar\u0131n migrate olmas\u0131 i\u00e7in yeterli olacak ve veritaban\u0131, tablolar vs. yap\u0131lar\u0131 olu\u015fturulup proje o \u015fekilde aya\u011fa kald\u0131r\u0131lacakt\u0131r.<\/p>\nEntity G\u00fcncelleme Durumlar\u0131<\/h3>\nMigration’\u0131n olu\u015fturdu\u011fu entity \u00fczerinde bir de\u011fi\u015fiklik meydana geldi\u011fi zaman ilgili de\u011fi\u015fikli\u011fi yakalayacak yeni bir migration eklemek en do\u011frusu olacakt\u0131r. \u00d6rne\u011fin; “Employee” s\u0131n\u0131f\u0131na “Date” propertysi ekleyerek de\u011fi\u015fiklik yapt\u0131\u011f\u0131m\u0131z\u0131 d\u00fc\u015f\u00fcnelim.<\/p>\n\r\n    public class Employee\r\n    {\r\n        public int Id { get; set; }\r\n        public string Name { get; set; }\r\n        public string SurName { get; set; }\r\n        public int Age { get; set; }\r\n\r\n        public DateTime Date { get; set; }\r\n    }\r\n<\/pre>\n\u015eimdi bu de\u011fi\u015fikli\u011fi yakalamas\u0131 i\u00e7in yeni bir migration olu\u015ftural\u0131m.
\n<\/a><\/p>\n
<\/a>
\nYukar\u0131daki ekran g\u00f6r\u00fcnt\u00fcs\u00fcne dikkat ederseniz olu\u015fturdu\u011fumuz migration ilgili klas\u00f6re eklenmi\u015ftir. \u0130\u00e7eri\u011fine g\u00f6z atarsak e\u011fer;<\/p>\n
\r\n    public partial class EmployeeAddDateProp : Migration\r\n    {\r\n        protected override void Up(MigrationBuilder migrationBuilder)\r\n        {\r\n            migrationBuilder.AddColumn<DateTime>(\r\n                name: "Date",\r\n                table: "Employees",\r\n                nullable: false,\r\n                defaultValue: new DateTime(1, 1, 1, 0, 0, 0, 0, DateTimeKind.Unspecified));\r\n        }\r\n\r\n        protected override void Down(MigrationBuilder migrationBuilder)\r\n        {\r\n            migrationBuilder.DropColumn(\r\n                name: "Date",\r\n                table: "Employees");\r\n        }\r\n    }\r\n<\/pre>\ng\u00f6rd\u00fc\u011f\u00fcn\u00fcz \u00fczere bu sefer “Employee” entitysindeki de\u011fi\u015fiklik yakalanm\u0131\u015ft\u0131r ve bir kolon ekleme i\u015flemi yap\u0131lmaktad\u0131r.<\/p>\n
\u015eimdi tek yapmam\u0131z gereken bu migration\u0131 ya komut sat\u0131r\u0131ndan ya da programatik olarak migrate etmemiz gerekmektedir. Bu i\u015flem i\u00e7in \u00f6nceki sat\u0131rlarda ele ald\u0131\u011f\u0131m\u0131z her iki y\u00f6ntemden birini uygularsan\u0131z veritaban\u0131na ilgili de\u011fi\u015fikli\u011fin yans\u0131t\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6receksiniz.<\/p>\n
Migrationlar\u0131 Geri Almak ya da Belirli Bir Migrationa Geri D\u00f6nmek<\/h3>\nMigrationlar\u0131 geri almak istiyorsan\u0131z tek yapman\u0131z gereken geri d\u00f6nmek istedi\u011finiz migration ad\u0131n\u0131 update komutunun sonuna a\u015fa\u011f\u0131daki gibi belirtmeniz gerekmektedir.<\/p>\n
\r\ndotnet ef database update [migration ad\u0131]\r\n<\/pre>\nBu kal\u0131pta komutu \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131zda aradaki t\u00fcm migration i\u015flemleri geri al\u0131nacak ve veritaban\u0131 belirtilen migration\u0131n ayarlar\u0131na g\u00f6re tasarlanacakt\u0131r.<\/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, Bu i\u00e7eri\u011fimizde Asp.NET Core 2 MVC’de migration yap\u0131s\u0131n\u0131n nas\u0131l kullan\u0131ld\u0131\u011f\u0131n\u0131 inceleyece\u011fiz. \u0130lk olarak migration altyap\u0131s\u0131n\u0131n kurulumunu ger\u00e7ekle\u015ftirecek, ard\u0131ndan migration olu\u015fturacak, s\u00fcre\u00e7te migrationlar \u00fczerinde d\u00fczenleme i\u015flemleri ger\u00e7ekle\u015ftirecek ve t\u00fcm bu i\u015flemlerin neticesinde migration yap\u0131lar\u0131n\u0131n...<\/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":[2664,2651,2663,990],"class_list":["post-9624","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-asp-net-core-2-mvc","tag-net-core","tag-asp-net-core-2-mvc","tag-asp-net-core-2-mvc-migrations","tag-migrations"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9624","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=9624"}],"version-history":[{"count":39,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9624\/revisions"}],"predecessor-version":[{"id":9669,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/9624\/revisions\/9669"}],"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=9624"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=9624"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=9624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}