Evolve.EraseOnValidationErroroption is provided specifically for this use case.
Yes! Evolve will use the session level lock of your database to coordinate the migrations on multiple nodes. This prevents two distinct Evolve executions from running an Evolve command on the same database at the same time.
Yes! The option
Evolve.ConnectionString can also be the name of a key in a connectionStrings section of your config file.
Yes! Use this syntax for your environment variables:
evolve.jsonfile in your solution.
<appSettings>or let the