* release/2.1-MSRC:
Update to consume aspnetcore 2.0.5-155
Update to consume aspnetcore 2.0.5-152
Revert "Update to consume aspnetcore 2.0.5-152"
Update to consume aspnetcore 2.0.5-152
Commit to trigger a rebuild of the CLI because of a build in place from the Runtime.
Adding the 2.0.3 asp.net store to the native installer tests.
Update to consume aspnetcore 2.0.5-147
Update to consume aspnetcore 2.0.5-146
Updating the runtime to 2.0.5.
Update to consume aspnetcore 2.0.5-142
Fixing the expected fx-version.
Adding a separate dependency version for Microsoft.Build.Runtime.
Updating the branding of the CLI to 2.1.4 and the runtime to 2.0.5.
Conflicts:
build/DependencyVersions.props
* dotnet/release/2.0.0: (32 commits)
Update wix version (#8313)
Use explict and non-preview versions for the build DLL
Fixing a typo...
The 15.4.8 version of the Microsoft.Build.Runtime nuget package is currupt; use the replacement 15.4.8.1
Fix dotnet-install to check the right path for no-op installs when --shared-runtime is specified
Fixed a typo...
Nuget.config update to align with CLI:master - add comments in DependencyVersions.prop
Even more package dependency re-names...
Third pass clean-up of package names.
Second pass clean-up of package names; resequencing download.
Updating dependency version properties in alignment with sample orchestrated build file at: https://dotnetfeed.blob.core.windows.net/orchestrated/20171129-03/orchestration-metadata/PackageVersions.props
The access key is already resolved: 'CoreSetupBlobAccessTokenParam'
Fixed another typo...
Fixed typo...
The first pass will need the extra args [same as run-build.ps1].
Dependency Uptake: download and import a package version props file.
Accounting for MSRC builds with pre-set 'CoreSetupBlobRootUrl' and 'CoreSetupBlobAccessToke' properties.
Changes per code review...
The URL root will include the "dotnet" container; the structure will be identical after the "dotnet" container.
No passwords should be in the open as environmental variables.
...
Conflicts:
build/DependencyVersions.props
src/redist/redist.csproj
src/tool_msbuild/tool_msbuild.csproj
src/tool_roslyn/tool_roslyn.csproj
test/Microsoft.DotNet.Cli.Utils.Tests/Microsoft.DotNet.Cli.Utils.Tests.csproj
* release/2.0.0-MSRC:
Update aspnetcore to 2.0.3 build 125
Update aspnetcore to 2.0.3 build 124
Update aspnetcore to 2.0.3 build 123
Updating branding to 2.0.3, again
Fixing closing tags in the DEB and RPM targets.
Enabling our native installer tests to always get a 2.0.0 asp.net runtime store. We need to solve this in a more generic way in the future. But this will unblock the build for now.
Update aspnetcore runtime store and LZMA to 2.0.3 build 120
Adding the pre-release runtime version hack to RHEL as well. Basically, skip native installer tests when using a pre-release runtime.
Adding the access token to the native installer URLs so that we can download those from protected locations when needed.
Fixing the expected runtime version by the tool tests.
Updating the runtime version.
Updating the branding to 15.5.1
Adding a test hack to allow the CLI to pass tests with a pre-release runtime for 2.0 TFM.
Merged PR 82801: Allow non-anonymous storage account access for .lzma download
It is not currently possible when there is a -f|--framework argument because
we cannot force a TargetFramework global property on to the restore evaluation.
Doing so completely breaks restore by applying the TargetFramework to all
projects transitively. The correct behavior is to restore for all frameworks,
then build/publish/etc for the given target framework. Achieving that still
requires two distinct msbuild invocations.
This also changes the verbosity of implicit restore from quiet to that
of the subsequent command (default=minimal). Similar to global properties,
we cannot specify a distinct console verbosity for the /restore portion of
the overall execution. For consistency, we apply the same verbosity change
to the case where we still use two separate msbuild invocations.
This also fixes an issue where the separate restore invocation's msbuild log
would be overwritten by the subsequent command execution. However, this remains
unfixed in the case where we still use two separate msbuild invocations.
We were taking care to set the console verbosity to minimal, but
only when no verbosity argument is passed. However, the default
verbosity for all CLI msbuild commands is already minimal and so
we can just get out of the way.
* release/2.0.0:
Separating the 'legacy' URL construction from the 'current' URL construction methods and logic.
Use temporary path for fake deps.json in test
MSBuild 15.4.8
Insert SDK 2.0.2-vspre-20170927-1
* dotnet/release/2.0.0:
Use temporary path for fake deps.json in test
Porting 'dotnet-install.sh' from CLI:master to CLI:release/2.0.0
'NuGet.master.config' does not appear to be used.
Reverting previous change to: 'NuGet.master.config'
Moving the runtime version to 2.0.0 for the SDK.
Revert release/2.0.0 back to 1bcee43995
Adding the unified transport NuGet feed.
Keeping the branding for release/2.0.0 at 2.0.3.
MSBuild 15.4.8
Insert SDK 2.0.2-vspre-20170927-1
* release/2.0.0:
Porting 'dotnet-install.sh' from CLI:master to CLI:release/2.0.0
'NuGet.master.config' does not appear to be used.
Reverting previous change to: 'NuGet.master.config'
Moving the runtime version to 2.0.0 for the SDK.
Revert release/2.0.0 back to 1bcee43995
Adding the unified transport NuGet feed.
Update cli-deps-satellites
Fix up roslyn satellite assembly handling to match new insertion mechanism
* dotnet/rel/1.1.0:
Enable VB dotnet new test cases
Fix fedora.23 dockerfile
Updating the ReadMe: "rel-1.0.1" to "rel-1.1.0"
Update Roslyn to 2.3.0-beta4-61830-03
update nuget to 4.3.0-preview4-4258
