Go to file
Ryan Nowak 3cc6e8373b Fail faster in Blazor E2E tests
This change adds a fail-fast mechanism to our E2E tests based on
the browser console. This will fail super hard if an unhandled exception
is thrown.

I think it would be interesting to also see if we could do the same
thing for 404s.

The goal of this change is to make it so that the E2E tests can fail
faster (3-4s) than the 30s timeout in the case that something
catastrophic happens. As a nice side benefit you get to see the
exception message.
2019-08-02 17:23:46 -07:00
.azure/pipelines Revert "Improve components infrastructure (#12145)" (#12679) 2019-07-29 09:03:57 -07:00
.config
.github
.vscode
docs Revert "Improve components infrastructure (#12145)" (#12679) 2019-07-29 09:03:57 -07:00
eng [release/3.0] Update dependencies from 2 repositories (#12815) 2019-08-02 00:47:10 +00:00
src Fail faster in Blazor E2E tests 2019-08-02 17:23:46 -07:00
.editorconfig
.gitattributes
.gitignore Make a no-op change 2019-07-03 10:37:36 -07:00
.gitmodules
CONTRIBUTING.md
Directory.Build.props Remove supposed optimization of local builds 2019-07-16 16:53:52 -07:00
Directory.Build.targets Use Arcade for resx generation (#12179) 2019-07-17 18:31:50 -07:00
LICENSE.txt
NuGet.config Copy souces from Versions.props to NuGet.config 2019-07-10 22:07:27 -07:00
README.md
SECURITY.md
THIRD-PARTY-NOTICES.txt Added Angular 8 license info (#12367) 2019-07-19 21:28:46 -07:00
activate.ps1
activate.sh
build.cmd
build.ps1 Revert "Improve components infrastructure (#12145)" (#12679) 2019-07-29 09:03:57 -07:00
build.sh Revert "Improve components infrastructure (#12145)" (#12679) 2019-07-29 09:03:57 -07:00
clean.cmd
clean.ps1 Change `clean.ps1` (and `clean.cmd`) to restore deleted files after cleaning 2019-07-18 11:21:50 -07:00
clean.sh
dockerbuild.sh
global.json Update SDK to preview7 (#12682) 2019-07-29 10:06:07 -07: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 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.