From 213f54fe9a82de6a6581691c4dcd6a607ca086db Mon Sep 17 00:00:00 2001 From: Shad Storhaug Date: Mon, 1 Feb 2021 05:46:39 +0700 Subject: [PATCH] Updated README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ad9930d669..0e4902fb3b 100644 --- a/README.md +++ b/README.md @@ -243,7 +243,7 @@ Then all you need to do is choose the `Lucene.Net Local Packages` feed from the #### Execution 1. Open `Lucene.Net.sln` in Visual Studio. -2. Choose the target framework to test by opening `build/TestTargetFramework.proj` and uncommenting the corresponding ``. +2. Choose the target framework to test by opening `build/TestTargetFramework.props` and uncommenting the corresponding `` (and commenting all others). 3. Build a project or the entire solution, and wait for Visual Studio to discover the tests - this may take several minutes. 4. Run or debug the tests in Test Explorer, optionally using the desired filters. @@ -251,7 +251,7 @@ Then all you need to do is choose the `Lucene.Net Local Packages` feed from the ### Azure DevOps -We have setup our `azure-pipelines.yml` file with logical defaults so anyone with an Azure DevOps account can build Lucene.Net and run the tests with minimal effort. Even a free Azure DevOps account will work, but tests will run much faster if the account is setup as public, which enables up to 10 parallel jobs to run simultaneously. +We have setup our `azure-pipelines.yml` file with logical defaults so anyone with an Azure DevOps account can build Lucene.NET and run the tests with minimal effort. Even a free Azure DevOps account will work, but tests will run much faster if the account is setup as public, which enables up to 10 parallel jobs to run simultaneously. #### Prerequisites