StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODo I just completely misunderstand how to use Visual Studio's 2008 profiler?
text
Body
copied!<p><strong>complaining {</strong></p> <p>I always end up incredibly frustrated when I go to profile my code using Visual Studio 2008's profiler (from the Analyze menu option). It is one of the poorest designed features of VS, in my opinion, and I cringe every time I need use it.</p> <p><strong>}</strong></p> <p>I have a few questions concerning it's use, I'm hoping you guys can give me some pointers :-)</p> <ol> <li>Do you need to have your projects built in Debug or Release to profile them? One dialog (that I have no idea how to get back to) mentioned I should profile under Release. Okay - I do that - when I go to run the code, it tells me I'm missing PDB files. Awesome. So I go back to Debug mode, and I try to run it, and it tells me that half of my projects need to be recompiled with the /PROFILE switch on.</li> <li>Is it possible to profile C++/CLI projects? With the /PROFILE switch on, half of the time I get absolutely no output from my C++/CLI projects.</li> <li>Why, when attempting to profile C# projects, do they show up in the Report under Modules view Name list as 0x0000001, 0x0000002, 0x0000003, etc? Really, VS? Really? You can't take a guess at the names of my modules?</li> <li>For that matter, why are function names reported as 0x0A000011, 0x06000009, 0xA0000068, etc?</li> <li>Why, oh why, does VS rebuild EVERYTHING in the dependency tree of the executable being profiled? It might not be a problem if you have 5-6 projects in your solution, but when you have 70, <strong>it's almost quicker to not even bother with the profiler</strong>.</li> <li>Can you recommend any good guides on using the VS2008 profiler?</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload