ArchiSteamFarm/ArchiSteamFarm.Tests/ArchiSteamFarm.Tests.csproj

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Library</OutputType>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="ConfigureAwaitChecker.Analyzer" PrivateAssets="all" />
    <PackageReference Include="Microsoft.NET.Test.Sdk" />
    <PackageReference Include="MSTest.TestAdapter" />
    <PackageReference Include="MSTest.TestFramework" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\ArchiSteamFarm\ArchiSteamFarm.csproj" />
  </ItemGroup>
</Project>
Add MatchableTypes As well as unit testing so I'm sure that part is not screwed up. 2017-07-10 08:20:15 +02:00			`<Project Sdk="Microsoft.NET.Sdk">`
			`<PropertyGroup>`
Correct ArchiSteamFarm.Tests for net472 2018-06-11 01:38:35 +02:00			`<OutputType>Library</OutputType>`
Add MatchableTypes As well as unit testing so I'm sure that part is not screwed up. 2017-07-10 08:20:15 +02:00			`</PropertyGroup>`

			`<ItemGroup>`
Manage package versions centrally (#2317) Closes #2316 The issue we're facing right now comes from the fact of desynchronization of packages between different projects. Since I didn't find any way to "fix" the package versions of our plugins to the main ASF project, we'll instead use centralized Directory.packages.props which specifies appropriate versions 2021-05-02 14:51:08 +02:00			`<PackageReference Include="ConfigureAwaitChecker.Analyzer" PrivateAssets="all" />`
			`<PackageReference Include="Microsoft.NET.Test.Sdk" />`
			`<PackageReference Include="MSTest.TestAdapter" />`
			`<PackageReference Include="MSTest.TestFramework" />`
Add MatchableTypes As well as unit testing so I'm sure that part is not screwed up. 2017-07-10 08:20:15 +02:00			`</ItemGroup>`

			`<ItemGroup>`
			`<ProjectReference Include="..\ArchiSteamFarm\ArchiSteamFarm.csproj" />`
			`</ItemGroup>`
			`</Project>`