dradovic
dradovic
It was a conscious choice when switching to v4.x (supporting .NET Core) to omit the command line tools. At the time, I asked on SO the following question: [Best practice...
I also want to mention that I personally never used that command line tool. Mig#'s API is really simple to use from any kind of app directly so why should...
I get and share your point about reinventing the wheel. I wouldn't want to multi-target the same console app. A .NET Core app should use the .NET Core configuration capabilities...
Please study the SO question referenced earlier in order to understand what might be wrong with packaging the command line tool in the same NuGet. Also, I have switched to...
Makes sense. I personally do not need this feature. So feel free to submit a PR.
I've been only using CascadeOnDelete so far so I have only implemented that. However, this should really be easy to implement as well. So feel free setup a PR.
You didn't missing anything. For short: this feature does not exist yet. When Mig# came into being, it was a pure migration fwk which assumed that a migration always know...
Yes. Support for this data type has not been added yet. A primary design goal for Mig# was to provide a framework that enables you to painlessly switch database platforms...
Feel free to issue a PR for this.
In the AsIdentity() Method it would useful to have parameters for MinValue, Start With and Increment
Yes. Would make sense. Feel free to issue a PR for this.