Automatic migrations made easy with .NET Entity Framework(blog.appharbor.com)
blog.appharbor.com
Automatic migrations made easy with .NET Entity Framework
http://blog.appharbor.com/2012/04/24/automatic-migrations-with-entity-framework-4-3
6 comments
When was the last time you checked in on C# land? It's getting a lot better lately.
ASP.NET MVC with Razor, Nuget, and the JUnit/NUnit-like test framework in Visual Studio are all in that line of thought. For something Active Record-like, historically more mature--and somewhat less ponderous--alternatives to EF and LINQ2SQL include NHibernate (FluentNHibernate is nice) and other approaches like Simple.Data, PetaPoco, etc.
Oh yeah, migrations have been notably absent, although I've tried a few like FluentMigrations, which is nice but "out of process" enough that I find it terribly easy to neglect.
ASP.NET MVC with Razor, Nuget, and the JUnit/NUnit-like test framework in Visual Studio are all in that line of thought. For something Active Record-like, historically more mature--and somewhat less ponderous--alternatives to EF and LINQ2SQL include NHibernate (FluentNHibernate is nice) and other approaches like Simple.Data, PetaPoco, etc.
Oh yeah, migrations have been notably absent, although I've tried a few like FluentMigrations, which is nice but "out of process" enough that I find it terribly easy to neglect.
Thanks!, and don't forget to let us know if there's anything you think we could do better.
This looks very promising. I've created my own lightweight system for automatic schema alterations and I can't imagine going back to working without it.
This could pretty much be a drop-in replacement for what I've done. Nice.
This could pretty much be a drop-in replacement for what I've done. Nice.
Looking better every day.
I do have a question though. I'm a .Net guy who has only worked with self hosted systems and Azure and I've always wondered how the latency affects people who build serious system using the add-ons provided. I just can't imagine it performing well without knowing where exactly your RabbitMQ(CloudAMQP), MongoDB(MongoHQ), and Memcache type services are hosted. They could be sitting in the next rack to you or in a completely different part of the country (in theory).
I do have a question though. I'm a .Net guy who has only worked with self hosted systems and Azure and I've always wondered how the latency affects people who build serious system using the add-ons provided. I just can't imagine it performing well without knowing where exactly your RabbitMQ(CloudAMQP), MongoDB(MongoHQ), and Memcache type services are hosted. They could be sitting in the next rack to you or in a completely different part of the country (in theory).
We use FluentMigrator and it works amazingly.
AppHarbor, you guys are bringing this one step closer to existing; great job.