<TargetFramework> vs <TargetFrameworks>

[BrianSchaffer]

When using TargetFrameworks plural in csproj *.feature.cs files always auto generate expecting nUnit when I am using msTest.

Using TargetFramework (singular) resolves the problem. Anyone able to explain this behavior?

[clrudolphi]

@BrianSchaffer Are you still having this problem?
I quickly tried to reproduce the issue but cannot.

If you are still having this problem, please create an Issue (bug report) and include as much detail as you can, and if possible, post a link to a solution demonstration a reproduction.

[304NotModified]

@BrianSchaffer do you have a Directory.Build.props or related file that could mix with your projects?

See https://learn.microsoft.com/en-us/visualstudio/msbuild/customize-by-directory?view=visualstudio and https://learn.microsoft.com/en-us/visualstudio/msbuild/customize-your-build?view=visualstudio

[BrianSchaffer]

Yes, I was using a simple Directory.Build.props.

had problem with

<Project>
    <PropertyGroup>
        <TargetFrameworks>net9.0;net10.0</TargetFrameworks>
    </PropertyGroup>
</Project>

problems went away by changing Directory.Build.props to

<Project>
    <PropertyGroup>
        <TargetFramework>net10.0</TargetFramework>
    </PropertyGroup>
</Project>

rootDir

• testDir
  Directory.Build.props.
  • testProjDir
    *.csproj