Go to file
Doug Bunting 352ad1a980
Rebrand and update for 5.0.1 (#27406)
* Move to 5.0.1 versions

* Move to GA .NET SDK
- required for some tests to pass

* Remove feeds that won't be needed after 5.0.0 is GA

* Cherry-pick `$(CrossgenOutput)` and Directory.Build.*.in changes from master
- [master] Update dependencies from dotnet/runtime dotnet/efcore (#26788)
    - 219ecd688012
- when project template tests run test assets, need latest shared Fx bits
- hit `BadImageFormatException`s otherwise
    - test projects build against uploaded packages
    - those packages reference the 5.0.1 shared framework
    - the ASP.NET parts of the 5.0.1 shared Fx are `crossgen`ed to target Windows

- Use runtime and ref/ assemblies matching repo in Helix testing
    - add Directory.Build.*.in files based on project template test infrastructure
    - use files as import boundary where the project doesn't create its own Directory.Build.* files
    - ensure `dotnet-watch` tests also use the latest runtime and ref/ assemblies

- Extend Helix Directory.Build.* workarounds
    - generate Directory.Build.* files when restoring any projects
    - include generated files in Helix runs needing the latest runtime
    - copy generated files when testing `dotnet-watch` locally
    - include generated content in Microsoft.NET.Sdk.BlazorWebAssembly.IntegrationTests test assets
        - remove duplicate settings from existing Directory.Build.* files
    - ensure shared framework and targeting packs are laid out under .dotnet/ before test assets restore

- Disable `crossgen` when building for Helix runs
    - make `$(CrossgenOutput)` property override-able
    - use override in CI jobs that submit to other platforms
        - for now, leave the ARM64 Helix jobs alone (build on Ubuntu, run in Debian)

* Correct an `$(IsTestAssetProject)` setting
- affected projects are all test assets or provide test support
- without this, a number of the projects are incorrectly marked as shipping

* Baseline released 5.0.0 packages
- this is a complete rewrite of eng/Baseline.xml
  - based on the 5.0.0 MergedManifest.xml file

* Add 5.0.0 PackageOverrides.txt and PlatformManifest.txt files
- need consistent versions when servicing targeting packs

Co-authored-by: dotnet-maestro[bot] <42748379+dotnet-maestro[bot]@users.noreply.github.com>
2020-11-10 09:51:47 -08:00
.azure/pipelines Rebrand and update for 5.0.1 (#27406) 2020-11-10 09:51:47 -08:00
.config Update dependencies from https://github.com/dotnet/runtime build 20201029.3 (#27353) 2020-10-29 12:38:54 -07:00
.github
.vscode
docs
eng Rebrand and update for 5.0.1 (#27406) 2020-11-10 09:51:47 -08:00
src Rebrand and update for 5.0.1 (#27406) 2020-11-10 09:51:47 -08:00
.editorconfig
.gitattributes
.gitignore
.gitmodules
.vsconfig
AspNetCore.sln Remove Microsoft.Components.Web.Extensions (#26256) (#26298) 2020-09-25 12:14:56 -07:00
CODE-OF-CONDUCT.md
CONTRIBUTING.md
Directory.Build.props Fix Helix testing issues with stable versions and local builds (#25865) 2020-09-13 21:45:23 -07:00
Directory.Build.targets [release/5.0] Target 5.0.0 shared framework in global tools (#27599) 2020-11-10 09:46:06 -08:00
LICENSE.txt
NuGet.config Rebrand and update for 5.0.1 (#27406) 2020-11-10 09:51:47 -08:00
README.md
SECURITY.md
THIRD-PARTY-NOTICES.txt Add Swashbuckle to Third-Party-Notices.txt (#26012) 2020-09-17 13:19:55 -07:00
activate.ps1
activate.sh
build.cmd
build.ps1 Enable ARM64 installers build. (#25579) 2020-09-10 10:59:37 -07:00
build.sh
clean.cmd
clean.ps1
clean.sh
dockerbuild.sh
global.json Rebrand and update for 5.0.1 (#27406) 2020-11-10 09:51:47 -08: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