dotnet-installer/TestAssets/TestPackages/dotnet-fallbackfoldertool/dotnet-fallbackfoldertool.csproj

<Project Sdk="Microsoft.NET.Sdk" ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <Import Project="$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), testAsset.props))\testAsset.props" />

  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
    <AssemblyName>dotnet-fallbackfoldertool</AssemblyName>
    <OutputType>Exe</OutputType>
    <VersionSuffix></VersionSuffix>
  </PropertyGroup>
  
</Project>
Switched to using a FallbackPackagePathResolver to find the tool dll, because now with Fallback folders, we can have the tool dll in the fallback folder but its assets file in the user nuget cache. This happens because Nuget never writes to the fallback folder, including the tool's assets file that it generates during restore. 2017-03-24 05:20:47 +00:00			`<Project Sdk="Microsoft.NET.Sdk" ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">`
			`<Import Project="$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), testAsset.props))\testAsset.props" />`

			`<PropertyGroup>`
			`<TargetFramework>netcoreapp2.0</TargetFramework>`
			`<AssemblyName>dotnet-fallbackfoldertool</AssemblyName>`
			`<OutputType>Exe</OutputType>`
			`<VersionSuffix></VersionSuffix>`
			`</PropertyGroup>`
Show error if tools package doesn't include runtimeconfig file For test assets, don't explicitly include the runtimeconfig file, as the pack command does it automatically 2017-04-27 00:59:08 +00:00
Switched to using a FallbackPackagePathResolver to find the tool dll, because now with Fallback folders, we can have the tool dll in the fallback folder but its assets file in the user nuget cache. This happens because Nuget never writes to the fallback folder, including the tool's assets file that it generates during restore. 2017-03-24 05:20:47 +00:00			`</Project>`