Blog ListLatest articles about Visual Studio, windows phone 7, Silverlight, SharePoint, WCF, .Net, Azure here.
This site collects many different feeds from blogs, newsgroups and other Visual Studio sites. We publish short excerpts from these postings or articles on the VisualStudioFeeds.com front page. The whole process is automated and we cannot review every single posting that is added to the site. We try to include quality blogs and sites only so that the signal/noise ratio should be good.
Get the latest visual studio news here.http://visualstudiofeeds.com/index.php?option=com_content&view=category&id=138&layout=blog&Itemid=53
Tue, 03 Mar 2015 18:46:24 +0000Joomla! 1.5 - Open Source Content Managementen-gbEF6.1.3 Beta 1 Availablehttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=42426:EF6.1.3%20Beta%201%20Available&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=42426:EF6.1.3%20Beta%201%20Available&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 Today we are making Beta 1 of the EF6.1.3 release available. This patch release contains only high priority bug fixes. What are the 6.1.3 release timelines? At this stage we are planning for our next release to be the RTM. This may change if we get additional reports of high priority bugs that we decide should be fixed in 6.1.3. We expect to ship the next release sometime next month but this may change if we decided to take additional changes. What’s in Beta 1? EF6.1.3 will just contain

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsThu, 12 Feb 2015 14:08:45 +0000EF6.1.2 RTM Availablehttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41799:EF6.1.2%20RTM%20Available&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41799:EF6.1.2%20RTM%20Available&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 Today we are pleased to announce the availability of EF6.1.2. This patch release includes a number of high priority bug fixes and some contributions from our community. What’s in EF6.1.2? EF6.1.2 is mostly about bug fixes, you can see a list of the fixes included in EF6.1.2 on our CodePlex site. We also accepted a couple of noteworthy changes from members of the community: Query cache parameters can be configured from the app/web.configuration file

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsMon, 22 Dec 2014 16:22:15 +0000EF7 - Priorities, Focus, and Initial Releasehttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41545:EF7%20-%20Priorities,%20Focus,%20and%20Initial%20Release&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41545:EF7%20-%20Priorities,%20Focus,%20and%20Initial%20Release&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 We all know, you don’t get to write software in a vacuum. Aside from the technical task we are trying to achieve there are things such as dependencies, stakeholders, release dates, etc. that impact the order and priority of tasks we do. In this post we wanted to share the top factors influencing the features and scenarios we focus on first. Where are we at? Up until recently we’ve been focused on validating our “New Platforms, New Data Stores” vision for EF7. This has meant building out a core framework, experimenting with patterns to support

data stores with different capabilities, and implementing providers to validate our work. In terms of data stores, we have experimented with SQL Server, SQLite, InMemory, Azure Table Storage, and Redis providers. We’ve also had discussions with other folks looking at DocumentDB, SQL Compact, and MongoDB providers. For platforms, we have targeted traditional .NET Framework applications (WPF, WinForms, Console, and ASP.NET 4), Phone/Store/Universal, and ASP.NET 5 (a.k.a ASP.NET vNext). The vision for EF7 is “a core framework that handles concepts common to most data stores with provider specific extensions that become available when you target a specific...(Read whole news on source site)

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsTue, 02 Dec 2014 16:17:50 +0000EF6.1.2 Beta 2 Availablehttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41347:EF6.1.2%20Beta%202%20Available&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41347:EF6.1.2%20Beta%202%20Available&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 Today we are making Beta 2 of the EF6.1.2 release available. This patch release contains bug fixes and some contributions from our community. When will EF6.1.2 RTM? We were originally planning to go straight to RTM from Beta 1. However, we ended up taking a number of important bug fixes after Beta 1 shipped and we decided that the churn in the code base warranted another pre-release before we RTM. The pre-releases are important because they allow our customers and provider/extension writers to report any issues before we ship the RTM release. Our plan

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsTue, 18 Nov 2014 10:15:28 +0000Visual Studio 2015 Preview and Entity Frameworkhttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41236:Visual%20Studio%202015%20Preview%20and%20Entity%20Framework&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41236:Visual%20Studio%202015%20Preview%20and%20Entity%20Framework&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 Today we are pleased to announce the availability of Visual Studio 2015 Preview. You can download it and read more about the release on the Visual Studio team blog. This post details the places that Entity Framework is included in Visual Studio 2015 Preview. Our team is concurrently working on two versions of Entity Framework, both of which are included in this preview. Entity Framework 6.1.2 (Beta 1) This release includes Beta 1 of Entity Framework 6.1.2 runtime and tooling. EF6.1.2 includes a number bug fixes and community contributions, you can see

a list of the changes included in EF6.1.2 on our CodePlex site. The Entity Framework 6.1.2 runtime is included in a number of places in this release. The runtime will be installed if you create a new model using the Entity Framework Tools in a project that does not already have the EF runtime installed. The runtime is pre-installed in new ASP.NET projects, depending on the project template you select. If you encounter any issues using this beta of the 6.1.2 release be sure to

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsWed, 12 Nov 2014 09:15:41 +0000EF7 – v1 or v7?http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41029:EF7%20–%20v1%20or%20v7?&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=41029:EF7%20–%20v1%20or%20v7?&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 A while ago we blogged about EF7 targeting new platforms and new data stores. In that post we shared that our EF6.x code base wasn’t setup to achieve what we wanted to in EF7, and that EF7 would be a “lightweight and extensible version of EF”.
That begs the question, is EF7 the next version of EF, or is it something new? Before we dig into the answer, let’s cover exactly what’s the same and what’s changing.
What’s staying the same?
When it comes to writing code, most of the top level experience is staying the same in EF7.
You still create a

class that derives from DbContext and has DbSet properties for each type in your model.
You still use LINQ to write queries against your DbSet properties.
You still Add and Remove instances of types from your DbSet properties.
There are still DbContext.ChangeTracker and DbContext.Database properties for accessing change tracking information and database related APIs.
An example
For example, this code looks exactly the same in EF6.x and EF7.
using (var db = new BloggingContext()){ db.Blogs.Add(new Blog { Url = "blogs.msdn.com/adonet" }); db.SaveChanges();

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsMon, 27 Oct 2014 16:15:24 +0000EF7 - What Does “Code First Only” Really Meanhttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=40955:EF7%20-%20What%20Does%20“Code%20First%20Only”%20Really%20Mean&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=40955:EF7%20-%20What%20Does%20“Code%20First%20Only”%20Really%20Mean&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 A while back we blogged about our plans to make EF7 a lightweight and extensible version of EF that enables new platforms and new data stores. We also talked about our EF7 plans in the Entity Framework session at TechEd North America. Prior to EF7 there are two ways to store models, in the xml-based EDMX file format or in code. Starting with EF7 we will be retiring the EDMX format and having a single code-based format for models. A number of folks have raised concerns around this move and most of it stems from misunderstanding about

what a statement like “EF7 will only support Code First” really means. Code First is a bad name Prior to EF4.1 we supported the Database First and Model First workflows. Both of these use the EF Designer to provide a boxes-and-lines representation of a model that is stored in an xml-based .edmx file. Database First reverse engineers a model from an existing database and Model First generates a database from a model created in the EF Designer. In EF4.1 we introduced Code First. Understandably, based on the name, most folks think of Code First as...(Read whole news on source site)

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsTue, 21 Oct 2014 13:00:24 +0000EF6.1.2 Beta 1 Availablehttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=40476:EF6.1.2%20Beta%201%20Available&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=40476:EF6.1.2%20Beta%201%20Available&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 Today we are making Beta 1 of the EF6.1.2 release available. This patch release contains bug fixes and some contributions from our community. What’s in Beta 1? EF6.1.2 is mostly about bug fixes, you can see a list of the fixes included in EF6.1.2 on our CodePlex site. We also accepted a couple of noteworthy changes from members of the community: Query cache parameters can be configured from the app/web.configuration file

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsThu, 18 Sep 2014 15:41:28 +0000Visual Studio “14” CTP 3 and Entity Frameworkhttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=40026:Visual%20Studio%20“14”%20CTP%203%20and%20Entity%20Framework&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=40026:Visual%20Studio%20“14”%20CTP%203%20and%20Entity%20Framework&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 Today we’re providing a third CTP of the next version of Visual Studio, to gather your early feedback. For more information on this release, see Visual Studio “14” CTPs and the Visual Studio Blog. This post covers the places that Entity Framework is included in the release and some limitations to be aware of when using it. Entity Framework Tools There is a bug in the version of the designer included in this CTP that will cause a ‘Method not found’ error to appear when trying to use the EF Tools. There is

no workaround for this error and it prevents the tools from being used. We are working to make a version of the Entity Framework 6.1.1 tools available that can be installed on Visual Studio “14” CTP3. We will update this post with details once the installer is available. Entity Framework 6.x Runtime The Entity Framework 6.1.1 runtime is included in a number of places in Visual Studio “14” CTP. The runtime will be installed if you create a new model using the Entity Framework Tools in a project that does not...(Read whole news on source site)

]]>admin@visualstudiofeeds.com (Administrator)ADO.NET team blog - Site Home - MSDN BlogsMon, 18 Aug 2014 11:25:25 +0000VS2013 Update 3 and Entity Frameworkhttp://visualstudiofeeds.com/index.php?option=com_content&view=article&id=39831:VS2013%20Update%203%20and%20Entity%20Framework&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53
http://visualstudiofeeds.com/index.php?option=com_content&view=article&id=39831:VS2013%20Update%203%20and%20Entity%20Framework&catid=138:adonetteamblog-sitehome-msdnblogs&Itemid=53 Today we are releasing Visual Studio 2013 Update 3. You can read the release announcements by Soma and Brian Harry. This update includes the Entity Framework 6.1.1 (EF6.1.1) runtime and tooling. EF6.1.1 was previously released out-of-band about 6 weeks ago, so you may have already installed the update to Entity Framework. If not, it will be automatically installed when you install Visual Studio 2013 Update 3. How do I get Update 3? You can download Visual Studio 2013 Update 3. Note that installing the update will not affect the

version of the Entity Framework runtime included in existing projects. We recommend using NuGet to update to the latest version of the runtime. For detailed information on how to upgrade, see Updating a Package in the NuGet documentation.