Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Microsoft ASP.NET Universal Providers 1.1 were released yesterday together with System.Web.Providers 1.2. On latter nuget page states: Legacy package, System.Web.Providers is now included in the 'Microsoft.AspNet.Providers' package.
Is this only name change or something more interesting/important? Should I remove System.Web.Providers 1.2 package reference if I have Microsoft.AspNet.Providers 1.1 and Microsoft.AspNet.Providers.Core 1.0 referenced?
You nailed it when you quoted, “Legacy package, System.Web.Providers is now included in the ‘Microsoft.AspNet.Providers’ package.” You can remove System.Web.Providers and just use the other two packages.
I read the original post by Scott Hanselman and compared it to the description for the “new” Microsoft.AspNet.Providers 1.1. They both say that this package of providers is the same except it supports SQL Azure and SQL Compact edition.