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/6682
Window title
Update Introduction step content
Include installation location and list of all components installed
Update Summary step content
What is not included:
Remove "Welcome to ..." text -- it come from the installer tool
itself, it cannot be customized
Add 'success' graphic – cannot include picture in the html used by
the installer
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.
* 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.
...
When we only have a single shared framework, the python json parser throws an error since there is a hanging comma on the last property.
Fixing this by removing the comma when there is only a single Shared Framework dependency.
