This repo is building the .NET Standard
C# Other
Clone or download
terrajobst Merge pull request #785 from terrajobst/planning-vnext
Add planning for .NET Standard vNext
Latest commit 1874541 Jul 24, 2018
Permalink
Failed to load latest commit information.
Microsoft.Packaging.Tools.Trimming Add diagnostic logging to trimming Jun 12, 2018
apicompat Update baseline files based on changes in BuildTools Oct 27, 2017
buildpipeline Rename config.json task to avoid confusing run.cmd in master (#749) May 22, 2018
docs Add planning for .NET Standard vNext Jul 24, 2018
external/docs Add Intellisense package restore and hookup for netstandard package Jun 29, 2017
netstandard Merge branch 'master' into pr793 Jul 13, 2018
pkg Remove Microsoft.Packaging.Tools Jun 7, 2017
platforms Update Xamarin.WatchOS API to 11.14.0.10 Jul 19, 2018
.gitattributes Initial commit Sep 1, 2016
.gitignore Initial commit Sep 1, 2016
BuildToolsVersion.txt Update BuildTools to preview1-02902-01 Jun 2, 2018
CONTRIBUTING.md Initial commit Sep 1, 2016
DotnetCLIVersion.txt Building non-Windows builds using the CLI's MSBuild (#638) Feb 1, 2018
LICENSE.TXT Update the License May 15, 2017
NuGet.config Add transport feed as a source Oct 25, 2017
Packaging.props Update intellisense based on the 2-2-2018 doc build Feb 9, 2018
README.md Link to Versions document in README Apr 3, 2017
THIRD-PARTY-NOTICES.TXT Update the License May 15, 2017
build-managed.sh Fix some unix build issues. Jan 26, 2017
build.cmd Add double quotation marks for pathes have space(s) Dec 6, 2016
build.sh Fix some unix build issues. Jan 26, 2017
clean.cmd Add double quotation marks for pathes have space(s) Dec 6, 2016
config.json Rename config.json task to avoid confusing run.cmd in master (#749) May 22, 2018
dependencies.props Update BuildTools to preview1-02902-01 Jun 2, 2018
dir.proj Respond to PR feedback. Oct 27, 2017
dir.props Enable latest version of C# Jul 13, 2018
dir.targets Clean up some more properties that aren't needed or moved to BuildTools Apr 28, 2017
dir.traversal.targets Add Conflict Resolution task Dec 28, 2016
init-tools.cmd Updating to 2.0.0 RTM CLI Oct 27, 2017
init-tools.msbuild Enable publish to azure blob feed Oct 24, 2017
init-tools.sh Building non-Windows builds using the CLI's MSBuild (#638) Feb 1, 2018
netci.groovy Update CI to use OSX10.12, needed to move to the 2.0 CLI Apr 27, 2017
packages.builds Respond to PR feedback. Oct 27, 2017
publish.msbuild Get access to build.common.targets in publish.msbuild in master (#751) May 22, 2018
run.cmd Add double quotation marks for pathes have space(s) Dec 6, 2016
run.sh signing suggestions from wes Jan 20, 2017
signing.builds finalizing signing work Jan 26, 2017
src.builds Respond to PR feedback. Oct 27, 2017

README.md

.NET Standard

This repository contains the principles and definition of the .NET Standard.

.NET Standard solves the code sharing problem for .NET developers across all platforms by bringing all the APIs that you expect and love across the environments that you need: desktop applications, mobile apps & games, and cloud services:

  • .NET Standard is a set of APIs that all .NET platforms have to implement. This unifies the .NET platforms and prevents future fragmentation.
  • .NET Standard 2.0 will be implemented by .NET Framework, .NET Core, and Xamarin. For .NET Core, this will add many of the existing APIs that have been requested.
  • .NET Standard 2.0 includes a compatibility shim for .NET Framework binaries, significantly increasing the set of libraries that you can reference from your .NET Standard libraries.
  • .NET Standard will replace Portable Class Libraries (PCLs) as the tooling story for building multi-platform .NET libraries.

How to Engage, Contribute and Provide Feedback

You are also encouraged to start a discussion by filing an issue.

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.

Learning More

Currently defined versions of the .NET Standard can be located in the Versions document.

For more information, check out the FAQ. It should answer any questions you have not covered by the versions documentation.