dotnet-installer/scripts/compile
2016-01-28 20:34:19 -08:00
..
compile-corehost.ps1 Fix host name, debuggability and embed CRT 2016-01-14 12:06:18 -08:00
compile-corehost.sh Fix host name, debuggability and embed CRT 2016-01-14 12:06:18 -08:00
compile-stage-1.ps1 Making some of the testbase methods protected. 2016-01-22 15:22:45 -08:00
compile-stage-1.sh Removing the publishing of the CLI to a separate compilation folder, we don't need it anymore after allowing publish to publish to flat output folders again. This simplifies the scripts. I kept packaging happening in a separate compilation folder because for that we need the tfm folder structure. This also fixes a bug where binaries were only being copied for the first time we built, because we checked that compilationfolder/bin/config/tfm was there. After fowler changes, this was not true for the published CLI, but the packaged folders were still creating this structure, which cause in subsequent build to only the binaries under compilationfolder/bin/debug/dnxcore50 to be copied to stage2dir/bin, instead of everything. 2016-01-28 20:34:19 -08:00
compile-stage-2.ps1 Making some of the testbase methods protected. 2016-01-22 15:22:45 -08:00
compile-stage-2.sh Removing the publishing of the CLI to a separate compilation folder, we don't need it anymore after allowing publish to publish to flat output folders again. This simplifies the scripts. I kept packaging happening in a separate compilation folder because for that we need the tfm folder structure. This also fixes a bug where binaries were only being copied for the first time we built, because we checked that compilationfolder/bin/config/tfm was there. After fowler changes, this was not true for the published CLI, but the packaged folders were still creating this structure, which cause in subsequent build to only the binaries under compilationfolder/bin/debug/dnxcore50 to be copied to stage2dir/bin, instead of everything. 2016-01-28 20:34:19 -08:00
compile-stage.ps1 Removing the publishing of the CLI to a separate compilation folder, we don't need it anymore after allowing publish to publish to flat output folders again. This simplifies the scripts. I kept packaging happening in a separate compilation folder because for that we need the tfm folder structure. This also fixes a bug where binaries were only being copied for the first time we built, because we checked that compilationfolder/bin/config/tfm was there. After fowler changes, this was not true for the published CLI, but the packaged folders were still creating this structure, which cause in subsequent build to only the binaries under compilationfolder/bin/debug/dnxcore50 to be copied to stage2dir/bin, instead of everything. 2016-01-28 20:34:19 -08:00
compile-stage.sh Removing the publishing of the CLI to a separate compilation folder, we don't need it anymore after allowing publish to publish to flat output folders again. This simplifies the scripts. I kept packaging happening in a separate compilation folder because for that we need the tfm folder structure. This also fixes a bug where binaries were only being copied for the first time we built, because we checked that compilationfolder/bin/config/tfm was there. After fowler changes, this was not true for the published CLI, but the packaged folders were still creating this structure, which cause in subsequent build to only the binaries under compilationfolder/bin/debug/dnxcore50 to be copied to stage2dir/bin, instead of everything. 2016-01-28 20:34:19 -08:00
compile.ps1 Allow NuGet cache for non-CI builds 2016-01-05 00:37:23 -08:00
compile.sh switch from DNX to cross-plat NuGet! 2016-01-19 11:43:09 -08:00