-
Notifications
You must be signed in to change notification settings - Fork 325
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
[17.3.0] You must install or update .NET to run this application. #3938
Comments
The output message complains about .NET "Core" not being found, and based on the verison " '2.0.0-preview.0' " it looks like a fallback is used to a very old version that is out of life. I see you say that your project is not .NET Core, but rather .NET Frameworks 4.6.2. It looks like additional dll is trying to run after your tests. Could you please check the build output to see how many dlls matched and if it says in the output which dlls are running? Is any of those dlls not expected to run? Providing diagnostic logs would also help, if that is possible for you https://github.com/microsoft/vstest-docs/blob/main/docs/diagnose.md |
vstest.console.exe "...\bin\Release...Sdk.Testing.dll" -> .NETFramework,Version=v4.6.2 I cant check right now, but might be the Adapter Utilities which are not correctly excluded in the filter that are causing the issue with .net core. |
Yeah there is another issue where I am thinking the same, I am guessing that this would be caused by multi-tfm, that would previously skip the dll because it is not .net framework. I am building a pipeline to get repro, locally I see it fail even on 17.2.0 (but did not try your exact case yet). |
openend #3939 with suggested filters to use while we are fixing it. |
So, some confirmation because I had the same problem on a different project today: Not only rollback to 17.2.0 works but also correcting the filter to exclude the AdapterUtilities.dll. How to:
The issue will probably not affect everyone because it relates to these projects have older exclusions where the namespace contained |
Close this one because a suggestion was given by the comment #3938 (comment) |
okay |
Description
Running Tests in Azure DevOps produces the following error with a .NET Framework Solution.
Assumption: Since the problem started when the installer started installing Version 17.3.0 instead of 17.2.0, it is assumed this is not a problem of Azure DevOps with
vmImage: 'windows-latest'
.Steps to reproduce
With the following Setup of YAML Pipeline Tasks
Error can be reproduced, even with a Commit as base that had a successful build before the weekend.
Test Projects are in .NET Version 4.6.2.
Expected behavior
Tests Task fails if Tests do not work, it should run green if all Tests are passed.
Workaround
Specifying the previous version 17.2.0 fixes the problem.
Actual behavior
Error is thrown as shown in Description.
Note: The error is thrown after the Tests are run, so there are more that 100 passed tests in the published result.
Environment
Azure Devops Pipeline with
vmImage: 'windows-latest'
.The text was updated successfully, but these errors were encountered: