4 ms·
MVC3 has always been extensible enough so you could add most of the major new features in the MVC4 roadmap. The "extra mile" polish you would normally add to MV
by edandersen 15y ago
MVC3 has always been extensible enough so you could add most of the major new features in the MVC4 roadmap. The "extra mile" polish you would normally add to MVC3 applications look like they will be in MVC4 as standard:
* jQuery Mobile templates
* Mobile/Desktop view switch API
* EF Code First DB Migrations (finally, without having to rely on third party libraries such as MigratorDotNet)
* Built-in JavaScript and CSS minimization
Can't wait!
- smhinsey 15y agoI wonder if this is going to push the NH guys to do an official migrations package. You can already come pretty close to it just using the schema migration APIs, so they have a lot of the pieces. I'd love to see some competition in what I think is historically an under-addressed part of development on any given Microsoft stack.
- traskjd 15y agoOur LightSpeed ORM product does schema migrations between a whole pile of databases and includes Visual Studio 2008 & 2010 integration for seeing the migrations, executing them, generating the SQL files etc. I haven't seen anyone else really pushing Migrations that hard yet in the .NET space. Would be nice to see others trying to improve this space.
- smhinsey 15y agoInteresting, I've never heard of LightSpeed. I'll be honest that I have a near-zero level of trust for this type of software from vendors in the .NET space, but I'll definitely give it a look.
- skeletonjelly 15y ago> * EF Code First DB Migrations Orchard has this using NHibernate. Being unfamiliar with EF and NH though (long time LLBLGen user here) is this what you mean?
- Michiel 15y ago"finally, without having to rely on third party libraries such as MigratorDotNet" Yes, heaven forbid we .NET developers should rely on third party libraries...