forked from fluentmigrator/fluentmigrator
-
Notifications
You must be signed in to change notification settings - Fork 1
Home
TheCloudlessSky edited this page Feb 9, 2012
·
27 revisions
The primary goals of Ignite are to:
+ combine and optimize assets in production environments
+ allow to easily debug individual assets
+ process super-languages like LESS, SASS and CoffeeScript
+ serve JavaScript templateswith other assets (e.g. [Mustache](http://mustache.github.com/) and [Underscore.js Template]](http://underscorejs.org)
+ easily enable HTTP caching for packages
+ keep packages in memory rather than disk
Please read through the following links:
- Getting FluentMigrator
- How to create a Migration
- Fluent Interface
- Migration Runners
- Use inbuilt database functions when setting the default value
- Sql Server Specific Extensions
- Raw Sql Helper for inserting data
- Auto Reversing Migrations
- Resharper File Template
- Transaction Modes for the Migration Runner
- ApplicationContext: Passing parameters to Migrations
- Dealing with Multiple Database Types
- Filter migrations run based on Tags
- Enforce migration version numbering rules
- Create custom metadata for the VersionInfo table