Documentation : Documentation Update Required for EF Migration Steps

[TLeoDev]

Expected Behavior

The documentation should guide users through the Entity Framework (EF) migration process in a way that the steps can be executed smoothly and without errors.

Current Behavior

Currently, the documentation's sequence for EF migration leads to potential issues. The steps mentioned for applying migration changes for PostgreSQL and MySQL are out of order. The necessary adjustments in the migration file (as detailed in step 4) need to be performed before executing the MySQL migration command.

Steps to Reproduce

1. Follow the documentation steps for EF migration.
2. Notice that executing the command for MySQL migration (dotnet ef migrations add "<nameofyourmigration>" -p ..\IoTHub.Portal.MySql\ -v -- --DbProvider MySQL) fails if the adjustments in step 4 are not done beforehand.

Context (Environment)

Portal version: [e.g., 1.0.2]
LoRaWAN Stack version: [e.g., 2.0.0]

Suggested Changes

The documentation should be updated to reflect the following order:

1. Go into the Server project folder with terminal:

cd .\IoTHub.Portal.Server\

1. Execute the command for PostgreSQL provider:

dotnet ef migrations add "<nameofyourmigration>" -p ..\IoTHub.Portal.Postgres\ -v -- --DbProvider PostgreSQL

1. Open the created migration and adjust as follows:

   a) Move the using directive into the namespace directive.
   b) Add "_ =" before each statement of the Up and Down methods.
   c) Add the CGI copyright to the top of the file.

2. Execute the command for MySQL provider (only after the above adjustments):

dotnet ef migrations add "<nameofyourmigration>" -p ..\IoTHub.Portal.MySql\ -v -- --DbProvider MySQL

1. Open the newly created migration for MySQL and repeat step 3.