I have an existing database with data loaded.
Desired End Result:
Radzen application with a SQL script (generated from Radzen data classes) to create a fresh database (with identical database schema as original) to use for User Acceptance Testing.
Current End Result:
After opening the Radzen generated code in Visual Studio, running add-migration and script-migration -i, the resulting script creates a database with many incorrect data types.
Just so we're on the same page, the original database I used to generate the Radzen application is different than the one the Radzen data classes define.
This is problematic for three reasons:
The original database and the Radzen data classes don't match.
Since I have data in my original database, I don't want to run any unnecessary scripts or migrations; the original database and the Radzen data classes should simply match.
Since this breaks Entity Framework Core Migrations, my other team members cannot perform their work or add new migrations until this is fixed.
Migrations are very important to my team because we use the Code First approach religiously. We have found that it makes everything database related much simpler for us, our DBAs and Production Support. Code First has saved us tens of thousands of dollars over the years. That is why it is very important for us to have the original database align with Radzen generated data classes.
In my email, I have included a SQL script that enumerates the differences.
Steps to Reproduce:
Please see script and video sent to support.