We were publishing a -debug zip with sdk code and symbols, but it was captured before
publishing was finished and had incorrect code content. Trying to use it would blow up
due to incorrect runtimeconfig.json.
Replace it with a -symbols zip that contains only symbols and that can be overlayed
over the main zip. This is just like the -langpack zip that has satellite assemblies.
Also add an option to leave the PDBs in the same directory/packages as code:
/p:SeparateSymbolsArchive=false. Setting this on local builds facilitates
debugging and profiling by removing the need to adjust symbol paths or copy PDBs
around.
* release/2.0-vs: (22 commits)
Insert SDK 2.0.2-vspre-20170921-5
Insert SDK 2.0.2-vspre-20170915-1
MSBuild 15.4.7
Updating the websdk version to 2.0.0-rel-20170908-653
Insert NuGet Build 4.4.0-preview3-4475 into cli
Remove out of support ubuntu1610
Removing extra line feeds...
Turning on the NuPkg publishing from Win x86
The enumeration of the nupkg packages depends on that the creation of packages has already occurred.
Trivial change to start a VSO build
Push the 'VS.Redist.Common.Net.Core.SDK*.nupkg' packages to blob storage.
Remove EOL openSuSE 42.1
Trigger build
Trigger build
Sign additional files
Update CLI_NETSDK_Version SDK to 2.0.2-vspre-20170825-1
Dummy commit to trigger CI due to 20170824.1 publish nuget time out 20170824.1
Insert NuGet Build 4.4.0-preview1-4434 into cli
Update to SDK build which includes NuGet 4.4.0-preview1-4365
Insert NuGet Build 4.4.0-preview1-4365 into cli
...
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
