"Done" message was shown when running dotnet ef migrations script

[ghost]

I'm working on ef migrations in web tool side. I use dotnet ef migrations script to generate T-SQL file of migrations. When this command is done, it will show a "Done" on screen, whose the code is from src/dotnet-ef/MigrationsScriptCommand.cs (line 74 Reporter.Error.WriteLine("Done");) . This "Done" should not be handled by "Reporter.Error".

When I run the whole thing by msbuild tasks, the "Done" will be captured by msbuild.exe and it was recognized an error message. This makes people think this command has a problem and actually it is not.

Is there an option not showing "Done" on screen or some other approach to skip "Done" ?

[natemcmaster]

Fixed via #5020. More work on how we log needs to be done. See #4771

[smitpatel]

I am using Entity Framework .NET Core CLI Commands 1.0.0-rc3-20747 and still hitting this issue.

dotnet : Done. To undo this action, use 'ef migrations remove'
At line:1 char:1
+ dotnet ef migrations add Init
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Done. To undo t...rations remove':String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

[smitpatel]

not just for done for any other message also same error

dotnet : An operation was scaffolded that may result in the loss of data. Please review the migration for accuracy.
At line:1 char:1
+ dotnet ef migrations add StringLength
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (An operation wa...n for accuracy.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

Done. To undo this action, use 'ef migrations remove'

[divega]

Reopening for now based on @smitpatel's findings.

[natemcmaster]

Possible duplicate of #4771

[smitpatel]

I was using powershell but cli commands.

[natemcmaster]

I've proposed 2 changes in #5542 that will help with this and related scripting errors:

1. dotnet ef will only use stderr for actual error messages.
2. Commands with json output --json will now also have --json-delimited. This will additionally spit out '//BEGIN' and '//END' for those so those building scripting on top of ef commands and who need to ensure they get only JSON as they parse its output.

cc @mlorbetske