You may be not able to use the debugger in Microsoft Visual Studio 2013 Shell (Isolated) applications or Visual Studio 2013 Shell (Integrated) applications.
Applications or implementations (for example, the Microsoft.Build.Utilities.FileTracker class) use the SetDllDirectory("") function. This function unconditionally removes the vsdebugeng.dll registry path. However, the Visual Studio debugger requires the vsdebugeng.dll file to be located on the native load library search path.
To work around this issue, change the registry definition for vsdebugeng.dll file by using the AddDllDirectory function and the SetDefaultDllDirectories function in the WinMain() shell function.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2918446 - Last Review: 26 Dec 2013 - Revision: 1