Selecting the “Install Remote Debugger Extension” option will prompt Visual Studio to install the extensions in Azure, which is necessary to view snapshots. The UI experience remains almost identical but now you will be required to select an Azure Storage account to collect your snapshot logs and to share the snapshot collection plan (App Services will also require Azure Storage in Preview 2). Once your VM/VMSS has been set up to host your ASP.NET or ASP.NET Core web application you can open your project in Visual Studio, click on the “Debug->Attach to Snapshot Debugger…” menu item, where you will now be able to select VM/VMSS as shown. However, for developers and organizations that require greater control over of their platform and environment, VMs remain a critical option, and Snapshot Debugger is now fully supported in the latest preview of Visual Studio.
We are excited to announce that in our Visual Studio 2019 Enterprise preview we are expanding Snapshot Debugger support beyond Azure App Services hosting ASP.NET Core and ASP.NET applications to now also include Azure Virtual Machines (VM), Azure Virtual Machine scale sets (VMSS) and Azure Kubernetes Services (AKS)! Azure Virtual Machines/Azure Virtual Machine scale setsįor most PaaS scenarios Azure App Services is more than capable of encapsulating a complete end to end experience. Developers can then attach to these snapshots using Visual Studio and see what’s going on with variables, Locals, Watches and Call Stack windows, all this while the live site continues to serve your customers. When a Snappoint is hit in your production environment, a snapshot is dynamically created without stopping the process. The Snapshot Debugger provides a familiar and powerful debugging experience, allowing developers to set Snappoints and Logpoints in code, similar to debugger breakpoints and tracepoints.
You may also request that a process dump be taken, but that requires perfect timing and some luck to capture the most important details, you also must gauge how your collection strategy might negatively impact performance.
You might consider asking your DevOps team to “turn up” production logging but this relies on you having already anticipated where issues might occur prior to deployment. When an unanticipated issue occurs in production it can be difficult to replicate the exact conditions in your testing environment and almost impossible to do so on your local development machine. When Visual Studio 2017 Enterprise 15.5 became generally available we introduced the Snapshot Debugger, an innovative diagnostic tool that allows developers to quickly and accurately evaluate problems in their Azure production environments without stopping the process and with minimal performance impact.
0 kommentar(er)
