You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Remove netstandard2.1 target and test support via net6.0, #1040
* Add net10.0 target
* Fix merge issue
* Regenerate github workflows; test OpenNLP on net10
* More C# 14 field keyword changes
* .NET 10 build support in Azure DevOps
* Remove net9.0 tests for lucene-cli
* Add back net9.0
* Remove net9.0 from lucene-cli
* Conditionally set IsPublishable
* Regenerate github workflows
* Remove net9.0 tests
* PR feedback
* Add .NET 9 tests to ADO
* Upgrade Antlr4BuildTasks to 12.11.0
* Fix net9.0 test build
* Revert SetTargetFramework change
* Add net9.0 tests to CLI and OpenNLP test projects
* Directory.Build.props: Added section to compare Visual Studio versions (including prerelease versions) to use to drive IsLegacyVisualStudioVersion property across the solution
* SWEEP: Added legacy support for Visual Studio 2022, excluding net10.0, netstandard2.0, and .NET Framework from compilation. net10.0 isn't supported at all. The others cause invalid warnings in VS 2022 and excluding them from compile is the simplest way around that.
* publish-test-results-for-test-projects.yml: Upload test results for net10.0 for Lucene.Net.Tests.Cli and Lucene.Net.Tests.Analysis.OpenNLP
* publish-test-results-for-test-projects.yml: Upload test results for net9.0 for Lucene.Net.Tests.Cli and Lucene.Net.Tests.Analysis.OpenNLP
* .build/runbuild.ps1 + github/workflows/Generate-TestWorkflows.ps1 + Directory.Build.targets: Added a key identifier SupportedTargetFrameworks to the MSBuild query so it can be parsed using a regex rather than relying on the position in the output (which changed in .NET 9). Updated all callers to use a Get-SupportedTargetFramworks() function to encapsulate the logic of retrieving the target frameworks and parsing out the string we are interested in with an error message if matching fails.
* .github/workflows/Generate-TestWorkflows.ps1: Generate workflow files with no BOM
* Regenerated GitHub test workflows
* Fix comment
---------
Co-authored-by: Shad Storhaug <shad@shadstorhaug.com>
Write-Host"Frameworks To Test for ${testProject}: $frameworksString"-ForegroundColor Yellow
@@ -417,12 +417,21 @@ function Get-Version() {
417
417
418
418
functionGet-FrameworksToTest() {
419
419
# Call the target to get the configured test frameworks for a project known to contain all of them. We only read the first line because MSBuild adds extra output.
Assert($frameworksToTest.Length-gt0) "The project at $(Normalize-FileSystemSlashes "$projectWithAllTestFrameworks") contains no target frameworks. Please configure a project that includes all testable target frameworks."
# NOTE: This will not appear when run directly in the console with minimal verbosity. MSBuild only produces the output when using a pipe, which is what we are doing here.
# NOTE: This will not appear when run directly in the console with minimal verbosity. MSBuild only produces the output when using a pipe, which is what we are doing here.
Write-Host"WARNING: Skipping project '$projectName' because it is not marked with `<IsTestProject`>true`<`/IsTestProject`> and/or it contains no test frameworks for the current environment."-ForegroundColor Yellow
0 commit comments