From 9cee73bc6142fcd0d28700e1bf48d54bcb217041 Mon Sep 17 00:00:00 2001 From: Genevieve Warren <24882762+gewarren@users.noreply.github.com> Date: Tue, 9 Mar 2021 16:45:04 -0800 Subject: [PATCH 1/3] fix broken links --- .../dapr-for-net-developers/dapr-at-20000-feet.md | 1 - .../architecture/dapr-for-net-developers/observability.md | 8 ++++---- .../dapr-for-net-developers/publish-subscribe.md | 2 +- .../azure-key-vault-protects-secrets.md | 3 --- .../example-migration-eshop.md | 2 +- docs/core/additional-tools/vscode-dotnet-runtime.md | 2 +- docs/core/migration/20-21.md | 2 +- docs/core/tutorials/netcore-hosting.md | 2 +- docs/fsharp/tools/fsharp-interactive/index.md | 2 +- docs/standard/components.md | 2 +- .../core-changes/msbuild/2.1/dotnetclitoolreference.md | 2 +- 11 files changed, 12 insertions(+), 16 deletions(-) diff --git a/docs/architecture/dapr-for-net-developers/dapr-at-20000-feet.md b/docs/architecture/dapr-for-net-developers/dapr-at-20000-feet.md index ac38efebff671..b79583d9e26af 100644 --- a/docs/architecture/dapr-for-net-developers/dapr-at-20000-feet.md +++ b/docs/architecture/dapr-for-net-developers/dapr-at-20000-feet.md @@ -150,7 +150,6 @@ At the time of this writing, the following component types are provided by Dapr: | [Bindings](https://github.com/dapr/components-contrib/tree/master/bindings) | Provides a uniform interface to trigger application events from external systems and invoke external systems with optional data payloads. | | [Middleware](https://github.com/dapr/components-contrib/tree/master/middleware) | Allows custom middleware to plug into the request processing pipeline and invoke additional actions on a request or response. | | [Secret stores](https://github.com/dapr/components-contrib/tree/master/secretstores) | Provides a uniform interface to interact with external secret stores, including cloud, edge, commercial, open-source services. | -| [Tracing exporters](https://github.com/dapr/components-contrib/tree/master/exporters) | Provides a uniform interface to open telemetry wrappers. | As the jet completes its fly over of Dapr, you look back once more and can see how it connects together. diff --git a/docs/architecture/dapr-for-net-developers/observability.md b/docs/architecture/dapr-for-net-developers/observability.md index 2552e43397681..4463cbadf6e9a 100644 --- a/docs/architecture/dapr-for-net-developers/observability.md +++ b/docs/architecture/dapr-for-net-developers/observability.md @@ -35,7 +35,7 @@ As Dapr abstracts away the plumbing, the application is unaware of how observabi Dapr's [sidecar architecture](dapr-at-20000-feet.md#sidecar-architecture) enables built-in observability features. As services communicate, Dapr sidecars intercept the traffic and extract tracing, metrics, and logging information. Telemetry is published in an open standards format. By default, Dapr supports [OpenTelemetry](https://opentelemetry.io/) and [Zipkin](https://zipkin.io/). -Dapr provides [collectors](https://docs.dapr.io/operations/monitoring/open-telemetry-collector/) that can publish telemetry to different back-end monitoring tools. These tools present Dapr telemetry for analysis and querying. Figure 9-1 shows the Dapr observability architecture: +Dapr provides [collectors](https://docs.dapr.io/operations/monitoring/tracing/open-telemetry-collector/) that can publish telemetry to different back-end monitoring tools. These tools present Dapr telemetry for analysis and querying. Figure 9-1 shows the Dapr observability architecture: ![Dapr observability architecture](media/observability/observability-architecture.png) @@ -280,7 +280,7 @@ Dapr generates a large set of metrics for Dapr system services and its runtime. | dapr_http_server_request_count | Runtime | Number of HTTP requests started in an HTTP server. | | dapr_http/client/sent_bytes | Runtime | Total bytes sent in request body (not including headers) by an HTTP client. | -For more information on available metrics, see the [Dapr metrics documentation](https://docs.dapr.io/developing-applications/building-blocks/observability/metrics). +For more information on available metrics, see the [Dapr metrics documentation](https://docs.dapr.io/operations/monitoring/metrics/). #### Configure Dapr metrics @@ -307,7 +307,7 @@ With the Prometheus scraper collecting and publishing metrics into the monitorin ![Grafana dashboard displaying Dapr system services metrics](media/observability/grafana-sample.png) -The Dapr documentation includes a [tutorial for installing Prometheus and Grafana](https://docs.dapr.io/operations/monitoring/grafana/). +The Dapr documentation includes a [tutorial for installing Prometheus and Grafana](https://docs.dapr.io/operations/monitoring/metrics/grafana/). ### Logging @@ -376,7 +376,7 @@ helm install dapr dapr/dapr --namespace dapr-system --set global.logAsJson=true #### Collect logs -The logs emitted by Dapr can be fed into a monitoring back end for analysis. A log collector is a component that collects logs from a system and sends them to a monitoring back end. A popular log collector is [Fluentd](https://www.fluentd.org/). Check out the [How-To: Set up Fluentd, Elastic search and Kibana in Kubernetes](https://docs.dapr.io/operations/monitoring/fluentd/) in the Dapr documentation. This article contains instructions for setting up Fluentd as log collector and the [ELK Stack](https://www.elastic.co/elastic-stack) (Elastic Search and Kibana) as a monitoring back end. +The logs emitted by Dapr can be fed into a monitoring back end for analysis. A log collector is a component that collects logs from a system and sends them to a monitoring back end. A popular log collector is [Fluentd](https://www.fluentd.org/). Check out the [How-To: Set up Fluentd, Elastic search and Kibana in Kubernetes](https://docs.dapr.io/operations/monitoring/logging/fluentd/) in the Dapr documentation. This article contains instructions for setting up Fluentd as log collector and the [ELK Stack](https://www.elastic.co/elastic-stack) (Elastic Search and Kibana) as a monitoring back end. ### Health status diff --git a/docs/architecture/dapr-for-net-developers/publish-subscribe.md b/docs/architecture/dapr-for-net-developers/publish-subscribe.md index 6ad0af17e0b6c..c8be0891bc83a 100644 --- a/docs/architecture/dapr-for-net-developers/publish-subscribe.md +++ b/docs/architecture/dapr-for-net-developers/publish-subscribe.md @@ -288,7 +288,7 @@ You have to specify several elements with every subscription: ## Reference application: eShopOnDapr -The accompanying [eShopOnDapr](https://github.com/dotnet-architecture/eShopOnDapr) app provides an end-to-end reference architecture for constructing a microservices application implementing Dapr. eShopOnDapr is an evolution of the widely popular [eShopOnContainers](https://github.com/dotnet-architecture/eShopOnContainer) app, created several years ago. Both versions use the pub/sub pattern for communicating [integration events](https://devblogs.microsoft.com/cesardelatorre/domain-events-vs-integration-events-in-domain-driven-design-and-microservices-architectures/#integration-events) across microservices. Integration events include: +The accompanying [eShopOnDapr](https://github.com/dotnet-architecture/eShopOnDapr) app provides an end-to-end reference architecture for constructing a microservices application implementing Dapr. eShopOnDapr is an evolution of the widely popular [eShopOnContainers](https://github.com/dotnet-architecture/eShopOnContainers) app, created several years ago. Both versions use the pub/sub pattern for communicating [integration events](https://devblogs.microsoft.com/cesardelatorre/domain-events-vs-integration-events-in-domain-driven-design-and-microservices-architectures/#integration-events) across microservices. Integration events include: - When a user checks-out a shopping basket. - When a payment for an order has succeeded. diff --git a/docs/architecture/microservices/secure-net-microservices-web-applications/azure-key-vault-protects-secrets.md b/docs/architecture/microservices/secure-net-microservices-web-applications/azure-key-vault-protects-secrets.md index e881fa2b54020..7685dd020edaf 100644 --- a/docs/architecture/microservices/secure-net-microservices-web-applications/azure-key-vault-protects-secrets.md +++ b/docs/architecture/microservices/secure-net-microservices-web-applications/azure-key-vault-protects-secrets.md @@ -42,9 +42,6 @@ Note that calling `AddAzureKeyVault` requires the application ID that was regist - **Data Protection key management and lifetime in ASP.NET Core** \ [https://docs.microsoft.com/aspnet/core/security/data-protection/configuration/default-settings](/aspnet/core/security/data-protection/configuration/default-settings) -- **Microsoft.Extensions.Configuration** GitHub repository. \ - - >[!div class="step-by-step"] >[Previous](developer-app-secrets-storage.md) >[Next](../key-takeaways.md) diff --git a/docs/architecture/porting-existing-aspnet-apps/example-migration-eshop.md b/docs/architecture/porting-existing-aspnet-apps/example-migration-eshop.md index da9b72c254250..3e167954fb6ea 100644 --- a/docs/architecture/porting-existing-aspnet-apps/example-migration-eshop.md +++ b/docs/architecture/porting-existing-aspnet-apps/example-migration-eshop.md @@ -21,7 +21,7 @@ This chapter demonstrates how to perform many of the upgrade steps by hand. Alte ## Run *ApiPort* to identify problematic APIs -The first step in preparing to migrate is to run the *ApiPort* tool. The tool identifies how many .NET Framework APIs the app calls and how many of these have .NET Standard or .NET Core equivalents. Focus primarily on your own app's logic, not third-party dependencies, and pay attention to `System.Web` dependencies that will need to be ported. The ApiPort tool was introduced in the last chapter on [understanding and updating dependencies](/understand-update-dependencies.md). +The first step in preparing to migrate is to run the *ApiPort* tool. The tool identifies how many .NET Framework APIs the app calls and how many of these have .NET Standard or .NET Core equivalents. Focus primarily on your own app's logic, not third-party dependencies, and pay attention to `System.Web` dependencies that will need to be ported. The ApiPort tool was introduced in the last chapter on [understanding and updating dependencies](understand-update-dependencies.md). After [installing and configuring the *ApiPort* tool](../../standard/analyzers/portability-analyzer.md), run the analysis from within Visual Studio, as shown in Figure 4-2. diff --git a/docs/core/additional-tools/vscode-dotnet-runtime.md b/docs/core/additional-tools/vscode-dotnet-runtime.md index 7ff73c812138d..05a897bb53bcc 100644 --- a/docs/core/additional-tools/vscode-dotnet-runtime.md +++ b/docs/core/additional-tools/vscode-dotnet-runtime.md @@ -27,4 +27,4 @@ For more examples, check out these open source extensions that currently leverag ## Getting started: end users -In general, the end user should not need to interact with the .NET install tool for extension authors at all. If you are having problems with the extension, check out our [troubleshooting page](https://github.com/dotnet/vscode-dotnet-runtime/blob/master/Documentation/troubleshooting.md) or file an issue on our [GitHub](https://github.com/dotnet/vscode-dotnet-runtime/issues). +In general, the end user should not need to interact with the .NET install tool for extension authors at all. If you are having problems with the extension, check out our [troubleshooting page](https://github.com/dotnet/vscode-dotnet-runtime/blob/master/Documentation/troubleshooting-runtime.md) or file an issue on our [GitHub](https://github.com/dotnet/vscode-dotnet-runtime/issues). diff --git a/docs/core/migration/20-21.md b/docs/core/migration/20-21.md index 01e2c93800323..03f40251f3b24 100644 --- a/docs/core/migration/20-21.md +++ b/docs/core/migration/20-21.md @@ -19,7 +19,7 @@ For an overview of the new features in .NET Core 2.1, see [What's new in .NET Co - Remove `` references for tools that are bundled in the .NET Core 2.1 SDK (v 2.1.300 or later). These references include: - - [dotnet-watch](https://github.com/dotnet/aspnetcore/blob/master/src/Tools/dotnet-watch/README.md) (Microsoft.DotNet.Watcher.Tools) + - `dotnet-watch` - [dotnet-user-secrets](https://github.com/dotnet/aspnetcore/blob/master/src/Tools/dotnet-user-secrets/README.md) (Microsoft.Extensions.SecretManager.Tools) - [dotnet-sql-cache](https://github.com/dotnet/aspnetcore/blob/master/src/Tools/dotnet-sql-cache/README.md) (Microsoft.Extensions.Caching.SqlConfig.Tools) - [dotnet-ef](/ef/core/miscellaneous/cli/dotnet) (Microsoft.EntityFrameworkCore.Tools.DotNet) diff --git a/docs/core/tutorials/netcore-hosting.md b/docs/core/tutorials/netcore-hosting.md index 9502ca7c14815..e8b332deaed1b 100644 --- a/docs/core/tutorials/netcore-hosting.md +++ b/docs/core/tutorials/netcore-hosting.md @@ -34,7 +34,7 @@ Keep in mind that the sample hosts are meant to be used for learning purposes, s ## Create a host using `nethost.h` and `hostfxr.h` -The following steps detail how to use the `nethost` and `hostfxr` libraries to start the .NET Core runtime in a native application and call into a managed static method. The [sample](https://github.com/dotnet/samples/tree/master/core/hosting/HostWithHostFxr) uses the `nethost` header and library installed with the .NET SDK and copies of the [`coreclr_delegates.h`](https://github.com/dotnet/runtime/blob/master/src/installer/corehost/cli/coreclr_delegates.h) and [`hostfxr.h`](https://github.com/dotnet/runtime/blob/master/src/native/corehost/hostfxr.h) files from the [dotnet/runtime](https://github.com/dotnet/runtime) repository. +The following steps detail how to use the `nethost` and `hostfxr` libraries to start the .NET Core runtime in a native application and call into a managed static method. The [sample](https://github.com/dotnet/samples/tree/master/core/hosting/HostWithHostFxr) uses the `nethost` header and library installed with the .NET SDK and copies of the [`coreclr_delegates.h`](https://github.com/dotnet/runtime/blob/main/src/native/corehost/coreclr_delegates.h) and [`hostfxr.h`](https://github.com/dotnet/runtime/blob/master/src/native/corehost/hostfxr.h) files from the [dotnet/runtime](https://github.com/dotnet/runtime) repository. ### Step 1 - Load `hostfxr` and get exported hosting functions diff --git a/docs/fsharp/tools/fsharp-interactive/index.md b/docs/fsharp/tools/fsharp-interactive/index.md index 962406d55bf0c..31891e418b5a5 100644 --- a/docs/fsharp/tools/fsharp-interactive/index.md +++ b/docs/fsharp/tools/fsharp-interactive/index.md @@ -131,7 +131,7 @@ You can specify as many package references as you like in a script. > [!NOTE] > There's currently a limitation for scripts that use framework references (e.g.`Microsoft.NET.Sdk.Web` or `Microsoft.NET.Sdk.WindowsDesktop`). Packages like Saturn, Giraffe, WinForms are not available. This is being tracked in issue [#9417](https://github.com/dotnet/fsharp/issues/9417). -For more information, see [package management extensibility and other extensions](https://github.com/dotnet/fsharp/tree/main/src/fsharp/Microsoft.DotNet.DependencyManager). +For more information, see [package management extensibility and other extensions](https://fsharp.github.io/FSharp.Compiler.Service/reference/Microsoft.DotNet.DependencyManager.html). ## Referencing assemblies on disk with F# interactive diff --git a/docs/standard/components.md b/docs/standard/components.md index 72c56646c3c8d..3960d8cdb246b 100644 --- a/docs/standard/components.md +++ b/docs/standard/components.md @@ -100,7 +100,7 @@ Subsequent revisions to the standards have been developed by the TC49-TG2 (C#) a The following official Ecma documents are available for [C#](https://www.ecma-international.org/publications-and-standards/standards/ecma-334/) and the [CLI](https://www.ecma-international.org/publications-and-standards/standards/ecma-335/) ([TR-84](https://www.ecma-international.org/publications-and-standards/technical-reports/ecma-tr-84/)): - **The C# Language Standard (version 5.0)**: [ECMA-334.pdf](https://www.ecma-international.org/wp-content/uploads/ECMA-334_5th_edition_december_2017.pdf) -- **The Common Language Infrastructure**: [ECMA-335.pdf](hhttps://www.ecma-international.org/wp-content/uploads/ECMA-335_6th_edition_june_2012.pdf). +- **The Common Language Infrastructure**: [ECMA-335.pdf](https://www.ecma-international.org/wp-content/uploads/ECMA-335_6th_edition_june_2012.pdf). - **Information Derived from the Partition IV XML File**: [ECMA-084.pdf](https://www.ecma-international.org/publications/files/ECMA-TR/ECMA%20TR-084.pdf) format. The official ISO/IEC documents are available from the ISO/IEC [Publicly Available Standards](https://standards.iso.org/ittf/PubliclyAvailableStandards/) page. These links are direct from that page: diff --git a/includes/core-changes/msbuild/2.1/dotnetclitoolreference.md b/includes/core-changes/msbuild/2.1/dotnetclitoolreference.md index 8c4db95900830..f04a88340372c 100644 --- a/includes/core-changes/msbuild/2.1/dotnetclitoolreference.md +++ b/includes/core-changes/msbuild/2.1/dotnetclitoolreference.md @@ -10,7 +10,7 @@ Tools now included in .NET Core 2.1 SDK: | \ value | Tool | |------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| -| `Microsoft.DotNet.Watcher.Tools` | [dotnet-watch](https://github.com/dotnet/aspnetcore/blob/master/src/Tools/dotnet-watch/README.md) | +| `Microsoft.DotNet.Watcher.Tools` | `dotnet-watch` | | `Microsoft.Extensions.SecretManager.Tools` | [dotnet-user-secrets](https://github.com/dotnet/aspnetcore/blob/master/src/Tools/dotnet-user-secrets/README.md) | | `Microsoft.Extensions.Caching.SqlConfig.Tools` | [dotnet-sql-cache](https://github.com/dotnet/aspnetcore/blob/master/src/Tools/dotnet-sql-cache/README.md) | | `Microsoft.EntityFrameworkCore.Tools.DotNet` | [dotnet-ef](/ef/core/miscellaneous/cli/dotnet) | From 69938dbdb8a4a1ac7670641e98b9eb4eecf0cfd0 Mon Sep 17 00:00:00 2001 From: Genevieve Warren <24882762+gewarren@users.noreply.github.com> Date: Tue, 9 Mar 2021 17:07:34 -0800 Subject: [PATCH 2/3] fix duplicate alt text --- .../framework/install/application-not-started.md | 16 ++++++++-------- ...-to-view-certificates-with-the-mmc-snap-in.md | 2 +- .../automate-training-with-cli.md | 12 ++++++------ 3 files changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/framework/install/application-not-started.md b/docs/framework/install/application-not-started.md index 6c93d86cd8c0d..4258dbc48d6cf 100644 --- a/docs/framework/install/application-not-started.md +++ b/docs/framework/install/application-not-started.md @@ -5,15 +5,15 @@ ms.date: 09/05/2019 --- # Troubleshooting a 'This application could not be started' error message -Applications that are developed for the .NET Framework typically require that a specific version of the .NET Framework be installed on your system. In some cases, you may attempt to run an application without either an installed version or the expected version of the .NET Framework present. This often produces an error dialog box like the following: +Applications that are developed for .NET Framework typically require that a specific version of .NET Framework be installed on your system. In some cases, you may attempt to run an application without either an installed version or the expected version of .NET Framework present. This often produces an error dialog box like the following: ![This application could not be started](media/application-not-started/app-could-not-be-started.png) -This typically indicates one of the following conditions: +This error typically indicates one of the following conditions: - A .NET Framework installation on your system has become corrupted. -- The version of the .NET Framework needed by your application cannot be detected. +- The version of .NET Framework needed by your application cannot be detected. To address this issue so that you can run your application, do the following: @@ -21,11 +21,11 @@ To address this issue so that you can run your application, do the following: 1. If the .NET Framework Repair Tool recommends any additional action, such as those shown in the following figure, select **Next**. - ![Recommended changes](media/application-not-started/repair-tool-recommended-changes.png) + ![Repair tool recommended changes](media/application-not-started/repair-tool-recommended-changes.png) 1. The .NET Framework Repair Tools displays a dialog box shown in the following figure to indicate that changes are complete. Leave the dialog box open while you to try rerun your application. This should succeed if the .NET Framework Repair Tool has identified and corrected a corrupted .NET Framework installation. - ![Recommended changes](media/application-not-started/repair-tool-changes-complete.png) + ![Repair tool changes complete](media/application-not-started/repair-tool-changes-complete.png) 1. If your application runs successfully, select the **Finish** button. Otherwise, select the **Next** button. @@ -33,7 +33,7 @@ To address this issue so that you can run your application, do the following: ![Unable to resolve the problem](media/application-not-started/repair-tool-no-resolution.png) -1. If you still cannot run the application, install the latest version of the .NET Framework supported by your version of Windows, as shown in the following table. +1. If you still cannot run the application, install the latest version of .NET Framework that's supported by your version of Windows, as shown in the following table. |Windows version|.NET Framework installation| |---|---| @@ -49,9 +49,9 @@ To address this issue so that you can run your application, do the following: 1. Attempt to launch the application. -1. In some cases, you may see a dialog box like the following, which asks you to install the .NET Framework 3.5. Select **Download and install this feature** to install the .NET Framework 3.5, then launch the application again. +1. In some cases, you may see a dialog box like the following, which asks you to install .NET Framework 3.5. Select **Download and install this feature** to install .NET Framework 3.5, then launch the application again. - ![Unable to resolve the problem](media/application-not-started/install-3-5.png) + ![Windows Features dialog box suggesting to install .NET Framework 3.5](media/application-not-started/install-3-5.png) ## See also diff --git a/docs/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in.md b/docs/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in.md index 36ff6d3cc4934..e753a3abe90a6 100644 --- a/docs/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in.md +++ b/docs/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in.md @@ -45,7 +45,7 @@ The following procedure demonstrates how to examine the stores on your local dev 6. In the **Add or Remove Snap-in** window, select **OK**. - ![Add certificate snap-in](./media/mmc-certificate-snap-in-selected.png) + ![Add or Remove Snap-ins window with OK button highlighted](./media/mmc-certificate-snap-in-selected.png) 7. Optional: From the **File** menu, select **Save** or **Save As** to save the MMC console file for later use. diff --git a/docs/machine-learning/automate-training-with-cli.md b/docs/machine-learning/automate-training-with-cli.md index 6d2d26a778864..7dddb53eab2c3 100644 --- a/docs/machine-learning/automate-training-with-cli.md +++ b/docs/machine-learning/automate-training-with-cli.md @@ -22,7 +22,7 @@ The ML.NET CLI is a [.NET Core tool](../core/tools/global-tools.md). Once instal As shown in the following figure, it is simple to generate a high quality ML.NET model (serialized model .zip file) plus the sample C# code to run/score that model. In addition, the C# code to create/train that model is also generated, so that you can research and iterate on the algorithm and settings used for that generated "best model". -![image](media/automate-training-with-cli/cli-high-level-process.png "AutoML engine working inside the ML.NET CLI") +![AutoML engine working inside the ML.NET CLI](media/automate-training-with-cli/cli-high-level-process.png) You can generate those assets from your own datasets without coding by yourself, so it also improves your productivity even if you already know ML.NET. @@ -39,7 +39,7 @@ Example of usage (classification scenario): mlnet classification --dataset "yelp_labelled.txt" --label-col 1 --has-header false --train-time 10 ``` -![image](media/automate-training-with-cli/mlnet-classification-powershell.gif) +![ML.NET classification from the command line](media/automate-training-with-cli/mlnet-classification-powershell.gif) You can run it the same way on *Windows PowerShell*, *macOS/Linux bash*, or *Windows CMD*. However, tabular auto-completion (parameter suggestions) won't work on *Windows CMD*. @@ -65,9 +65,9 @@ Here those metrics are summarized grouped by ML task so you can understand the q ### Metrics for Classification models -The following displays the classification metrics list for the top five models found by the CLI: +The following image displays the classification metrics list for the top five models found by the CLI: -![image](media/automate-training-with-cli/cli-multiclass-classification-metrics.png) +![Classification metrics for top five models](media/automate-training-with-cli/cli-multiclass-classification-metrics.png) Accuracy is a popular metric for classification problems, however accuracy isn't always the best metric to select the best model from as explained in the following references. There are cases where you need to evaluate the quality of your model with additional metrics. @@ -77,9 +77,9 @@ To explore and understand the metrics that are output by the CLI, see [Evaluatio A regression model fits the data well if the differences between the observed values and the model's predicted values are small and unbiased. Regression can be evaluated with certain metrics. -You'll see a similar list of metrics for the best top five quality models found by the CLI. In this particular case related to a regression ML task: +You'll see a similar list of metrics for the top five quality models found by the CLI, except in this case, the top five are related to a regression ML task: -![image](media/automate-training-with-cli/cli-regression-metrics.png) +![Regression metrics for top five models](media/automate-training-with-cli/cli-regression-metrics.png) To explore and understand the metrics that are output by the CLI, see [Evaluation metrics for regression](resources/metrics.md#evaluation-metrics-for-regression-and-recommendation). From 7a2e09408ec3c76fec5ba3ee93d8e2545737ceb4 Mon Sep 17 00:00:00 2001 From: Genevieve Warren <24882762+gewarren@users.noreply.github.com> Date: Tue, 9 Mar 2021 17:17:54 -0800 Subject: [PATCH 3/3] Revert "fix duplicate alt text" This reverts commit 69938dbdb8a4a1ac7670641e98b9eb4eecf0cfd0. --- .../framework/install/application-not-started.md | 16 ++++++++-------- ...-to-view-certificates-with-the-mmc-snap-in.md | 2 +- .../automate-training-with-cli.md | 12 ++++++------ 3 files changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/framework/install/application-not-started.md b/docs/framework/install/application-not-started.md index 4258dbc48d6cf..6c93d86cd8c0d 100644 --- a/docs/framework/install/application-not-started.md +++ b/docs/framework/install/application-not-started.md @@ -5,15 +5,15 @@ ms.date: 09/05/2019 --- # Troubleshooting a 'This application could not be started' error message -Applications that are developed for .NET Framework typically require that a specific version of .NET Framework be installed on your system. In some cases, you may attempt to run an application without either an installed version or the expected version of .NET Framework present. This often produces an error dialog box like the following: +Applications that are developed for the .NET Framework typically require that a specific version of the .NET Framework be installed on your system. In some cases, you may attempt to run an application without either an installed version or the expected version of the .NET Framework present. This often produces an error dialog box like the following: ![This application could not be started](media/application-not-started/app-could-not-be-started.png) -This error typically indicates one of the following conditions: +This typically indicates one of the following conditions: - A .NET Framework installation on your system has become corrupted. -- The version of .NET Framework needed by your application cannot be detected. +- The version of the .NET Framework needed by your application cannot be detected. To address this issue so that you can run your application, do the following: @@ -21,11 +21,11 @@ To address this issue so that you can run your application, do the following: 1. If the .NET Framework Repair Tool recommends any additional action, such as those shown in the following figure, select **Next**. - ![Repair tool recommended changes](media/application-not-started/repair-tool-recommended-changes.png) + ![Recommended changes](media/application-not-started/repair-tool-recommended-changes.png) 1. The .NET Framework Repair Tools displays a dialog box shown in the following figure to indicate that changes are complete. Leave the dialog box open while you to try rerun your application. This should succeed if the .NET Framework Repair Tool has identified and corrected a corrupted .NET Framework installation. - ![Repair tool changes complete](media/application-not-started/repair-tool-changes-complete.png) + ![Recommended changes](media/application-not-started/repair-tool-changes-complete.png) 1. If your application runs successfully, select the **Finish** button. Otherwise, select the **Next** button. @@ -33,7 +33,7 @@ To address this issue so that you can run your application, do the following: ![Unable to resolve the problem](media/application-not-started/repair-tool-no-resolution.png) -1. If you still cannot run the application, install the latest version of .NET Framework that's supported by your version of Windows, as shown in the following table. +1. If you still cannot run the application, install the latest version of the .NET Framework supported by your version of Windows, as shown in the following table. |Windows version|.NET Framework installation| |---|---| @@ -49,9 +49,9 @@ To address this issue so that you can run your application, do the following: 1. Attempt to launch the application. -1. In some cases, you may see a dialog box like the following, which asks you to install .NET Framework 3.5. Select **Download and install this feature** to install .NET Framework 3.5, then launch the application again. +1. In some cases, you may see a dialog box like the following, which asks you to install the .NET Framework 3.5. Select **Download and install this feature** to install the .NET Framework 3.5, then launch the application again. - ![Windows Features dialog box suggesting to install .NET Framework 3.5](media/application-not-started/install-3-5.png) + ![Unable to resolve the problem](media/application-not-started/install-3-5.png) ## See also diff --git a/docs/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in.md b/docs/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in.md index e753a3abe90a6..36ff6d3cc4934 100644 --- a/docs/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in.md +++ b/docs/framework/wcf/feature-details/how-to-view-certificates-with-the-mmc-snap-in.md @@ -45,7 +45,7 @@ The following procedure demonstrates how to examine the stores on your local dev 6. In the **Add or Remove Snap-in** window, select **OK**. - ![Add or Remove Snap-ins window with OK button highlighted](./media/mmc-certificate-snap-in-selected.png) + ![Add certificate snap-in](./media/mmc-certificate-snap-in-selected.png) 7. Optional: From the **File** menu, select **Save** or **Save As** to save the MMC console file for later use. diff --git a/docs/machine-learning/automate-training-with-cli.md b/docs/machine-learning/automate-training-with-cli.md index 7dddb53eab2c3..6d2d26a778864 100644 --- a/docs/machine-learning/automate-training-with-cli.md +++ b/docs/machine-learning/automate-training-with-cli.md @@ -22,7 +22,7 @@ The ML.NET CLI is a [.NET Core tool](../core/tools/global-tools.md). Once instal As shown in the following figure, it is simple to generate a high quality ML.NET model (serialized model .zip file) plus the sample C# code to run/score that model. In addition, the C# code to create/train that model is also generated, so that you can research and iterate on the algorithm and settings used for that generated "best model". -![AutoML engine working inside the ML.NET CLI](media/automate-training-with-cli/cli-high-level-process.png) +![image](media/automate-training-with-cli/cli-high-level-process.png "AutoML engine working inside the ML.NET CLI") You can generate those assets from your own datasets without coding by yourself, so it also improves your productivity even if you already know ML.NET. @@ -39,7 +39,7 @@ Example of usage (classification scenario): mlnet classification --dataset "yelp_labelled.txt" --label-col 1 --has-header false --train-time 10 ``` -![ML.NET classification from the command line](media/automate-training-with-cli/mlnet-classification-powershell.gif) +![image](media/automate-training-with-cli/mlnet-classification-powershell.gif) You can run it the same way on *Windows PowerShell*, *macOS/Linux bash*, or *Windows CMD*. However, tabular auto-completion (parameter suggestions) won't work on *Windows CMD*. @@ -65,9 +65,9 @@ Here those metrics are summarized grouped by ML task so you can understand the q ### Metrics for Classification models -The following image displays the classification metrics list for the top five models found by the CLI: +The following displays the classification metrics list for the top five models found by the CLI: -![Classification metrics for top five models](media/automate-training-with-cli/cli-multiclass-classification-metrics.png) +![image](media/automate-training-with-cli/cli-multiclass-classification-metrics.png) Accuracy is a popular metric for classification problems, however accuracy isn't always the best metric to select the best model from as explained in the following references. There are cases where you need to evaluate the quality of your model with additional metrics. @@ -77,9 +77,9 @@ To explore and understand the metrics that are output by the CLI, see [Evaluatio A regression model fits the data well if the differences between the observed values and the model's predicted values are small and unbiased. Regression can be evaluated with certain metrics. -You'll see a similar list of metrics for the top five quality models found by the CLI, except in this case, the top five are related to a regression ML task: +You'll see a similar list of metrics for the best top five quality models found by the CLI. In this particular case related to a regression ML task: -![Regression metrics for top five models](media/automate-training-with-cli/cli-regression-metrics.png) +![image](media/automate-training-with-cli/cli-regression-metrics.png) To explore and understand the metrics that are output by the CLI, see [Evaluation metrics for regression](resources/metrics.md#evaluation-metrics-for-regression-and-recommendation).