From e687a05fcc646b5fb29af007114231fa214b1406 Mon Sep 17 00:00:00 2001 From: Arthur Vickers Date: Wed, 17 Nov 2021 15:23:58 +0000 Subject: [PATCH] Update daily builds for EF7 --- docs/DailyBuilds.md | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/docs/DailyBuilds.md b/docs/DailyBuilds.md index a6fcdfa7d79..682ba44beb3 100644 --- a/docs/DailyBuilds.md +++ b/docs/DailyBuilds.md @@ -8,7 +8,7 @@ Create a file called "NuGet.config" with the following contents and put it next - + @@ -18,7 +18,7 @@ Continue reading for full details and troubleshooting. ## Types of builds -Daily builds are created automatically whenever a new commit is merged to the `main` branch. These builds are verified by more than 70,000 tests each running on a range of platforms. These builds are reliable and have significant advantages over using previews: +Daily builds are created automatically whenever a new commit is merged to the `main` branch. These builds are verified by more than 80,000 tests each running on a range of platforms. These builds are reliable and have significant advantages over using previews: * Previews typically lag behind daily builds by around three to five weeks. This means that each preview is missing many bug fixes and enhancements, even if you get it on the day it is released. The daily builds always have the latest features and bug fixes. * Serious bugs are usually fixed and available in a new daily build within one or two days--sometimes less. The same fix will likely not make a new preview/release for weeks. @@ -30,13 +30,13 @@ A disadvantage of using daily builds is that there can be significant API churn The daily builds are not published to NuGet.org because the .NET build infrastructure is not set up for this. Instead they can be pulled from a custom NuGet package source. To access this custom source, create a `NuGet.config` file in the same directory as your .NET solution or projects. -For EF Core 6.0 daily builds, `NuGet.config` should contain: +For EF7 daily builds, `NuGet.config` should contain: ```xml - + @@ -50,10 +50,10 @@ The easiest way to use daily builds is with wildcards in project references. For ```xml - - - - + + + + ``` @@ -71,11 +71,10 @@ Alternately, your IDE might provide auto-completion directly in the .csproj file ## What about Visual Studio and the SDK? -EF Core 6.0 targets .NET 6. This means that: +EF7 currently targets .NET 6. This means that: -* Your application must target .NET 6 or later; .NET Core 3.1 or .NET 5.0 are not longer supported targets. +* Your application must target .NET 6 or later; .NET Framework, .NET Core 3.1, and .NET 5 are no longer supported targets. * The daily builds should work with any IDE that supports .NET 6. - * They do require a Visual Studio 2022 preview release. * The daily builds require that the .NET 6 SDK is installed. ## Troubleshooting @@ -93,7 +92,7 @@ In addition, packages may be missing if the standard `nuget.org` package source - + @@ -109,7 +108,7 @@ A good way to ensure you're dealing with a completely clean NuGet configuration - +