Go to file
Javier Calvarro Nelson 8e1e81ae78
[HTTPS] Update certificate strategy for Mac OS (#20022)
* Fixes and improvements for dotnet-dev-certs:
* Revamps the HTTPS developer certificate tool implementation.
  * It accumulated a lot of cruft during the past few years and that has made making changes harder.
* Separated the CertificateManager implementation into different classes per platform.
  * This centralizes the decision point of choosing a platform in a single place.
  * Makes clear what the flow is for a given platform.
  * Isolates changes needed for a given platform in the future.
* Moved CertificateManager to a singleton
  * No more statics!
* Updates logging to use EventSource
  * We didn't have a good way of performing logging as the code is shared and must run in multiple contexts and the set of dependencies need to be kept to a minimum.
  * Adding ETW allow us to log/monitor the the tool execution and capture the logs with `dotnet trace` without having to invent our own logging.
  * We can decide to write an EventListener in `dotnet-dev-certs` to write the results to the console output.
* Updates the way we handle the dev-cert in Mac OS to use the security tool to import the certificate into the store instead of using the certificate store.
2020-04-16 13:52:10 -07:00
.azure/pipelines Revert "Use BuildTools internally too" 2020-04-15 14:40:56 -07:00
.config
.github Disable the sync action in forks (#19934) 2020-03-19 12:34:04 -07:00
.vscode
docs Adding an area-ownership document (#20108) 2020-03-24 14:44:32 -07:00
eng Update dependencies from https://github.com/dotnet/efcore build 20200415.4 (#20884) 2020-04-16 12:08:33 -07:00
src [HTTPS] Update certificate strategy for Mac OS (#20022) 2020-04-16 13:52:10 -07:00
.editorconfig
.gitattributes
.gitignore Adding reference to MessagePackAnalyzer to check for MsgPack001 / MsgPack002 (Banned API) (#19989) 2020-03-19 16:05:45 -07:00
.gitmodules
.vsconfig Add .vsconfig files in root and beside slns 2020-03-31 14:25:44 -07:00
CODE-OF-CONDUCT.md Link Code of Conduct 2020-04-02 19:51:30 -07:00
CONTRIBUTING.md More updates docs (#20513) 2020-04-03 22:09:36 +00:00
Directory.Build.props Merge branch 'master' into johluo/remove-extensions-deps 2020-04-06 11:17:56 -07:00
Directory.Build.targets Merge branch 'master' into merge/release/3.1-to-master 2020-03-27 10:24:36 -07:00
LICENSE.txt
NuGet.config Update dependencies from https://github.com/dotnet/efcore build 20200331.5 (#20399) 2020-04-01 07:16:57 +00:00
README.md Update README.md (#20486) 2020-04-03 16:00:27 +00:00
SECURITY.md
THIRD-PARTY-NOTICES.txt
activate.ps1
activate.sh
build.cmd
build.ps1 Build aspnetcore for win-arm64 (#19317) 2020-03-06 14:47:29 -08:00
build.sh
clean.cmd
clean.ps1
clean.sh
dockerbuild.sh
global.json [release/3.1] Update dependencies from dotnet/arcade (#20815) 2020-04-14 19:58:09 +00:00
restore.cmd
restore.sh
startvs.cmd

README.md

ASP.NET Core

ASP.NET Core is an open-source and cross-platform framework for building modern cloud based internet connected applications, such as web apps, IoT apps and mobile backends. ASP.NET Core apps run on .NET Core, a free, cross-platform and open-source application runtime. It was architected to provide an optimized development framework for apps that are deployed to the cloud or run on-premises. It consists of modular components with minimal overhead, so you retain flexibility while constructing your solutions. You can develop and run your ASP.NET Core apps cross-platform on Windows, Mac and Linux. Learn more about ASP.NET Core.

Get Started

Follow the Getting Started instructions in the ASP.NET Core docs.

Also check out the .NET Homepage for released versions of .NET, getting started guides, and learning resources.

See the Issue Management Policies document for more information on how we handle incoming issues.

How to Engage, Contribute, and Give Feedback

Some of the best ways to contribute are to try things out, file issues, join in design conversations, and make pull-requests.

Reporting security issues and bugs

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. 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.

These are some other repos for related projects:

Code of conduct

See CODE-OF-CONDUCT