Go to file
2016-11-20 23:40:17 +00:00
cli Update known-issues.md 2016-11-15 16:54:56 -08:00
Documentation Remove VS2012 pre-reqs (#129) 2016-06-17 09:55:03 -07:00
release-notes Merge pull request #338 from leecow/master 2016-11-16 08:13:51 -08:00
samples Add Dockerfile (#277) 2016-09-26 08:51:01 -07:00
tools/cli-bootstrap Moving Rover (cli-bootstrapping tool) from private repository, into public 2016-11-20 23:40:17 +00:00
.gitattributes we'd like line endings to be normalized 2016-11-20 23:40:17 +00:00
.gitignore Don't add .DS_Store to source 2016-06-27 13:56:32 -05:00
ISSUE_TEMPLATE Update README.md (#225) 2016-07-19 14:10:22 -07:00
LICENSE Initial commit 2014-11-17 17:09:08 -08:00
netci.groovy Spawning netci.groovy in core 2016-11-02 21:32:26 -07:00
README.md Fixing broken link to get the latest builds (#331) 2016-11-05 05:07:53 -07:00
roadmap.md Cleaning up and updating the roadmap.md (#282) 2016-10-17 12:35:35 -07:00

.NET Core Home

The core repository is the starting point to engage in and learn about the .NET Core stack.

Note: please note that this repository is not for filing product issues. If you run into an issue using .NET Core, there are multiple repos where you can file an issue:

We will be removing the ability to file issues on this repo in the near future.

Get Started

If you're new to .NET Core and have 10 minutes to try it, start here:

If you have some more time and want to go deeper or get the latest builds:

.NET Core Platform

The .NET Core platform is made of several components, which includes the managed compilers, the runtime, the base class libraries, and numerous application models such as ASP.NET.

How to Engage, Contribute and Provide Feedback

All projects accept contributions:

You are also encouraged to start a discussion by posting on the .NET Foundation Forums or filing an issue in the corresponding GitHub project. See the contributing guides for more details.

.NET Foundation

The .NET Core platform is part of the .NET Foundation.

Licenses

.NET Core platform projects typically use either the MIT or Apache 2 licenses for code. Some projects license documentation and other forms of content under Creative Commons Attribution 4.0.

See specific projects to understand the license used.

Understanding the relationship between .NET Core and the .NET Framework

.NET Core and the .NET Framework have (for the most part) a subset-superset relationship. .NET Core is named "Core" since it contains the core features from the .NET Framework, for both the runtime and framework libraries. For example, .NET Core and the .NET Framework share the GC, the JIT and types such as String and List<T>.

.NET Core was created so that .NET could be open source, cross platform and be used in more resource-constrained environments. We have also published a subset of the .NET Reference Source under the MIT license, so that you and the community can port additional .NET Framework features to .NET Core.

Understanding the relationship between .NET Core and Mono

Mono is an important part of the .NET ecosystem, particularly for client scenarios (e.g. Xamarin). We will look for ways to collaborate with Mono developers and encourage them to take our code to improve Mono. We will also look for opportunities to improve .NET Core with MIT-licensed Mono code.

An important collaboration opportunity is making .NET Core NuGet packages (produced from this code) work on Mono. The SIMD NuGet package is a perfect example.

Learning about ASP.NET and .NET Core

ASP.NET Core is a new cross-platform version of ASP.NET that is designed for the cloud, and runs on Windows, Linux and Mac. It targets .NET Core by default, but you may choose to target the .NET Framework on Windows.