So before I begin the fight to get EF migrations working in a production docker environment I thought I'd ask to see if there are any recommendations on doing this:
My scenario is docker images are built by my CI (GitLab) pushed to our docker registry and then automatically deployed to a "Dev" environment. The docker image simply runs Web.Host which of course when it starts complains that the database is not initialised. Since the "Dev" environment is not easy accessible it makes it hard to run the initial database migrations and the Migrator project to add the initial data.
Do you have any recommendations around around this?
Guys, still having issues with this. I downloaded the latest version today, no sign of the PackageTargetFallback tag in the projects and adding it doesn't appear to fix things.
Changing TargetFrameworks to <TargetFrameworks>net461;netcoreapp1.1</TargetFrameworks> seems to help but gives different errors.
Is it realistic to be able to use with Visual Studio for Mac (now on stable release)?
So I downloaded the new .NET core version with the following settings:
Project Type: ASP.NET CORE & Angular Project Version: 4.0.0 Framework: .NET Core 1.1
I tried to open with Visual Studio for Mac and got the following:
Errors in Core.csproj Package Abp.Zero.Ldap 2.0.1 is not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1). Package Abp.Zero.Ldap 2.0.1 supports: net46 (.NETFramework,Version=v4.6) One or more packages are incompatible with .NETCoreApp,Version=v1.1.
Which prevents anything from building.
So I tried on regular Visual Studio on Windows and got:
Package Microsoft.Composition 1.0.27 is not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1). Package Microsoft.Composition 1.0.27 supports: portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)
Which has the same effect.
I note that you warn on the download about LDAP and SignalR being unsupported however not sure how to get around these issues.