Go to file
Ryan Nowak 688ab7fc49 Fix dotnet-blazor serve
This wasn't properly forwarding the base path to the configuration.
Basically nothing was setting RemainingArguments. We have a test project
that sets the base path, but it was never used when debugging locally.

I also cleaned this up a bit and changed it to use dotnet exec. This
allow you to debug the CLI and related server pipeline, but has the
tradeoff of not rebuilding.
2019-01-02 00:32:09 -08:00
.azure/pipelines Fix ANCM environment variables bugs (#6083) 2018-12-28 15:48:20 -08:00
.config Suppress false-positives in credential scanning (#4392) 2018-12-04 15:30:47 -08:00
.github
.vscode
build Build Windows Installers using the repo's main build script and repotasks (#6139) 2018-12-31 10:54:15 -08:00
docs Improve InstallVisualStudio.ps1 (#6089) 2018-12-21 14:55:31 -08:00
eng Build Windows Installers using the repo's main build script and repotasks (#6139) 2018-12-31 10:54:15 -08:00
src Fix dotnet-blazor serve 2019-01-02 00:32:09 -08:00
test/Cli.FunctionalTests Restore accidental deletion of common.psm1 2018-12-20 17:34:06 -08:00
.editorconfig
.gitattributes Merge remote-tracking branch 'blazor/stevesa/migration-to-mondorepo' into stevesa/merge-components-repo 2018-11-27 11:29:12 +00:00
.gitignore Merge branch 'release/2.2' 2018-12-14 16:03:16 -08:00
.gitmodules Merge branch 'release/2.2' 2018-12-14 16:03:16 -08:00
CONTRIBUTING.md
Directory.Build.props Build Windows Installers using the repo's main build script and repotasks (#6139) 2018-12-31 10:54:15 -08:00
Directory.Build.targets Merge branch 'release/2.2' 2018-12-21 18:29:32 -08:00
LICENSE.txt
NuGet.config
README.md
THIRD-PARTY-NOTICES.txt Merge branch 'release/2.2' 2018-12-07 11:11:44 -08:00
build.cmd build.cmd/sh changes (#5958) 2018-12-20 16:52:15 -08:00
build.ps1 Build Windows Installers using the repo's main build script and repotasks (#6139) 2018-12-31 10:54:15 -08:00
build.sh build.cmd/sh changes (#5958) 2018-12-20 16:52:15 -08:00
dockerbuild.sh
global.json Merge branch 'release/2.2' 2018-12-14 16:03:16 -08:00
korebuild-lock.txt Merge branch 'release/2.2' 2018-12-14 16:03:16 -08:00
korebuild.json Merge branch 'release/2.2' 2018-12-26 14:21:28 -08:00
restore.cmd build.cmd/sh changes (#5958) 2018-12-20 16:52:15 -08:00
restore.sh build.cmd/sh changes (#5958) 2018-12-20 16:52:15 -08:00
startvs.cmd fix starts.cmd when there is a space in user name (#5963) 2018-12-19 08:09:30 -08:00
version.props Merge branch 'release/2.2' 2018-12-14 16:03:16 -08:00

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 can run on .NET Core or on the full .NET Framework. 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.

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

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.