* rel/1.1.0: (41 commits)
Updating the Sdk to one that includes the error surfacing work.
Update NuGet to 4.3.0-preview2-4082
Update NuGet to 4.3.0-preview1-4081 and SDK to corresponding 1.1.0 based version
Updating MSBuild to 15.3.0-preview-000246-05 to match VS.
Updating the global.json creation to use the IFile interface and adding a unit test to cover it.
Making restore use a config file so that it does not use fallback folders that may exist in the machine.
Dropping a global.json when running the first run experience with a version that matches the version of the CLI being used in the command that triggered the first run.
Updating the websdk version for 1.0
Trying to fix the opensuse42 test failure, where we tried to invoke a tool that target 1.0.4 where the 1.0 runtime is not available.
Pinning the stage0 to the last build out of rel/1.0.1 and adding a project to download 1.0 dependencies for test assets.
Updating the branding to rel/1.1.0
Dummy commit.
Adding the access token to the lzma url.
Dummy change to force a build.
Reverting the msbuild version to the release version.
Adding the web feed to nuget.config, as some packages failed to mirror and we need a build ASAP.
Updating the msbuild, SDK and Web SDK versions.
Dummy commit to kick off the build.
the FSharp.NET.Sdk version `-bundled` contains only the Sdk dir
bump f# sdk package version
...
New file name structure for the runtime and the CLI
per: https://github.com/dotnet/designs/issues/2
The renaming of assets, therefore the dotnet installation scripts must change to accommodate.
Trivial:
"Write-Host" should be "Write-Output"
New RHEL minor versions are compatible with previous RHEL minor
versions. They also replace them: all users using RHEL 7.n are migrated
to RHEL 7.(n+1) by a simple yum upgrade. So just treat all RHEL 7.x
version as RHEL.
This only holds true for minor versions. RHEL 7 is not compatible with
RHEL 6. But since .NET Core only supports RHEL 7, this shouldn't matter.
The script does not install to /usr/local/share/. It instead installs to
$HOME/.dotnet. Fix the doc text.
Also fix the names in code that incorrectly talk about /usr/local/share.
It duplicates functionality achieved by using `--runtime-id linux-x64`.
Remove it and fix callers.
Keep the the --linux-portable flag in the build scripts; that now calls
--runtime-id linux-x64 in the install script.
This lets us specify the runtime id of the desired .NET Core SDK on the
command line. This makes it easier to get the SDK for the desired
runtime without having to modify the install script for new runtimes
unsupported by the current version of this script.
* rel/1.0.1: (66 commits)
Update LZMA license with correct text
Bump to 2.0.0-rc5-61427-04
Remove duplicate installer suffix
Add license text to LZMA SDK license notice
Updating the SDK to 1.0.0-alpha-20170224-6
Updating both platform abstractions and dependency model to 1.0.3.
Bump Roslyn to 2.0.0-rc5-61424-02
Update Stage0 to use the latest build.
Update README with new distros.
Back porting #5597 into rel/1.0.0
Fixing the exclude pattern used by the Migration to exclude WEB SDK globs.
Remove RID from test package creation
Disable migrate and publish web app with content because CI does not have NPM
Adding an E2E test for pack with content during migration.
Fixing a failing test and adding a few more E2E tests around binplace content for migrated projects.
Fix debian_config.json on ubuntu16.10
Updating publish, pack and build of content to use None with Never/false/Never in their metadata for excluded items.
Intermediate commit to get a WIP PR out. This adds the None Update with CopyToOutputDirectory set to Never.
Switching the CopyToOutput for build and publish and the file for pack to use None Update instead of include. Also, fixed the exclude patterns for web apps.
Do not migrate Content that is already included in the Web SDK for web apps.
...
`which` is an external utility. `hash` or `command -v` are built-in
General Commands.
See http://stackoverflow.com/a/677212/863980
I chose `hash` here as `run-build.sh` is already using it.
When running the CLI builds on the new build agents, the CentOS
build failed with the following error:
2017-01-26T20:39:30.0800810Z Step 4 : RUN yum -q -y install unzip libunwind gettext libcurl-devel openssl-devel zlib libicu-devel
2017-01-26T20:39:30.3020500Z ---> Running in 97affb106685
2017-01-26T20:39:40.3872390Z [91mError: libselinux conflicts with fakesystemd-1-17.el7.centos.noarch
Swapping the the "fakesystemd" package with the real "systemd" package
fixed the issue, which was recommended in http://stackoverflow.com/a/36632668.
This issue hasn't been seen on the official builds because the build
agents in that pool have the Docker image cached, and they are using an
older version of the centos:7.1.1503 image which appears not to have
this issue.
New RHEL minor versions are compatible with previous RHEL minor
versions. They also replace them: all users using RHEL 7.n are migrated
to RHEL 7.(n+1) by a simple yum upgrade. So just treat all RHEL 7.x
version as RHEL.
This only holds true for minor versions. RHEL 7 is not compatible with
RHEL 6. But since .NET Core only supports RHEL 7, this shouldn't matter.
* Updating the version of msbuild to 15.1.0-preview-000516-03
* Remove test that assumes props/targets imports
The test ItAddsRefBetweenImports validated that the MSBuild XML model contained new project references between the props and targets imports. While useful be fore the SDK attribute, the test no longer adds value since the SDK is added implicitly, guaranteeing it wraps the remaining project contents.
* Move MSBuild to 15.1.0-preview-000509-03
This is the last msbuild version prior to the change of MSBuild's dependencies to include .NET 1.1 components.
* Move MSBuild invocations to use dirs.props/dirs.tasks
* Put back the test targets. We'll unify later.
* Remove dirs.props props from templates msbuild invocation
* Add InstallDir to path if SDK version is already installed
* Make changes based on feedback
* Rename "Append" to "Prepend"
* Remove check if directory is already in path
Check the exit status of get_latest_version_info and get_current_os_name to
prevent construction of invalid download URLs based on these functions.
Fixes#2923.
When probing for terminal capabilities, tput will return exit-code 1
when the attribute is not valid for the current terminal.
If we don't handle that exit-code, the shell-script too will exit with
failure.
This patch simply ignores errors for attributes we cannot use,
resulting in the same result as if we never probed for it in the first
place.
* Update README.md
* Moving Ubuntu 16.04 to be next to Ubuntu 14.04
* Adding Oracle Linux and Linux Mint to the titles
Adding Oracle Linux and Linux Mint to the titles next to their compatible binaries.
* Remove showing firsttime eula for non verbs.
* Add Serviceable assembly attribute and nuspec attributes for all shipping CLI assemblies.
Fix#3345
* Use NugetCache Sentinel for Telemetry setting.
* Fix Oracle Linux version in README.md
Oracle Linux 7 -> Oracle Linux 7.1
* Fix README to use hostfxr download links (#3622)
Also fix a rebase error from b524fd079e6dcdd744faeb6061ccbfe99d1f810f#diff-04c6e90faac2675aa89e2176d2eec7d8
* Remove the VS2012 CRT dependency from docs (#3632)
* fix typo in dotnet-install file
This was needed to rebuild the CLI with the updated Roslyn NuGet packages.
Thanks goes to @akoken for the fix.
I believe the intention here was to have -o behave like || however it's
not event needed. =~ does a regex match and so the =~ check against
ubuntu is sufficent.
PR #2493 introduced the new project.json schema. The tree has 118 files
with the old schema, which added several hundred warnings.
This change can't go in until PR #2864 does - it relies on those bug
fixes.
* debian package uninstallation script
* Script to remove/uninstall dotnet pkgs from a OSX machine.
* name change of deb uninstall script
* Address PR feedback
Changes to fail the script if the 'pkgutil --forget' command fails.
When running an app with `dotnet run`, we are redirecting the standard out and error just to print it out to our standard out and error. However, we are batching the output until we hit a newline, which isn't ideal for console apps.
To fix this, `dotnet run` no longer redirects the standard out and error.
Fix#2777
This is required to update the corefx dependencies from RC2 to RC3. Some
of the corefx libs have 'netstandard1.6' as TFM and this version of Nuget
supports that TFM.
Also the 'VersionRange.IncludePrerelease' has been removed from nuget and by
default 'VersionRange.Satisfies' returns true for any prerelease version.
The following packages are changing:
Microsoft.NetCore.App: 1.0.0-rc2-3002702 -> 1.0.0-rc3-002702
Microsoft.NETCore.DotNetHost: 1.0.1-rc2-002702-00 -> 1.0.1-rc3-002702-00
Microsoft.NETCore.DotNetHostPolicy: 1.0.1-rc2-002702-00 ->
1.0.1-rc3-002702-00
Microsoft.NETCore.DotNetHostResolver: 1.0.1-rc2-002702-00 ->
1.0.1-rc3-002702-00
Also publishing the *deb file to teh debian repo feed is disabled -
https://github.com/dotnet/cli/issues/2973
Moves CLI version suffix from preview1 to preview2
Sets channel for preview2 to 1.0.0-preview2, abandoning the Beta channel to the 1.0.0-preview1 release. Once @sokket's publishing cleanup work is complete we can re-converge the channels if desired.
