Issue https://github.com/dotnet/cli/issues/7091
Add internal command dotnet internal-reportinstallsuccess. Before
Windows installer finishes, run this command instead of dotnet new. It
will trigger the first time experience as well as sending telemetry with
installer exe name.
This command blocks to ensure that the webservice call completes.
According to https://github.com/dotnet/cli/issues/6683
- Remove Motto
- Change size to fit the first screen
- Update Introduction step content
- Include installation location and list of all components installed
- Update Summary step content
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"
* master: (106 commits)
Fixing the tests to handle the extra tests added by the min version change.
Fixing windows build and addressing code review comments.
Changing the resolver so that it will search for dotnet in the PATH instead of hard coded program files.
Update Roslyn to latest 15.3 version
Removing unused parameters.; ".StartsWith" method for strings is not always present.
Disabling net461 tests for the resolver.
Default channel in the install scripts; dotnet-install.ps1 and dotnet-install.sh = “release/1.0.0”
Forcing 'curl' to return an usable exitcode.
Changes per code review - stronger download failure logic.
Update to SetupCrossgen 125 - Coherence 25159
Changes per additional manual testing on ubuntu-x64
Addressing code review comments and trying to fix the windows break.
Updating the websdk version to 2.0.0-rel-20170518-512
Changes per manual testing on Windows-x64
Changes per manual testing on ubuntu-x64
Update to SetupCrossgen 123 - Coherence 25149
First draft changes for install script for the SDK and Runtime.
Update to SetupCrossGen 121 - Coherence 25102
Revert "Disabling the VB tests in non-windows platforms while MSBuild fixes a bug that we need for cross-plat."
fix command names
...
cmd.exe window will popup during the install. Will create an issue and fix it separately.
CLISDKMsiSourcePath needs to be install at the last step so the dotnet.exe will be there and all the files are there.
These nuget packages are used to deliver the CLI payload to Visual Studio
setup authoring. They are pushed (by VSO build definitions) into an internal feed consumed by
Visual Studio.
The windows installer downloads the VC redist bundles as a remote payload
from a URL. This URL owned by the VC++ team recently changed to point to
updated CRTs. This broke our windows installers. So we decided to upload
the CRTs to a URL owned by the .Net Core team and use that for chaining
the VC Redist bundle.
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.
Refactor HostVersion into its own class and use it everywhere host
artifacts are created. This includes the
- host nuget packages
- host installers (msi, pkg, deb)
Earlier the host MSI dependency key changed for every version. Therefore
the following stesp uninstalled host aggresively.
- Install a older dotnet CLI bundle (say v1)
- Install a newer dotnet CLI bundle (say v2)
- Uninstall the newer CLI bundle. This removes the host completely and
leaves the older version v1 unusable.
With this fix all the versions of the CLI in the machine will reference
count the host correctly.
Fixes - #2713
Remove code to find the previous install folder, always install into
%ProgramW6432%. Also remove the option to allow DOTNETHOME to be
overridable.
Fixes - #2743
