Browse Source

Cli Module adding: Fix migration commands

Resolves https://github.com/volosoft/volo/issues/9728
pull/12226/head
Yunus Emre Kalkan 4 years ago
parent
commit
dc45d64ec8
  1. 5
      framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/ProjectModification/EfCoreMigrationManager.cs
  2. 2
      framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/ProjectModification/SolutionModuleAdder.cs

5
framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/ProjectModification/EfCoreMigrationManager.cs

@ -48,9 +48,10 @@ public class EfCoreMigrationManager : ITransientDependency
? string.Empty
: $"--context {dbContext}";
CmdHelper.RunCmd($"cd \"{dbMigrationsProjectFolder}\" && dotnet ef migrations add {migrationName}" +
CmdHelper.RunCmd($"dotnet ef migrations add {migrationName}" +
$" --output-dir {outputDirectory}" +
$" {dbContextOption}");
$" {dbContextOption}",
workingDirectory: dbMigrationsProjectFolder);
}
protected virtual string ParseModuleName(string fullModuleName)

2
framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/ProjectModification/SolutionModuleAdder.cs

@ -679,7 +679,7 @@ public class SolutionModuleAdder : ITransientDependency
if (!string.IsNullOrEmpty(dbMigratorProject))
{
CmdHelper.RunCmd("cd \"" + Path.GetDirectoryName(dbMigratorProject) + "\" && dotnet run", out int exitCode);
CmdHelper.RunCmd($"dotnet run", out int exitCode, workingDirectory: Path.GetDirectoryName(dbMigratorProject));
}
}

Loading…
Cancel
Save