{"id":1709,"date":"2018-03-27T22:00:00","date_gmt":"2018-03-27T20:00:00","guid":{"rendered":"https:\/\/demo.sidekick.be\/itenium\/package-manager-console-ef-migrations\/"},"modified":"2025-11-28T13:31:47","modified_gmt":"2025-11-28T12:31:47","slug":"package-manager-console-ef-migrations","status":"publish","type":"post","link":"https:\/\/demo.sidekick.be\/itenium\/blog\/dev-setup\/package-manager-console-ef-migrations\/","title":{"rendered":"Package Manager Console Entity Framework 6 Migrations profile"},"content":{"rendered":"

Activating your Nuget_profile<\/h1>\n

When opening the Package Manager Console (PMC) in Visual Studio, the profile file is executed.<\/p>\n

%USERPROFILE%DocumentsWindowsPowerShellNuGet_profile.ps1\n<\/code><\/pre>\n
You can reload the NuGet_profile.ps1 file using . $profile<\/code> in the PMC.<\/p>\n
The following aliases allow you to install a package with just ip EntityFramework<\/code>:<\/p>\n
Set-Alias ip Install-Package\nSet-Alias unip Uninstall-Package\n<\/code><\/pre>\n
Provide most likely -Project parameter<\/h1>\n
There is (unfortunately) no way to configure the \u201cDefault project\u201d in the PMC. This workaround creates a Verb-RealNoun for each existing cmdlet and adds a short alias to these commands. Which project contains the migrations is by convention, as determined by $isLikelyDbContextProject<\/code>.<\/p>\n
# Execute commands against first ProjectName to end with one of these:\n$isLikelyDbContextProject = \".DataAccess\", \".Back\"\n\nfunction Get-DbContextProject {\n\treturn Get-Project -All |\n\t\tWhere-Object {\n\t\t\tif ($_.ProjectName.LastIndexOf(\".\") -gt -1) {\n\t\t\t\treturn $isLikelyDbContextProject -match $_.ProjectName.Substring($_.ProjectName.LastIndexOf(\".\"))\n\t\t\t} else {\n\t\t\t\treturn $false\n\t\t\t}\n\t\t} | Select -First 1\n}\n\nfunction Add-RealMigration($name = \"test\") {\n\t$project = Get-DbContextProject\n\tAdd-Migration $name -Project $project.ProjectName\n}\n\nSet-Alias am Add-RealMigration\n\n# Usage\nam AddedBlogTable\n<\/code><\/pre>\n
The entire list of aliases:<\/p>\n
Set-Alias em Enable-RealMigrations\nSet-Alias am Add-RealMigration\nSet-Alias ad Add-RealMigration\nSet-Alias ud Update-RealDatabase\nSet-Alias udv Update-RealDatabaseVerbosely\nSet-Alias gam Get-AppliedMigrations\nSet-Alias lm List-Migrations # List last $listMigrationsCount\nSet-Alias lam List-AllMigrations\n<\/code><\/pre>\n
\n
Updating the database using a numeric TargetMigration<\/h1>\n
Easily go back to a specific migration using ud -1<\/code> instead of<\/p>\n
Update-Database -TargetMigration:SecondLastMigrationName\n<\/code><\/pre>\n
Usage<\/h2>\n
# List last 5 migrations:\n# (aliased as List-Migrations or lm)\n$ Get-MigrationsTable | Select-Object -First 5 | Format-Table -AutoSize\n\nIndex Name                   Created          FullName  \n----- ----                   -------          --------  \n0     MatchShouldBePlayed    12\/24\/2016 16:25 201612241625590_MatchShouldBePlayed.cs  \n-1    MatchFormationComment  12\/24\/2016 14:34 201612241434105_MatchFormationComment.cs  \n-2    UserPasswordResetLinks 10\/23\/2016 18:53 201610231853333_UserPasswordResetLinks.cs  \n-3    ClubManagerTypes       09\/23\/2016 20:46 201609232046188_ClubManagerTypes.cs  \n-4    BlockMatchField        08\/18\/2016 21:40 201608182140266_BlockMatchField.cs  \n\n# Update database to ClubManagerTypes\n$ Update-RealDatabase -3 # Alias: ud -3\n\n# Update database to latest migration (MatchShouldBePlayed)\n$ Update-RealDatabase 0 # Alias: ud\n<\/code><\/pre>\n
Attention<\/strong>:
 This completely ignores whatever may be the last migration that was applied to the database. Having Update-RealDatabase -1<\/code> go back to the \u201clast applied<\/em> migration – 1\u201d instead of the current implementation \u201cgo to the second last migration added to the project\u201d, would require analysing Get-Migrations<\/code>, which would make the whole thing considerably slower. (FileSystem vs Sql query)<\/p>\n
Source<\/h2>\n
function Get-MigrationsTable {\n\t$project = Get-DbContextProject\n\t$projectPath = Split-Path -Path $project.FullName\n\n\t$migrations = Get-ChildItem \"$projectPathMigrations\" |\n\t\tWhere-Object { Test-MigrationName $_.Name } |\n\t\tSort-Object Name -Descending\n\n\treturn $migrations | ForEach-Object -Begin {$idx = 0} -Process {\n\t\t$withoutExt = $_.Name.Substring(0, $_.Name.LastIndexOf(\".\"))\n\t\t$migrationName = $withoutExt.Substring($withoutExt.IndexOf(\"_\") + 1)\n\t\t$dateStr = $_.Name.Substring(0, $_.Name.IndexOf(\"_\"))\n\t\t$date = [DateTime]::ParseExact($dateStr.Substring(0, 12), \"yyyyMMddHHmm\", $null)\n\n\t\t$_ | Select-Object -Property `\n\t\t\t@{l='Index';e={\"$idx\"}}, `\n\t\t\t@{l='Name'; e={$migrationName}}, `\n\t\t\t@{l='Created'; e={$date.ToString(\"g\")}}, `\n\t\t\t@{l='FullName'; e={$_.Name}}\n\n\t\t$idx -= 1\n\t}\n}\n\nfunction Update-RealDatabase([int]$targetMigration = 0) {\n\t$project = Get-DbContextProject\n\tif ($targetMigration -eq 0) {\n\t\t# Default: Update to latest migration\n\t\tUpdate-Database -Project $project.ProjectName\n\t} else {\n\t\t# With negative number: Go to x last created migration\n\t\t$migration = Get-MigrationsTable | Where-Object {$_.Index -eq $targetMigration}\n\t\techo \"Migrating to last migration $targetMigration => $($migration.name)\"\n\t\tUpdate-Database -Project $project.ProjectName -TargetMigration $migration.name\n\t}\n}\n\nfunction Test-MigrationName($fileName) {\n\treturn $fileName -match \"^(d[^.]+).(cs|vb)$\"\n}\n<\/code><\/pre>\n
\n
Open the Package Manager Console in Visual Studio<\/h1>\n
Menu: Tools > NuGet Package Manager > Package Manager Console
 Shortcut: Alt + T, N, O
 Custom shortcut: View.PackageManagerConsole<\/p>\n
Extras<\/h1>\n
Stuff that came into being during the making of this post<\/b><\/p>\n