mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
dotnet-installer/TestAssets/TestProjects/VSTestDesktopAndNetCore/VSTestDesktopAndNetCore.csproj

21 lines
964 B
XML
Raw Normal View History

Updating the projects files in the repo to use the SDK attribute.
2016-12-20 21:29:45 +00:00
<Project Sdk="Microsoft.NET.Sdk" ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
Testplatform release 15.0.0-preview-20161227-02 (#5055) * Update testplatform packages version * Refer TestPlatform version from DependencyVersions.props * Updating the packages with respect to Testplatform release 15.0.0-preview-20161227-02 * Add dit.props to test assets projects
2016-12-28 18:17:33 +00:00
<Import Project="$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), dir.props))\dir.props" />
1) Added support to run test from test3 verb for the project targeting multiple TFM 2) Added test to address above change 3) Crossgen were creating problem for full CLR built assemblies. Removed All those assembly from Crossgen list. 4) Removed the line of code which were deleting Extensions folder under sdk folder as this folder contain trx logger dlls
2016-10-25 14:40:18 +00:00
<PropertyGroup>
<OutputType>Exe</OutputType>
Moving as many of our test assets to netcoreapp2.0 as possible. I believe the only ones missing at the test packages, because tools always target 1.0. And the other ones are VSTestDotNetCore and VSTestXUnitDotNetCore, because we can't run tests on 2.0 yet. Or, when I tried it failed. I may came back to try this out later.
2017-03-02 20:46:21 +00:00
<TargetFrameworks>net46;netcoreapp2.0</TargetFrameworks>
1) Added support to run test from test3 verb for the project targeting multiple TFM 2) Added test to address above change 3) Crossgen were creating problem for full CLR built assemblies. Removed All those assembly from Crossgen list. 4) Removed the line of code which were deleting Extensions folder under sdk folder as this folder contain trx logger dlls
2016-10-25 14:40:18 +00:00
</PropertyGroup>
Nitpick
2016-11-01 20:26:42 +00:00
1) Added support to run test from test3 verb for the project targeting multiple TFM 2) Added test to address above change 3) Crossgen were creating problem for full CLR built assemblies. Removed All those assembly from Crossgen list. 4) Removed the line of code which were deleting Extensions folder under sdk folder as this folder contain trx logger dlls
2016-10-25 14:40:18 +00:00
<PropertyGroup Condition="'$(TargetFramework)' == 'net46'">
<DefineConstants>DESKTOP;$(DefineConstants)</DefineConstants>
</PropertyGroup>
Updating the version of the TestFramework which fixed the tests for dotnet test and vstest and actually managed to move the projects used there to 2.0. So, only test packages should remain 1.0.
2017-03-03 05:43:06 +00:00
<PropertyGroup Condition="'$(TargetFramework)' == 'netcoreapp2.0'">
<RuntimeFrameworkVersion>2.0.0-beta-001509-00</RuntimeFrameworkVersion>
1) Added support to run test from test3 verb for the project targeting multiple TFM 2) Added test to address above change 3) Crossgen were creating problem for full CLR built assemblies. Removed All those assembly from Crossgen list. 4) Removed the line of code which were deleting Extensions folder under sdk folder as this folder contain trx logger dlls
2016-10-25 14:40:18 +00:00
</ItemGroup>
<ItemGroup>
Version as Metadata in TestAssets
2017-03-03 03:52:26 +00:00
<PackageReference Include="MSTest.TestFramework" Version="1.0.6-preview" />
<PackageReference Include="MSTest.TestAdapter" Version="1.1.5-preview" />
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="$(CLI_TestPlatform_Version)" />
1) Added support to run test from test3 verb for the project targeting multiple TFM 2) Added test to address above change 3) Crossgen were creating problem for full CLR built assemblies. Removed All those assembly from Crossgen list. 4) Removed the line of code which were deleting Extensions folder under sdk folder as this folder contain trx logger dlls
2016-10-25 14:40:18 +00:00
</ItemGroup>
</Project>
Reference in a new issue Copy permalink