The profiler doesn't seem to work with D apps. I have no idea what could be causing this. Please escalate if you can confirm it's not working for you, and it's not something to do with the VisualD project system?
To reproduce in VS2010 (probably the same in other versions):
Build your project (Release with debug symbols; -release -g ?)
[Analyze] -> 'Launch performance wizard...'
Prompts are obvious from here.
I get the error:
PRF0010: Launch Aborted - Unable to start vsperfmon.exe
Error VSP1712: Invalid File: D:\WinDev\feedback\FeedBack_Release140516(4).vspPRF0025: No data was collected.
It works when I build C apps.
Comment #1 by r.sagitario — 2015-06-26T09:40:51Z
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
Comment #2 by turkeyman — 2015-06-27T09:09:11Z
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
Comment #3 by r.sagitario — 2015-08-05T21:10:59Z
> 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.
Comment #4 by turkeyman — 2015-08-06T10:41:27Z
Understand.
It's probably best we start letting go of 2010 >_<
If only >=2012 wasn't so rubbish!
Comment #5 by r.sagitario — 2015-08-07T12:24:59Z
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".
Comment #6 by turkeyman — 2015-08-09T01:48:01Z
Yup, it's all good. We've recently switched to 2013 at work, and I'm starting to make the change at home too >_<