mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
dotnet-installer/test/dotnet-compile.UnitTests/dotnet-compile.UnitTests.xproj

21 lines
1.2 KiB
Text
Raw Normal View History

Refactoring dotnet-compile to make adding the script variable testable. So far, moved it to have a compiler controller and two separate compilers: native and managed. Also moved the script runner to its own class so that we can mock it into the managed controller. Adding a ICommand interface and factory that we can use to mock Commands and avoid actually running them in unit tests.
2016-02-10 00:35:43 +00:00
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="14.0.24720" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">14.0.24720</VisualStudioVersion>
<VSToolsPath Condition="'$(VSToolsPath)' == ''">$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)</VSToolsPath>
</PropertyGroup>
Revert "Update the .xproj files to reference the "DotNet" targets and props instead of "DNX"." This reverts commit 4304ca9848eced94a0f39829fd31b2a3cf601bec.
2016-03-16 16:44:09 +00:00
<Import Project="$(VSToolsPath)\DNX\Microsoft.DNX.Props" Condition="'$(VSToolsPath)' != ''" />
Refactoring dotnet-compile to make adding the script variable testable. So far, moved it to have a compiler controller and two separate compilers: native and managed. Also moved the script runner to its own class so that we can mock it into the managed controller. Adding a ICommand interface and factory that we can use to mock Commands and avoid actually running them in unit tests.
2016-02-10 00:35:43 +00:00
<PropertyGroup Label="Globals">
<ProjectGuid>920b71d8-62da-4f5e-8a26-926c113f1d97</ProjectGuid>
<RootNamespace>dotnet-compile.UnitTests</RootNamespace>
<BaseIntermediateOutputPath Condition="'$(BaseIntermediateOutputPath)'=='' ">..\..\artifacts\obj\$(MSBuildProjectName)</BaseIntermediateOutputPath>
Updating tests to use the latest version of dotnet-test-xunit, which supports debugging from VS. Also updating our xproj files so that we can build the CLI from VS using the CLI.
2016-03-01 20:29:09 +00:00
<OutputPath Condition="'$(OutputPath)'=='' ">..\..\artifacts\bin</OutputPath>
Refactoring dotnet-compile to make adding the script variable testable. So far, moved it to have a compiler controller and two separate compilers: native and managed. Also moved the script runner to its own class so that we can mock it into the managed controller. Adding a ICommand interface and factory that we can use to mock Commands and avoid actually running them in unit tests.
2016-02-10 00:35:43 +00:00
</PropertyGroup>
<PropertyGroup>
<SchemaVersion>2.0</SchemaVersion>
</PropertyGroup>
Updating tests to use the latest version of dotnet-test-xunit, which supports debugging from VS. Also updating our xproj files so that we can build the CLI from VS using the CLI.
2016-03-01 20:29:09 +00:00
<ItemGroup>
<Service Include="{82a7f48d-3b50-4b1e-b82e-3ada8210c358}" />
</ItemGroup>
Revert "Update the .xproj files to reference the "DotNet" targets and props instead of "DNX"." This reverts commit 4304ca9848eced94a0f39829fd31b2a3cf601bec.
2016-03-16 16:44:09 +00:00
<Import Project="$(VSToolsPath)\DNX\Microsoft.DNX.targets" Condition="'$(VSToolsPath)' != ''" />
Refactoring dotnet-compile to make adding the script variable testable. So far, moved it to have a compiler controller and two separate compilers: native and managed. Also moved the script runner to its own class so that we can mock it into the managed controller. Adding a ICommand interface and factory that we can use to mock Commands and avoid actually running them in unit tests.
2016-02-10 00:35:43 +00:00
</Project>
Reference in a new issue Copy permalink