Updating from 2.4.1 to 3.11.1 issues

[kevsbox]

We have a set of regression tests written in Visual Studio/C# with Reqnroll/ MSTest & playwright. These work very well but I tried to update to the latest version of Reqnroll and MsTest

However when I do this I get these errors

Can anyone tell me how to fix this please.

Thanks

Kev

[clrudolphi]

@kevsbox
Please share the content of your .csproj file.

Also, please attempt another test run, but first Clean the solution before rebuilding (I'm speculating that doing this might resolve the first error message).

[kevsbox]

Hi
I tried a clean and still the same issue, so below is the .csproj file content

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net10.0</TargetFramework>
    <IsPackable>false</IsPackable>
    <BaseOutputPath></BaseOutputPath>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <UserSecretsId>8982c5fa-b282-4593-b8af-2f1dffff951c</UserSecretsId>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
    <WarningLevel>4</WarningLevel>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
    <WarningLevel>4</WarningLevel>
  </PropertyGroup>

  <ItemGroup>
    <Compile Remove="Features\QASuppliers\**" />
    <Compile Remove="obj\**" />
    <EmbeddedResource Remove="Features\QASuppliers\**" />
    <EmbeddedResource Remove="obj\**" />
    <None Remove="Features\QASuppliers\**" />
    <None Remove="obj\**" />
    <ReqnrollFeatureFiles Remove="Features\QASuppliers\**" />
    <ReqnrollObsoleteCodeBehindFiles Remove="Features\QASuppliers\**" />
    <SpecFlowFeatureFiles Remove="obj\**" />
    <SpecFlowObsoleteCodeBehindFiles Remove="obj\**" />
  </ItemGroup>

  <ItemGroup>
    <None Include="Images\vegan.jpg" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="ExcelDataReader" Version="3.9.0" />
    <PackageReference Include="ExcelDataReader.DataSet" Version="3.9.0" />
    <PackageReference Include="ExtentReports" Version="5.0.4" />
    <PackageReference Include="FluentAssertions" Version="8.10.0" />
    <PackageReference Include="Microsoft.Extensions.Configuration" Version="10.0.9" />
    <PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.9" />
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.7.0" />
    <PackageReference Include="Microsoft.Playwright" Version="1.61.0" />
    <PackageReference Include="Microsoft.Playwright.MSTest" Version="1.61.0" />
    <PackageReference Include="MSTest.TestAdapter" Version="4.2.3" />
    <PackageReference Include="MSTest.TestFramework" Version="4.2.3" />
    <PackageReference Include="Newtonsoft.Json" Version="13.0.4" />
    <PackageReference Include="PdfPig" Version="0.1.15" />
    <PackageReference Include="Reqnroll" Version="3.3.4" />
    <PackageReference Include="Reqnroll.MsTest" Version="3.3.4" />
    <PackageReference Include="Reqnroll.Tools.MsBuild.Generation" Version="3.3.4" />
    <PackageReference Include="System.Drawing.Common" Version="10.0.9" />
    <PackageReference Include="System.Windows.Extensions" Version="10.0.9" />
  </ItemGroup>

  <ItemGroup>
    <None Update="Files\ProductDataBad.xlsx">
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </None>
    <None Update="Images\vegan.jpg">
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </None>
  </ItemGroup>
  
</Project>

[clrudolphi]

@kevsbox Sorry, I should have asked this question at the beginning: Do all of the error messages related to 'ClassCleanupBehavior' point to the Reqnroll code-behind generated files? (such as CustomerOrders.feature.cs)

[clrudolphi]

I suggest the following cleanup to the csproj as an experiment:

• eliminate the first . None of those are strictly necessary for Reqnroll.
• eliminate: and from the package references. The reference to the Reqnroll.MsTest package is all that is needed.
• if you don't need to set to null for any specific reason, then remove that line.

Clean the solution.
Manually delete any obj/** and bin/** directories.
And then rebuild and run the tests.

[kevsbox]

Yep, that has fixed it, we are now updated. Many thanks