In the rest of this blog post, we’ll measure the performance impact of using the Snapshot Debugger against a live app with a quick case study using performance load testing. Snapshot Debugging has almost no performance impact on the performance of your production service or the experience end users see while using your application. Additionally, you can capture snapshots automatically when exceptions happen in your app by setting up Application Insights.
Ac snapshot studio professional code#
You can capture snapshots at specified lines of code in by using Snappoints, as shown below. You can read a further overview of how the Snapshot Debugger can be used effectively in production here. This means that you can debug the actual live, running app, without impacting the experience your customers have while using the app. While traditional breakpoints would halt your live server when hit and stop it from serving requests Snappoints quickly capture state, including locals, watches, and the call stack while your app continues to run. The Snapshot Debugger works by taking a snapshot of the state of your app at specified lines of code where you set Snappoints. The Snapshot Debugger enables a safe, non-invasive way for you to use the Visual Studio debugger you know and love directly against the production environment in Azure where the issue is happening. Often, the logs may be insufficient, or a local repro may be hard if not impossible to setup. If an issue happens in production, you may find yourself digging through logs or attempting to repro the issue in a local environment.
With the general availability of Visual Studio 2017 Enterprise 15.5 this week, Snapshot Debugger is now available for you to get started. Earlier this year we previewed the Snapshot Debugger, a tool that enables you to debug web apps running in production in Azure.
0 kommentar(er)
