Snapshot location uisng Add-Migration -OutputDir with Release fodler

[generik0]

HI

Thanks for a cool package.
When i for a migration i like to use:

Add-Migration -OutputDir Migrations\Release2018_x -Context XzyMigrationDbContext -Project Xzy.Migrations -StartupProject Xzy.App -Name Add_Xxy

But this also means that the snapshot is in the Migrations\Release2018_x folder.
What do i do when i make the next release and the migrations shoud be in Migrations\Release2019_y release.
Will there be issues with the multiple shnapshots=?

Thanks again, Br Rik

[bricelam]

Feel free to move the file and change the namespace. The tool can usually find it and update it.

Don't add two snapshots. That will cause problems.

[generik0]

@bricelam
Thanks for your answer, i find that if i move, it creates a new one each time under the Migrations\Release2018x.

I have tried to move to root, i.e "Migrations" and then an add-migration just creates a new snapshot.

[ajcvickers]

@generik0 Can you please post a runnable project/solution that demonstrates the behavior you are seeing?

[generik0]

@ajcvickers

I think you guys can make this test yourselves. It shold be a part of you CI integration tests.
Please note, i do not believe i saw this behaviour on 2.1.1, only 2.1.2
Please note that the migrations are moved into a fodler as VS is not making design dependant on main cs.
Please note snapshot is moved to folder parent to ouptut dir.

Snapshot under release folder:

Snampshot moved and namespace changed:

Migrations run with Add-Migration -OutputDir Migrations\Release2018_Q2 -Context ContentMigrationDbContext -Project Migration -StartupProject Web.App -Name TestSnapshot

[generik0]

@ajcvickers I have made an example. You just need to run:
Add-Migration -outputdir Migrations/Release42 -Context TestDbContext -project EfCoreMultipleTransactionsSameDbContext -startupproject EfCoreMultipleTransactionsSameDbContext -Name Add_Test
And you will see there is an extra snapshot created.
EfCoreNewSnapshotCreated.zip

[ajcvickers]

@generik0 Yes, thank you. I was able to reproduce this previously, hence it is assigned as a bug and in a milestone.

[jasonliaocn]

Hi, is it possible to create multiple target? previously my database is SQL server and I already have some migration histories, now I may want to deploy it to MySQL but all I can do is to delete the SQL Server migrations folder and start from the beginning again.

if I can specify the output folder for example Migrations-MySQL and there will be a new ModelSnapShot for MySQL generated would be better.

so the structure could be:
Migrations
---MySQL
------20181101042215_Add_Test.cs
------20181101042215_Add_Test.Designer.cs
------TestDbContextModelSnapshot.cs
---SQLServer
------20181101042215_Add_Test.cs
------20181101042215_Add_Test.Designer.cs
------TestDbContextModelSnapshot.cs

then I can specify to UseSqlServer or UseMySql with the target Migrations.