![]() ![]() ![]() The first step in optimizing the performance of your code is to know where to make improvements. ![]() If you like what you see in this blog post, please join our Visual Studio Performance Tools Community to stay up-to-date and help steer future features. Although we show ASP.NET in this post, these tools also work when debugging Windows desktop applications and C#/VB/C++ universal Windows applications that target desktop. Without leaving your debugging workflow, these tools let you quickly answer questions like “how is my memory footprint?” “what is using all this memory?”, “should I be concerned about the performance of this code?”, and “why is this so slow?”. In this post we’ll look at how using the debugger-integrated performance and memory tools in Visual Studio 2015 Update 1. So why not bring that task little closer to you? Would you like to learn how to make your code run faster, use less memory, or just find out whether your code has a CPU or memory issue? Of course you would-you’re a developer! But then, memory and performance tuning often suffers from the pitfall of being an “important but not urgent” task that you simply can’t seem to get to because of the really urgent stuff. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |