Unable to profile tests in Visual Studio 2013 when assembly path contains spaces
profiling, visual-studio-2013
Solution
So it turns out the problem is that if any of the assemblies that you hope to instrument over have spaces in their names, the "Profile Test" option fails to instrument them, which in turn means that no data is collected (because "Profile Test" appears to only use Instrumentation).
Obviously the workaround is to just not have assemblies with spaces in their names.
I logged a bug on Microsoft Connect.
Problem
Whenever I try to profile a test in Visual Studio 2013, by Right-Clicking on the test in Test Explorer, and selecting the "Profile Test" option, the test successfully executes (and passes), but the performance analysis fails with the following messages. ``` File contains no data buffers File contains no data buffers Analysis failed ``` I am using Windows 7 64. I can successfully profile the application itself (both Instrumentation and Sampling) with no problems.