diff --git a/aspnetcore/blazor/class-libraries.md b/aspnetcore/blazor/class-libraries.md index b1ec371f75..5d21684eda 100644 --- a/aspnetcore/blazor/class-libraries.md +++ b/aspnetcore/blazor/class-libraries.md @@ -5,7 +5,7 @@ description: Discover how components can be included in Blazor apps from an exte monikerRange: '>= aspnetcore-3.0' ms.author: riande ms.custom: mvc -ms.date: 05/01/2019 +ms.date: 05/06/2019 uid: blazor/class-libraries --- # Razor components class libraries @@ -59,7 +59,7 @@ Add Razor component files (*.razor*) to the Razor class library. ## Razor class libraries not supported for client-side apps -In Preview 4, Razor class libraries aren't compatible with Blazor client-side apps. +In ASP.NET Core 3.0 Preview, Razor class libraries aren't compatible with Blazor client-side apps. For Blazor client-side apps, use a Blazor component library created by the `blazorlib` template from a command shell: @@ -71,7 +71,7 @@ Component libraries using the `blazorlib` template can include static files, suc ## Static assets not supported for server-side apps -In Preview 4, Blazor server-side apps can't consume static assets from either a Razor class library (`razorclasslib`) or a Blazor library (`blazorlib`). +In ASP.NET Core 3.0 Preview, Blazor server-side apps can't consume static assets from either a Razor class library (`razorclasslib`) or a Blazor library (`blazorlib`). As a temporary workaround, you can try [BlazorEmbedLibrary](https://www.nuget.org/packages/BlazorEmbedLibrary/). diff --git a/aspnetcore/blazor/get-started.md b/aspnetcore/blazor/get-started.md index 2718790843..9c2e640225 100644 --- a/aspnetcore/blazor/get-started.md +++ b/aspnetcore/blazor/get-started.md @@ -64,9 +64,6 @@ Get started with Blazor: For information on the two Blazor hosting models, server-side and client-side, see . - > [!NOTE] - > Only Blazor client-side is supported on macOS in ASP.NET Core 3.0 Preview 4. For more information, see [Blazor server side: dotnet run fails with InvalidOperationException on MacOS](https://github.com/aspnet/AspNetCore/issues/9402). - 4. Open the *WebApplication1* folder in Visual Studio Code. 5. For a Blazor server-side project, the IDE requests that you add assets to build and debug the project. Select **Yes**. @@ -113,9 +110,6 @@ Get started with Blazor: For information on the two Blazor hosting models, server-side and client-side, see . - > [!NOTE] - > On macOS, use a Blazor client-side app. Blazor server-side isn't supported for macOS on ASP.NET Core 3.0 Preview 4. For more information, see [Blazor server side: dotnet run fails with InvalidOperationException on MacOS](https://github.com/aspnet/AspNetCore/issues/9402). - --- In a browser, navigate to `https://localhost:5001`. diff --git a/aspnetcore/blazor/routing.md b/aspnetcore/blazor/routing.md index 6fd93c110d..c7fad45dbb 100644 --- a/aspnetcore/blazor/routing.md +++ b/aspnetcore/blazor/routing.md @@ -5,7 +5,7 @@ description: Learn how to route requests in apps and about the NavLink component monikerRange: '>= aspnetcore-3.0' ms.author: riande ms.custom: mvc -ms.date: 04/24/2019 +ms.date: 05/06/2019 uid: blazor/routing --- # Blazor routing @@ -59,7 +59,7 @@ The router uses route parameters to populate the corresponding component paramet [!code-cshtml[](common/samples/3.x/BlazorSample/Pages/RouteParameter.razor?name=snippet_RouteParameter&highlight=2,7-8)] -As of Preview 4, optional parameters aren't supported. Two `@page` directives are applied in the previous example. The first permits navigation to the component without a parameter. The second `@page` directive takes the `{text}` route parameter and assigns the value to the `Text` property. +Optional parameters aren't supported for Blazor apps in ASP.NET Core 3.0 Preview. Two `@page` directives are applied in the previous example. The first permits navigation to the component without a parameter. The second `@page` directive takes the `{text}` route parameter and assigns the value to the `Text` property. ## Route constraints