Debugging is part of every developer’s routine. Something that is not often talked about is how much time can be wasted trying to find the root cause of a bug. A debugging session typically starts with your best guess of where to put the first breakpoint. You go through the repro steps and hope that your breakpoint is hit before the bug manifests i...

You will often configure an ASP.NET web site to run as an Active Directory (AD) user so that the site can access that user’s network resources (e.g. a file share). This is accomplished by changing the identity of the IIS Application Pool the web site runs under.If you try to use the IntelliTrace Standalone Collector with such an application p...

IntelliTrace in Visual Studio Enterprise comes with support for tracing out of the box. All you have to do is make sure the appropriate IntelliTrace events are enabled in VS settings and IntelliTrace will capture trace statements as events. When you are not using the default Debug.Trace methods and are instead using a custom TraceSource, you don...

As you probably already know, Visual Studio Ultimate offers an enhanced live debugging experience (F5 or Attach) through the use of IntelliTrace. Your application’s execution is recorded by IntelliTrace and you can navigate through time, both backwards and forwards, and examine your code as you normally would during a debugging session by int...