Go to file
Doug Bunting 1f84e28882
Use `$(TargetFrameworkIdentifier)` and `$(TargetFrameworkVersion)` consistently (#25428)
- always use `$([MSBuild]::VersionXYZ(...))` for version checks
- use `$(NETCoreAppFrameworkIdentifier)` where it's available
- move `$(KnownAppHostPackOrFrameworkReferenceTfm)` setting to Directory.Build.props
  - use it to correct `@(KnownFrameworkReference)` updates
  - metadata of those items still uses `netcoreapp5.0`
  - see also https://github.com/dotnet/efcore/pull/22279#discussion_r478674176

nits:
- do not assume `$(TargetFrameworkVersion)` starts with a 'v'; valid w/o it
- add `$(_IsMicrosoftNETCoreApp20OrOlder)` property in OpenAPI targets file
  - evaluate the `Condition` once instead of three times
2020-08-31 11:36:19 -07:00
.azure/pipelines [release/5.0] Reduce job timeouts in aspnetcore-quarantined-pr pipeline (#25300) 2020-08-26 23:12:48 -07:00
.config Supress security warnings for test keys (#23704) 2020-07-06 09:27:04 -07:00
.github React to runtime release branch rename (#25026) 2020-08-19 01:25:51 +00:00
.vscode Quarantined flaky RazorSDK tests (#22553) 2020-06-04 22:24:23 +00:00
docs Fix invalid Build command (#24771) 2020-08-11 18:27:46 +00:00
eng Use `$(TargetFrameworkIdentifier)` and `$(TargetFrameworkVersion)` consistently (#25428) 2020-08-31 11:36:19 -07:00
src Use `$(TargetFrameworkIdentifier)` and `$(TargetFrameworkVersion)` consistently (#25428) 2020-08-31 11:36:19 -07:00
.editorconfig Enable FxCop Analyzers for the repo (#23709) 2020-07-08 15:26:22 -07:00
.gitattributes Update .gitattributes to include jQuery files (#20537) 2020-06-17 06:17:29 -07:00
.gitignore
.gitmodules
.vsconfig Add .vsconfig files in root and beside slns 2020-03-31 14:25:44 -07:00
AspNetCore.sln InputFile follow-up (#25248) 2020-08-31 09:07:36 -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 Add net461 TFM to netstandard2.0 projects (#25094) 2020-08-27 16:05:40 -07:00
Directory.Build.targets Use `$(TargetFrameworkIdentifier)` and `$(TargetFrameworkVersion)` consistently (#25428) 2020-08-31 11:36:19 -07:00
LICENSE.txt
NuGet.config [master] Update dependencies from dotnet/efcore (#24848) 2020-08-13 02:39:54 +00:00
README.md Added the link to the IssueManagementPolicies document (#24591) 2020-08-05 15:03:59 -07:00
SECURITY.md
THIRD-PARTY-NOTICES.txt Add wireshark logging. Replaces #23088 (#25139) 2020-08-22 03:16:54 +00:00
activate.ps1
activate.sh
build.cmd
build.ps1 Enable `/warnAsError` (#23072) 2020-06-18 15:59:34 -07:00
build.sh Enable `/warnAsError` (#23072) 2020-06-18 15:59:34 -07:00
clean.cmd
clean.ps1
clean.sh
dockerbuild.sh Add additional environment variables to dockerbuild (#23956) 2020-07-15 14:54:04 -07:00
global.json Update dependencies from https://github.com/dotnet/arcade build 20200827.5 (#25373) 2020-08-28 22:18:52 +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 Triage Process 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