Using Visual Studio 2019, VB .Net.
Looking for the best way to time sections of code to find a the exact code causing new delays running a command.
These are applications on client workstations running against a a SQL Server database.
I did some tracing and profiling MANY years ago, but wondering if there's a better way today. I want to have minimal to no impact on client performance, while running these checks, if possible, or get a feel for anticipated performance impact.
If there is a significant impact, the quicker I can disable the timing checks, the better.