Update test projets and simplify the Continuous Integration workflow#70
Update test projets and simplify the Continuous Integration workflow#70manuelbl merged 9 commits intomanuelbl:masterfrom
Conversation
0xced
commented
Apr 30, 2025
- Remove DiffEngine package reference (it would fail with NU1605: Detected package downgrade: DiffEngine from 16.2.1 to 15.11.0)
- Simplify projects
- Don't use floating version. For example, 2.* resolves to 2.0.0 instead of 2.9.3
- Cleanup unused dependencies
- Use Verify.DocNet instead of custom code to convert PDF to PNG
- Fix deprecation warning on VerifierSettings.RegisterFileConverter
* Remove DiffEngine package reference (it would fail with NU1605: Detected package downgrade: DiffEngine from 16.2.1 to 15.11.0) * Simplify projects * Don't use floating version. For example, 2.* resolves to 2.0.0 instead of 2.9.3 * Cleanup unused dependencies * Fix deprecation warning on VerifierSettings.RegisterFileConverter
Package validation is now included in the .NET SDK. This also fixes these warnings when restoring: > warning NU1505: Duplicate 'PackageDownload' items found.
This greatly simplifies the CI yaml script.
It's now included in the .NET SDK.
|
Thanks for the updates. These are good changes in an area I'm struggling with. Projects supporting multiple .NET version have their challenges, and the .NET tools have some rough edges. Unfortunately, the updates don't quite work yet. Some of the unit tests fail. It affects some tests of the And And what is the reason for increasing |
That's surprising because it works fine on the GitHub Windows runner. The TestResults-Windows.zip from the last action run has all 13 tests passing.
That's what happens when the file can't be found. If you run Also, does it work if you explicitly specify an output directory on the command line by running the
If you delete the Here are the exact breaking changes that surface when running So now that version 3.3.0 is out with the breaking changes the best think is acknowledge that those breaking changes were introduced and update the baseline to the last released version. |
|
Thanks again for the PR. The failing tests are related to several factor:
The worst part is that the test only fail sometimes, probably when executed in a certain order. I was only able to fix it partially. I will have to live with the fact that I cannot execute them all from within Visual Studio. If each project is executed separately (as in the CI pipeline), it works. I was also able to resolve the issue with It's a shame that the incompatibilities with previous versions I have introduced were not detected. The baseline validator has been part of the project for some time and has detected incompatibilities before. But somehow, it hasn't detected all incompatibilities. Do you know if it has been extended to check for more issues? |
The problem was this old SDK reference that was removed in commit 6534161: <Sdk Name="Microsoft.DotNet.PackageValidation" Version="1.0.0-preview.7.21379.12" />Without this SDK, the built-in package validation feature from the .NET 8 SDK detects more breaking changes. |