Simple.Migrations | Simple but powerful migrations library for .NET Core
kandi X-RAY | Simple.Migrations Summary
kandi X-RAY | Simple.Migrations Summary
Simple.Migrations is a C# library. Simple.Migrations has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.
Simple.Migrations is a simple bare-bones migration framework for .NET Core (.NET Standard 1.2 and .NET 4.5). It doesn’t provide SQL generation, or an out-of-the-box command-line tool, or other fancy features. It does however provide a set of simple, extendable, and composable tools for integrating migrations into your application. WARNING: Until Simple.Migrations reaches version 1.0, I reserve the right to make minor backwards-incompatible changes to the API. API breakages are documented in [the CHANGELOG] CHANGELOG.md).
Simple.Migrations is a simple bare-bones migration framework for .NET Core (.NET Standard 1.2 and .NET 4.5). It doesn’t provide SQL generation, or an out-of-the-box command-line tool, or other fancy features. It does however provide a set of simple, extendable, and composable tools for integrating migrations into your application. WARNING: Until Simple.Migrations reaches version 1.0, I reserve the right to make minor backwards-incompatible changes to the API. API breakages are documented in [the CHANGELOG] CHANGELOG.md).
Support
Quality
Security
License
Reuse
Support
Simple.Migrations has a low active ecosystem.
It has 209 star(s) with 22 fork(s). There are 7 watchers for this library.
It had no major release in the last 6 months.
There are 4 open issues and 22 have been closed. On average issues are closed in 74 days. There are 2 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of Simple.Migrations is current.
Quality
Simple.Migrations has 0 bugs and 0 code smells.
Security
Simple.Migrations has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
Simple.Migrations code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
Simple.Migrations is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
Simple.Migrations releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Simple.Migrations
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Simple.Migrations
Simple.Migrations Key Features
No Key Features are available at this moment for Simple.Migrations.
Simple.Migrations Examples and Code Snippets
No Code Snippets are available at this moment for Simple.Migrations.
Community Discussions
No Community Discussions are available at this moment for Simple.Migrations.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install Simple.Migrations
[Simple.Migrations is available on NuGet](https://www.nuget.org/packages/Simple.Migrations).
Go to Tools → Options → Debugger → General.
Uncheck "Enable Just My Code (Managed only)".
Uncheck "Enable .NET Framework source stepping". Yes, it is misleading, but if you don’t, then Visual Studio will ignore your custom server order (see further on) and only use it’s own servers.
Check "Enable source server support".
Uncheck "Require source files to exactly match the original version"
Go to Tools → Options → Debugger → Symbols.
Select a folder for the local symbol/source cache. You may experience silent failures in getting symbols if it doesn’t exist or is read-only for some reason.
Add http://srv.symbolsource.org/pdb/Public under "Symbol file (.pdb) locations".
I’ll introduce SimpleMigrator by walking through a basic example. Here, we’ll create a separate console application, which contains all of our migrations and can be invoked in order to migrate the database between different versions. If you want your application to automatically migrate to the latest version when it’s started, or you want to put your migrations in another library, etc, that’s easy too: we’ll get on to those [a bit later](#finding-migrations). First, create a new Console Application. The first task is to create (at least one) migration. Migrations are classes which derive from Migration, and are decorated with the [Migration(versionNumber)] attribute. How you number your migrations is up to you: some people like to number them sequentially, while others like to use the current date and time (e.g. 20150105164402). You can also provide a description, which will be printed by the default logger.
There are Up and Down methods, which are overriden from Migration. These are invoked when the migration should be applied (Up) or reverted (Down). The Down method should undo the changes made by the Up method.
There’s an Execute method, which is inherited from Migration, which you call to execute SQL.
Go to Tools → Options → Debugger → General.
Uncheck "Enable Just My Code (Managed only)".
Uncheck "Enable .NET Framework source stepping". Yes, it is misleading, but if you don’t, then Visual Studio will ignore your custom server order (see further on) and only use it’s own servers.
Check "Enable source server support".
Uncheck "Require source files to exactly match the original version"
Go to Tools → Options → Debugger → Symbols.
Select a folder for the local symbol/source cache. You may experience silent failures in getting symbols if it doesn’t exist or is read-only for some reason.
Add http://srv.symbolsource.org/pdb/Public under "Symbol file (.pdb) locations".
I’ll introduce SimpleMigrator by walking through a basic example. Here, we’ll create a separate console application, which contains all of our migrations and can be invoked in order to migrate the database between different versions. If you want your application to automatically migrate to the latest version when it’s started, or you want to put your migrations in another library, etc, that’s easy too: we’ll get on to those [a bit later](#finding-migrations). First, create a new Console Application. The first task is to create (at least one) migration. Migrations are classes which derive from Migration, and are decorated with the [Migration(versionNumber)] attribute. How you number your migrations is up to you: some people like to number them sequentially, while others like to use the current date and time (e.g. 20150105164402). You can also provide a description, which will be printed by the default logger.
There are Up and Down methods, which are overriden from Migration. These are invoked when the migration should be applied (Up) or reverted (Down). The Down method should undo the changes made by the Up method.
There’s an Execute method, which is inherited from Migration, which you call to execute SQL.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
