<<<<<<< HEAD
This repo contains the library implementation (called "CoreFX") for .NET Core. It includes System.Collections, System.IO, System.Xml, and many other components. The corresponding .NET Core Runtime repo (called "CoreCLR") contains the runtime implementation for .NET Core. It includes RyuJIT, the .NET GC, and many other components. Runtime-specific library code (mscorlib) lives in the CoreCLR repo. It needs to be built and versioned in tandem with the runtime. The rest of CoreFX is agnostic of runtime-implementation and can be run on any compatible .NET runtime (e.g. CoreRT).
Great starting page: http://dotnet.github.io
- How to use .NET Core (with VS, VS Code, command-line CLI)
- Install official releases
- Documentation (Get Started, Tutorials, Porting from .NET Framework, API reference, ...)
- Roadmap
- Releases
- Bringing more APIs to .NET Core (and why some APIs will be left out)
Some of the best ways to contribute are to try things out, file bugs, join in design conversations, and fix issues.
- Dogfooding daily builds
- If you have a question or idea, file a new issue.
If you are having issues with the "full" .NET Framework (also called "Desktop"), the best way to file a bug is at Connect or through Product Support if you have a contract.
This section is in progress here: New contributor Docs - Issues (feel free to make it better - it's easy-to-edit wiki with RW permissions to everyone!)
This section is in progress here: New contributor Docs - Contributing (feel free to make it better - it's easy-to-edit wiki with RW permissions to everyone!)
- CoreFX source index: https://source.dot.net
- API Reference docs: https://docs.microsoft.com/en-us/dotnet/core/api
- .NET API Catalog: http://apisof.net (incl. APIs from daily builds and API usage info)
- "Full" .NET Framework source index: https://referencesource.microsoft.com
- General .NET OSS discussions: .NET Foundation forums
- Chat with other community members
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.
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
.NET Core (including the corefx repo) is licensed under the MIT license.
.NET Core is a .NET Foundation project.
There are many .NET related projects on GitHub.
- .NET home repo - links to 100s of .NET projects, from Microsoft and the community.
- ASP.NET Core home - the best place to start learning about ASP.NET Core.
Daily builds of .NET Core components are published to dotnet-core MyGet gallery. The latest version number of each library can be seen in that gallery.
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:
- dotnet/cli - for CLI tools and questions
- dotnet/corefx - for API issues and questions
- dotnet/coreclr - for runtime issues
- dotnet/docs - for .NET documentation issues and questions
- dotnet/sdk - for .NET Core SDK (used by Visual Studio and CLI) issues and questions
- dotnet/standard - for .NET Standard issues and questions
- nuget/home - for NuGet questions and issues
- aspnet/home - for ASP.NET Core questions and issues.
- aspnet/Docs - for ASP.NET and ASP.NET Core documentation issues and questions
- dotnet/netcorecli-fsc - for F# questions and issues
We will be removing the ability to file issues on this repo in the near future.
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:
- Get the latest builds of .NET Core on Windows, OSX and Linux
- Get the latest builds of ASP.NET Core on Windows, OSX and Linux
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.
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.
The .NET Core platform is part of the .NET Foundation.
.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.
.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.
Mono is an important part of the .NET ecosystem, particularly for client scenarios (for example, 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.
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.
upstream/master