As called out in this blog post, .NET Core 3.1 ends LTS on 13 December 2022, which is coming up quickly. Some of our .NET dependencies are dropping support for .NET Core 3.1, so in order to stay on current binaries, we are shifting our EXE's to .NET 6.0. This includes the CLI and all test projects. The libraries in the NuGet package will continue to build using .NET Standard 2.0, so they'll continue to work in either .NET or .NET Framework applications. They will also continue to be Windows-specific, which makes sense since UIA is a Windows-specific technology.
Validation included:
Run changes through the signed build pipeline. Artifacts are here
Install and run the signed CLI (using the MSI installer)
Using a local package store, update AIWin to use the signed NuGet package and make sure that it still works as expected
Motivation
Avoid the situation where we depend on libraries that are out of support or untested in our install environment.
Context
This and #834 both involve the WXS file. Some merge resolution will be needed, no matter what order we merge.
Details
As called out in this blog post, .NET Core 3.1 ends LTS on 13 December 2022, which is coming up quickly. Some of our .NET dependencies are dropping support for .NET Core 3.1, so in order to stay on current binaries, we are shifting our EXE's to .NET 6.0. This includes the CLI and all test projects. The libraries in the NuGet package will continue to build using .NET Standard 2.0, so they'll continue to work in either .NET or .NET Framework applications. They will also continue to be Windows-specific, which makes sense since UIA is a Windows-specific technology.
Validation included:
Motivation
Avoid the situation where we depend on libraries that are out of support or untested in our install environment.
Context
This and #834 both involve the WXS file. Some merge resolution will be needed, no matter what order we merge.
Pull request checklist