-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XUnit tests on net462 are skipped due to Strong name signature verification. #14091
Comments
Is that happening inside VS only or also with |
@ViktorHofer this is happening on 1ES images. windows-2022 image and this is the link to what is included in that image: It happens with dotnet test and I have not tried other scenarios. |
I don't understand the problem fully yet but it has to with full strong name signature verification on .NET Framework when using appdomains. Here's what we do in our repositories to make this work: Add a {
"shadowCopy": false
} In the test project: <ItemGroup>
<None Update="xunit.runner.json" CopyToOutputDirectory="PreserveNewest" />
</ItemGroup> EDIT: see dotnet/runtime#17313 (comment) & https://stackoverflow.com/questions/60058571/unit-testing-public-signed-net-core-framework-libraries for more details |
@JRahnama was Viktor's comment able to resolve your issue? |
@missymessa I just tested and can confirm the issue is fixed. Thank you. |
NetCore is working fine.
I have tested with:
Could be checked at PR #2033 on SqlClient repo.
Release Note Category
Release Note Description
The text was updated successfully, but these errors were encountered: