dotnet-installer/build/Compile.targets

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

  <Target Name="Compile" DependsOnTargets="Prepare;
                                           CompileCLI;
                                           BuildProjectsForNuGetPackages;" />

  <Target Name="CompileCLI">
    <RemoveDir Directories="$(OutputDirectory)" />
    <MakeDir Directories="$(OutputDirectory)"/>

    <!-- Publish DotNet -->
    <MSBuild Projects="$(SrcDirectory)/redist/redist.csproj"
             Targets="Publish" />

    <!-- Build MSBuildSdkResolver for all target frameworks (so we can build and test it x-plat) -->
    <MSBuild Projects="$(SrcDirectory)/Microsoft.DotNet.MSBuildSdkResolver/Microsoft.DotNet.MSBuildSdkResolver.csproj"
             Condition="'$(IncludeMSBuildSdkResolver)' != 'false'" />

    <!-- Publish MSBuildSdkResolver for net46 (to prepare it for the VS insertion nupkg packaging) -->
    <MSBuild Projects="$(SrcDirectory)/Microsoft.DotNet.MSBuildSdkResolver/Microsoft.DotNet.MSBuildSdkResolver.csproj"
             Condition="'$(IncludeMSBuildSdkResolver)' == 'true' and '$(OS)' == 'Windows_NT'"
             Properties="TargetFramework=net46"
             Targets="Publish" />
  </Target>
</Project>
Addressing more code review comments 2016-07-01 18:02:26 +00:00			`<?xml version="1.0" encoding="utf-8"?>`
			`<Project ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">`
Fixed tabs to 2 spaces instead of 4 for our targets files 2016-06-30 17:39:39 +00:00
Addressing more code review comments and removing the incrementality from BuildProjectsForNuGetPackages. All it does is invoke dotnet build, which already has incremental builds. I will let it handle this one. 2016-07-01 00:34:11 +00:00			`<Target Name="Compile" DependsOnTargets="Prepare;`
Remove Stage1 compilation 2017-02-08 03:41:45 +00:00			`CompileCLI;`
Move remaining Publish actions to redist.csproj 2017-03-01 08:30:02 +00:00			`BuildProjectsForNuGetPackages;" />`
Fixed tabs to 2 spaces instead of 4 for our targets files 2016-06-30 17:39:39 +00:00
Refactor props in crossgen.target 2017-02-21 22:22:36 +00:00			`<Target Name="CompileCLI">`
Remove duplicate properties 2017-02-27 19:06:44 +00:00			`<RemoveDir Directories="$(OutputDirectory)" />`
			`<MakeDir Directories="$(OutputDirectory)"/>`
Try to fix spacing 2017-02-22 19:03:11 +00:00
Try to fix spacing part 2 2017-02-22 19:06:57 +00:00			`<!-- Publish DotNet -->`
Fix passing /p:DISABLE_CROSSGEN on cli. When passing a property using the commandline, it is not flown through to "dotnet publish" calls. So instead of using "dotnet publish", just use the MSBuild task to invoke the Publish target on the reidst project. This way properties flow correctly. I also did a little cleaning of unused build logic. 2017-04-04 22:50:28 +00:00			`<MSBuild Projects="$(SrcDirectory)/redist/redist.csproj"`
			`Targets="Publish" />`
Add msbuild sdk resolver 2017-04-26 22:01:59 +00:00
Package MSBuild SDK resolver in VS insertion nupkg 2017-04-28 06:05:48 +00:00			`<!-- Build MSBuildSdkResolver for all target frameworks (so we can build and test it x-plat) -->`
Provide a way to not include the SDK Resolver When building the entire stack for a non windows target, the windows resolver packages will not be present (and in the case of a windows build, you'd only have one architecture anyway). Provide a way to opt out of including the resolver. It's only interesting for Visual Studio insertion cases, which is something the community at large doesn't need to worry about. 2017-05-12 00:58:28 +00:00			`<MSBuild Projects="$(SrcDirectory)/Microsoft.DotNet.MSBuildSdkResolver/Microsoft.DotNet.MSBuildSdkResolver.csproj"`
			`Condition="'$(IncludeMSBuildSdkResolver)' != 'false'" />`
Package MSBuild SDK resolver in VS insertion nupkg 2017-04-28 06:05:48 +00:00
			`<!-- Publish MSBuildSdkResolver for net46 (to prepare it for the VS insertion nupkg packaging) -->`
			`<MSBuild Projects="$(SrcDirectory)/Microsoft.DotNet.MSBuildSdkResolver/Microsoft.DotNet.MSBuildSdkResolver.csproj"`
Provide a way to not include the SDK Resolver When building the entire stack for a non windows target, the windows resolver packages will not be present (and in the case of a windows build, you'd only have one architecture anyway). Provide a way to opt out of including the resolver. It's only interesting for Visual Studio insertion cases, which is something the community at large doesn't need to worry about. 2017-05-12 00:58:28 +00:00			`Condition="'$(IncludeMSBuildSdkResolver)' == 'true' and '$(OS)' == 'Windows_NT'"`
Package MSBuild SDK resolver in VS insertion nupkg 2017-04-28 06:05:48 +00:00			`Properties="TargetFramework=net46"`
			`Targets="Publish" />`
First step to ingest template engine (#5065) * First step to ingest template engine Please do not merge yet @piotrp @seancpeters @livarocc * Localization * Attempt to get a build going Rename program.cs to New3Command.cs Move TableFormatter into its own file Consume template engine packages version 1.0.0-beta1-20161218-24 Temporarily add MyGet templating feed so that package restore will work * Update ExtendedCommandParser Make short form args prefer longer runs of characters in the source parameter before falling back to p:shortname syntax Change scoping for a few methods to get rid of inconsistent visiblity errors * Fix package installation wildcards * Cleanup New3Command, fix review issue, bump version, sorting for template list * Installation, loc fix, help formatting * Use latest TemplateEngine packages * New3 unit tests * Fixed formatting on csproj files * Add the build steps to add templates to the layout * Change tests slightly to make comparisons easier Also fixes the wrong flag getting passed to set language * Fixes for 127, 128, 130, 131 - help display * Sync to latest TemplateEngine version Absorbs new search logic * All tests passing Cleaner New3Command Support for project/item template contexts * Try to make tests more durable * Disable test parallelization for dotnet-new tests * Update web SDK and template engine versions * Remove AI package feed * Simplify CLI interface to Template Engine * Fix host identifier and update to latest packages * Update template engine & Web SDK versions * Fix template engine version * Remove UsingTask and redeclaration of property 2017-01-06 22:48:27 +00:00			`</Target>`
don't try to make crossgen executable if crossgen is disabled (it might not exist!) 2017-02-15 20:39:45 +00:00			`</Project>`