diff --git a/aspnetcore/index.yml b/aspnetcore/index.yml index b2c10dd261..de8c73e75f 100644 --- a/aspnetcore/index.yml +++ b/aspnetcore/index.yml @@ -152,7 +152,7 @@ conceptualContent: - url: signalr/introduction.md itemType: get-started text: "Create your first SignalR app" - - url: tutorials/signalr-blazor-webassembly.md + - url: tutorials/signalr-blazor.md itemType: tutorial text: "SignalR with Blazor WebAssembly" - url: tutorials/signalr-typescript-webpack.md @@ -407,4 +407,4 @@ additionalContent: - url: /dotnet/architecture/modern-web-apps-azure/development-process-for-azure text: Development process for Azure # footer (optional) - footer: "Contribute to ASP.NET Core docs. Read our [contributor guide](https://github.com/aspnet/AspNetCore.Docs/blob/master/CONTRIBUTING.md)." \ No newline at end of file + footer: "Contribute to ASP.NET Core docs. Read our [contributor guide](https://github.com/aspnet/AspNetCore.Docs/blob/master/CONTRIBUTING.md)." diff --git a/aspnetcore/security/data-protection/implementation/key-storage-providers.md b/aspnetcore/security/data-protection/implementation/key-storage-providers.md index 06b846f0bd..2999c32ee6 100644 --- a/aspnetcore/security/data-protection/implementation/key-storage-providers.md +++ b/aspnetcore/security/data-protection/implementation/key-storage-providers.md @@ -42,7 +42,7 @@ public void ConfigureServices(IServiceCollection services) } ``` -If the web app is running as an Azure service, connection string can be used to authenticate to Azure storage by using [Azure.Storage.Blobs](https://docs.microsoft.com/dotnet/api/azure.storage.blobs.blobcontainerclient). +If the web app is running as an Azure service, connection string can be used to authenticate to Azure storage by using [Azure.Storage.Blobs](/dotnet/api/azure.storage.blobs.blobcontainerclient). ```csharp string connectionString = ""; @@ -183,4 +183,4 @@ The `DataProtectionKeys` class/entity adopts the structure shown in the followin ## Custom key repository -If the in-box mechanisms aren't appropriate, the developer can specify their own key persistence mechanism by providing a custom [IXmlRepository](/dotnet/api/microsoft.aspnetcore.dataprotection.repositories.ixmlrepository). +If the in-box mechanisms aren't appropriate, the developer can specify their own key persistence mechanism by providing a custom [IXmlRepository](/dotnet/api/microsoft.aspnetcore.dataprotection.repositories.ixmlrepository). \ No newline at end of file diff --git a/aspnetcore/tutorials/build-a-blazor-app.md b/aspnetcore/tutorials/build-a-blazor-app.md index 98b02b51e6..83c5e86df2 100644 --- a/aspnetcore/tutorials/build-a-blazor-app.md +++ b/aspnetcore/tutorials/build-a-blazor-app.md @@ -100,7 +100,7 @@ At the end of this tutorial, you'll have a working todo list app. Save the `Shared/NavMenu.razor` file. -1. Build and run the app by executing the [`dotnet watch run`](/aspnet/core/tutorials/dotnet-watch) command in the command shell from the `TodoList` folder. After the app is running, visit the new Todo page by selecting the **`Todo`** link in the app's navigation bar, which loads the page at `/todo`. +1. Build and run the app by executing the [`dotnet watch run`](xref:tutorials/dotnet-watch) command in the command shell from the `TodoList` folder. After the app is running, visit the new Todo page by selecting the **`Todo`** link in the app's navigation bar, which loads the page at `/todo`. Leave the app running the command shell. Each time a file is saved, the app is automatically rebuilt. The browser temporarily loses its connection to the app while compiling and restarting. The page in the browser is automatically reloaded when the connection is re-established. diff --git a/aspnetcore/tutorials/razor-pages/new-field.md b/aspnetcore/tutorials/razor-pages/new-field.md index bce023f2ae..0590e8067c 100644 --- a/aspnetcore/tutorials/razor-pages/new-field.md +++ b/aspnetcore/tutorials/razor-pages/new-field.md @@ -23,7 +23,7 @@ In this section [Entity Framework](/ef/core/get-started/aspnetcore/new-db) Code When using EF Code First to automatically create a database, Code First: -* Adds an [`__EFMigrationsHistory`](https://docs.microsoft.com/ef/core/managing-schemas/migrations/history-table) table to the database to track whether the schema of the database is in sync with the model classes it was generated from. +* Adds an [`__EFMigrationsHistory`](/ef/core/managing-schemas/migrations/history-table) table to the database to track whether the schema of the database is in sync with the model classes it was generated from. * If the model classes aren't in sync with the database, EF throws an exception. Automatic verification that the schema and model are in sync makes it easier to find inconsistent database code issues. @@ -164,7 +164,7 @@ In this section [Entity Framework](/ef/core/get-started/aspnetcore/new-db) Code When using EF Code First to automatically create a database, Code First: -* Adds an [`__EFMigrationsHistory`](https://docs.microsoft.com/ef/core/managing-schemas/migrations/history-table) table to the database to track whether the schema of the database is in sync with the model classes it was generated from. +* Adds an [`__EFMigrationsHistory`](/ef/core/managing-schemas/migrations/history-table) table to the database to track whether the schema of the database is in sync with the model classes it was generated from. * If the model classes aren't in sync with the database, EF throws an exception. Automatic verification that the schema and model are in sync makes it easier to find inconsistent database code issues. @@ -305,7 +305,7 @@ In this section [Entity Framework](/ef/core/get-started/aspnetcore/new-db) Code When using EF Code First to automatically create a database, Code First: -* Adds an [`__EFMigrationsHistory`](https://docs.microsoft.com/ef/core/managing-schemas/migrations/history-table) table to the database to track whether the schema of the database is in sync with the model classes it was generated from. +* Adds an [`__EFMigrationsHistory`](/ef/core/managing-schemas/migrations/history-table) table to the database to track whether the schema of the database is in sync with the model classes it was generated from. * If the model classes aren't in sync with the database, EF throws an exception. Automatic verification that the schema and model are in sync makes it easier to find inconsistent database code issues. @@ -430,4 +430,4 @@ Run the app and verify you can create/edit/display movies with a `Rating` field. > [Previous: Add Search](xref:tutorials/razor-pages/search) > [Next: Add Validation](xref:tutorials/razor-pages/validation) -::: moniker-end +::: moniker-end \ No newline at end of file diff --git a/aspnetcore/tutorials/razor-pages/sql.md b/aspnetcore/tutorials/razor-pages/sql.md index 09327dc89f..d8711fb0df 100644 --- a/aspnetcore/tutorials/razor-pages/sql.md +++ b/aspnetcore/tutorials/razor-pages/sql.md @@ -124,7 +124,7 @@ In the previous code, the `Main` method has been modified to do the following: * Get a database context instance from the dependency injection container. * Call the `seedData.Initialize` method, passing to it the database context instance. -* Dispose the context when the seed method completes. The [using statement](https://docs.microsoft.com/dotnet/csharp/language-reference/keywords/using-statement) ensures the context is disposed. +* Dispose the context when the seed method completes. The [using statement](/dotnet/csharp/language-reference/keywords/using-statement) ensures the context is disposed. The following exception occurs when `Update-Database` has not been run: @@ -278,7 +278,7 @@ In the previous code, the `Main` method has been modified to do the following: * Get a database context instance from the dependency injection container. * Call the `seedData.Initialize` method, passing to it the database context instance. -* Dispose the context when the seed method completes. The [using statement](https://docs.microsoft.com/dotnet/csharp/language-reference/keywords/using-statement) ensures the context is disposed. +* Dispose the context when the seed method completes. The [using statement](/dotnet/csharp/language-reference/keywords/using-statement) ensures the context is disposed. The following exception occurs when `Update-Database` has not been run: @@ -422,7 +422,7 @@ In the previous code, the `Main` method has been modified to do the following: * Get a database context instance from the dependency injection container. * Call the `seedData.Initialize` method, passing to it the database context instance. -* Dispose the context when the seed method completes. The [using statement](https://docs.microsoft.com/dotnet/csharp/language-reference/keywords/using-statement) ensures the context is disposed. +* Dispose the context when the seed method completes. The [using statement](/dotnet/csharp/language-reference/keywords/using-statement) ensures the context is disposed. A production app would not call `Database.Migrate`. It's added to the preceding code to prevent the following exception when `Update-Database` has not been run: @@ -469,4 +469,4 @@ The next tutorial will clean up the presentation of the data. > [Previous: Scaffolded Razor Pages](xref:tutorials/razor-pages/page) > [Next: Update the pages](xref:tutorials/razor-pages/da1) -::: moniker-end +::: moniker-end \ No newline at end of file