* Updating README.md files as well as man pages
This aligns with the latest changes in the official documentation. It also aligns dotnet test readme.md to official docs and introduces a new doc in the "Documentation" directory that deals with dotnet test protocols.
- Added PackOptions, RuntimeOptions, PublishOptions and updated CompilationOptions
- Added IncludeFilesResolver to parse include, exclude patterns
- Added compile, embed and copyToOutput to compilationOptions
- Renamed compilationOptions to buildOptions
- Moved compilerName into buildOptions
- This change is backwards compatible
- Added warnings to be shown when the old schema is used
- Handled diagnostic messages in ProjectReader
- Added unit and end to end tests
Also removed the dependency on Microsoft.Extensions.CommandLineUtils.Sources NuGet package and instead just checking the source files into our repo as internal classes.
Fix#2526
* Add and modify commands' README files
Update those READMEs that are outdated. Add READMEs for dotnet pack
and dotnet restore as well.
* Removing private info, adding feedback alias
- Added --version-suffix to build and publish
- Support reading DOTNET_* version variables everywhere versions can be read
- Show the commit sha in dotnet --version
- Added tests that check the assembly output version
- Set DOTNET_BUILD_VERSION when producing the CLI app itself so that it has the version information stamped in for help.
There was a typo in file list that used Source
value for target attribute.
The ordering of metadata was different than
nuget.core and nuget.core never added
DevelopmentDependency if it was set to
false.
There are still some differences between a
nuspec generated through Manifest.Save
in Nuget.Core and this, but all of those
make it more consistent with the nuspec
that is put in the actual package so I'm
leaving them.
The primary difference is that NuGet.Core
used string types to represent the TFM in
groupable items so it would just pass through
whatever you gave the API to the nuspec.
The downside of this is that you might have
an invalid string and you wouldn't know that
until you packed (and cracked open the nuspec).
The new implementation parses the TFM
and writes a normalized version to the nuspec.
This is more wysiwyg so I'm leaving it.
Contained in branches: master#gitext://gotobranch/master
Contained in no tag
