dotnet-installer/test/Microsoft.DotNet.ToolPackage.Tests/SampleGlobalTool/includepublish.nuspec

<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>
        <id>global.tool.console.demo</id>
        <version>1.0.4</version>
        <description>test app</description>
        <authors>testauthor</authors>
    </metadata>
    <files>
        <file src="bin\Release\netcoreapp2.1\publish\*.*" target="tools\netcoreapp2.1\any\" />
        <file src="DotnetToolSettings.xml" target="tools\DotnetToolSettings.xml" />
    </files>
</package>
Global tools package obtain (#8035) Add ExeutablePackageObtainer Given a tools package id, it can create a fake project and restore to correct folder - DI, aka no circular dependency of commands - Parser of config XML - I try to create test nupkg at build time, so I can run test and debug easily with VSCode. The code is in test csproj. 2017-11-22 04:10:06 +00:00			`<?xml version="1.0" encoding="utf-8"?>`
			`<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">`
			`<metadata>`
			`<id>global.tool.console.demo</id>`
			`<version>1.0.4</version>`
			`<description>test app</description>`
			`<authors>testauthor</authors>`
			`</metadata>`
			`<files>`
Add install tool command (#8132) * compose all the parts * Fix on obtain and shim maker for better end to end experience * Fix error when there is space in the middle of path of nuget config * Fix path in profile.d is the tmp home path during install * better handle of ~home * remove profile.d file in uninstall script * Fix test since it looks up current directory * folder structure inside nupkg to tools/TFM/RID/mytool.dll * Add check for config file existence * Rename name space to Microsoft.DotNet.ShellShim * Rename name space to Microsoft.DotNet.ToolPackage 2017-12-04 22:13:24 +00:00			`<file src="bin\Release\netcoreapp2.1\publish\." target="tools\netcoreapp2.1\any\" />`
			`<file src="DotnetToolSettings.xml" target="tools\DotnetToolSettings.xml" />`
Global tools package obtain (#8035) Add ExeutablePackageObtainer Given a tools package id, it can create a fake project and restore to correct folder - DI, aka no circular dependency of commands - Parser of config XML - I try to create test nupkg at build time, so I can run test and debug easily with VSCode. The code is in test csproj. 2017-11-22 04:10:06 +00:00			`</files>`
			`</package>`