1 Reply Latest reply on Nov 3, 2011 4:42 AM by Peacekeeper

    MS Visual Studio 2010 -- "save" results in "debug" remaining deactivated for about a minute

      I've been using MS Visual Studio 2010 (specifically C#).  Whenever I do a save to the source code, I'm unable

      to run the debug command for about a minute.  This just started several days ago after reinstalling McAfee

      Security Center because of a "real-time scanning" bug (it kept deactivating).


      When I check the processes via Task Manager, mcshield.exe zooms up with respect to the processor cycles.

      My impression is that McAfee is checking to see if the Visual Studio debugger is going "rogue".