dotnet / dotnet/EntityFramework.Docs

Documentation for `EFMigrations` msbuild target

Abierto
#2,829 2 comentarios 0 reacciones 0 asignados Ver en GitHub
area-migrations
Lenguaje dominante
Mermaid
Estrellas
1.7k
Forks
2k
Merge medio
7 d 23 h
PR fusionados (30 d)
16

Descripción

## Ask a question

I've been scouring the web trying to figure out how to get our migration script to be generated automatically as part of `dotnet publish`. Lots of old articles regarding including a migrate.exe... ick

I enabled diagnostic output on a dotnet-publish invocation and lo-and-behold, there's already an EFMigrations task!!!

But I can't seem to find any documentation for how to configure it, or how to ensure the file is included in the publish directory.

We're using dotnet core and publishing on macs and ubuntu (GitHub Actions), so the (very few) posts I've seen regarding configuring a pub.xml don't seem to apply (VS4mac doesn't seem to support customized publish profiles?)

Regardless, what I'm looking for is hopefully some documentation around how to use this task in our msbuild configuration such that it runs during publish, and is included in the final /publish directory.

I'd also be grateful if anyone just linked to the source of Task Class itself that backs this msbuild target...

So far, I've just blindly stumbled my way to adding:

```

```

to our .csproj file. And that has gotten us to:

```
_GenerateEFSQLScripts:
Generating Entity framework SQL Scripts...
Executing command: dotnet ef migrations script --idempotent --output "/Users/jasonkarns//obj/Release/netcoreapp3.1/win-x64/PubTmp/EFSQLScripts/FisContext.sql" --context FisContext
Generating Entity framework SQL Scripts completed successfully
```

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza con el ejemplo de EFMigrations de .csproj y la salida de _GenerateEFSQLScripts de dotnet publish. Rastrea el código fuente de la tarea de MSBuild EFMigrations y documenta la configuración necesaria para ejecutarla durante la publicación e incluir el archivo SQL generado en el directorio final /publish.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Área
build-system, documentation
Tipo de issue
Documentación
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.