63baa06482
Using Browser.Exists is equivalent to Browser.FindElement except it provides better logs and diagnostics when the assertion fails. The additional waits will also rule out failures due to the browser taking time to update possibly improving stability. I looked at the implementation of WebDriverWait to verify that using it will not introduce additional delays to our tests. |
||
|---|---|---|
| .. | ||
| Analyzers | ||
| Authorization | ||
| Components | ||
| Forms | ||
| Ignitor | ||
| ProtectedBrowserStorage/src | ||
| Samples/BlazorServerApp | ||
| Server | ||
| Shared | ||
| Web | ||
| Web.JS | ||
| WebAssembly | ||
| benchmarkapps | ||
| test | ||
| .vsconfig | ||
| Components.slnf | ||
| ComponentsNoDeps.slnf | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| NuGetPackageVerifier.json | ||
| README.md | ||
| THIRD-PARTY-NOTICES.txt | ||
| build.cmd | ||
| build.sh | ||
| startvs.cmd | ||
README.md
Blazor
Build modern, interactive web-based UIs with C# and Razor.
This folder contains the underlying components programming model that powers both server-side and client-side Blazor applications.
Blazor is a component based web UI framework. Blazor apps can run client-side in browser on WebAssembly or server-side as part of an ASP.NET Core app. Blazor is a full single-page application (SPA) framework inspired by the latest JavaScript SPA frameworks, featuring support for offline/PWA applications, app size trimming, and browser-based debugging.
Blazor uses only the latest web standards. No plugins or transpilation needed. It runs in the browser on a real .NET runtime implemented in WebAssembly that executes normal .NET assemblies.
You can learn more about Blazor at https://blazor.net.
Getting Started
To get started with Blazor and build your first web app check out our getting started guide.