[Issue 12750] VS2010 profiler doesn't seem to work
https://issues.dlang.org/show_bug.cgi?id=12750 --- Comment #6 from Manu --- Yup, it's all good. We've recently switched to 2013 at work, and I'm starting to make the change at home too >_< --
[Issue 12750] VS2010 profiler doesn't seem to work
https://issues.dlang.org/show_bug.cgi?id=12750 Rainer Schuetze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Rainer Schuetze --- IMO VS2013 was a good improvement over VS2012. I haven't worked with VS2015 that much yet, but wasn't overwhelmed when I did... I hope you are fine with closing this bug as "won't fix". --
[Issue 12750] VS2010 profiler doesn't seem to work
https://issues.dlang.org/show_bug.cgi?id=12750 --- Comment #4 from Manu --- Understand. It's probably best we start letting go of 2010 >_< If only >=2012 wasn't so rubbish! --
[Issue 12750] VS2010 profiler doesn't seem to work
https://issues.dlang.org/show_bug.cgi?id=12750 --- Comment #3 from Rainer Schuetze --- > VS2010 I was rather hoping you upgraded in the meantime ;-) I recently tried getting profiling to work in VS2010 (installed in a VM), but that didn't even work for C++ projects. I'll probably won't be able to investigate that further for a VS version that's now superseded by 3 major releases. --
[Issue 12750] VS2010 profiler doesn't seem to work
https://issues.dlang.org/show_bug.cgi?id=12750 --- Comment #2 from Manu --- Okay, behaviour has changed. Now I get: Error VSP1398: The monitor was unable to start the VS performance driver. This driver has been blocked from loading Consider using the /Admin:Driver,Start and /Admin:Security options of VSPerfCmd from an elevated environment. Profiling cannot continue. Error VSP1341: Could not start logging engine. Shutting down. Profiling finished. PRF0010: Launch Aborted - Unable to start vsperfmon.exe Error VSP1712: Invalid File: D:\WinDev\dsignal\dsignal150627(4).vspPRF0025: No data was collected. VS2010 --
[Issue 12750] VS2010 profiler doesn't seem to work
https://issues.dlang.org/show_bug.cgi?id=12750 Rainer Schuetze changed: What|Removed |Added CC||r.sagita...@gmx.de --- Comment #1 from Rainer Schuetze --- I've accidentically hit "Performance and Diagnostics" in VS 2013 and noticed a number of issues with D projects. I've implemented a number of interfaces and properties that makes the Performance Wizard work for D projects. I can't try this in VS2010, but the fixes might help there, too. Check it out in https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.42-beta2 --