Instrumentation problems using the IDE for VC++ projects (vs2005 beta2)

I am trying to profile an application that consists of a mix of C# projects and c++ projects (built using /clr). I am specifically trying to see the impact of "thunking" on our application's performance. I have been able to sample short runs of the application, but I am not seeing the kind of information I would like. I was hoping to switch to an instrumentation run.

However, if I use "instrumentation" in the wizard (or later select it manually in the performance session), when I go to launch, I get a dialog box with a message "value does not fall within the expected range". After that the launch button no longer appears in the performance explorer. Is there another step I need to perform Is this a known problem

I was looking at using the command line tools but there is currently no documentation. I was reading one of the team member blogs about using the command line tools for profiling asp.net applications, but I seemed to be missing some context for each of the individual steps. Any recommended links or documents

Answer this question

Instrumentation problems using the IDE for VC++ projects (vs2005 beta2)

Tyax
This is a known issue and it is already fixed. THe "value does not flal within the expected range" error is shown for any C++ project in the UI for instrumentation sessions in Beta 2.

A very easy workaround is: instead of adding the C++ project as a target project, add the binary generated as a target binary. NOTE that with that approach you will need to build the C++ project automatically whenever you change the source. The performance session will not do it automatically.

Thanks for reporting the issue; my guess is it is fixed in July (or later) CTP.

-Munjal
Fábio

Hi Doug,

This sounds like an issue in the IDE, though I haven't seen it before. Can you possibly narrow down the problematic DLLs by pruning the list of instrumented binaries in the session properties

If that doesn't help, you may need to use the command line tools, as you mentioned. How you go about this will depend on what kind of project you're trying to profile. You mentioned ASP.NET, which can be tricky from the command line. If this is a stand-alone application, though, it shouldn't be too much work to get you moving.

As I don't know what links or documents you've already looked at, I'll direct you to the public one that I know of: https://blogs.msdn.com/profiler/archive/2004/07/29/201202.aspx

If you manage to get as far as collecting data, you should be able to go back into the IDE and open the VSP file for analysis. If you don't get this far, holler, and we'll try to sort this out.

One caveat: we've historically had trouble with CLR thunks. The data you get may not address what you're looking for.
Instrumentation problems using the IDE for VC++ projects (vs2005 beta2)

Answer this question