Releasing Microsoft ASP.NET Universal Providers Core 1.2

Releasing Microsoft ASP.NET Universal Providers Core 1.2

  • Comments 2

I hope everyone has been busy downloading Visual Studio 2012 and have started building awesome web applications. We have been busy too during this time.

We have just released an update to the version of Universal Providers that shipped with VS2012. Following are the key changes with this release

  • Address key performance issues with the providers
  • Depends on EntityFramework Code First


What should you do

This version of Universal Providers Core that shipped with VS2012 was 1.1. Take a moment and update to 1.2

You can follow this documentation on  how to update a nuget package.

While updating you will get the EntityFramework 5.0.0 package as well from the

Some common FAQ

  • Works on .NET v4.0/4.5
  • Works on VS2010/VS2012
  • 1.2 is compatible with 1.1

Please do reach out to us on the following forum channels for any questions on universal providers

All the best building awesome applications.

Cross posted to

Leave a Comment
  • Please add 6 and 5 and type the answer here:
  • Post
  • Yikes, guys.... we were looking at using the Universal Providers for membership and role support, but we already are committed to using NHibernate for a lot of our DA needs, so a dependency on the Entity Framework is unwelcome.  So much so that we aren't going to be able to use this.

  • In order for us to write providers that were able to support a variety of database types (SQL, SQL Azure, SQL Compact or any database supported by EF) we needed to build on top of an abstraction that abstracted away the database type and the natural one for us to use is Entity Framework. If you search for nHibernate and ASP.NET providers you find quite a few solutions that target nHibernate, I would suggest you try one of them. is one I found.

Page 1 of 1 (2 items)