I'm a new user of the .NET Memory Profiler, so bear with me.
I have already run the .NET Memory Profiler stand-alone, pointed to my executable, and it runs just fine.
Now I am trying it from within Visual Studio. FYI, the project I am trying to profile is mixed mode - the startup project is a C++ project, though it uses managed code and includes some C# dlls. Anyway, if I create a new project, and on the Launch page of settings, I select "Start target of current Visual Studio project" as the type of process to launch, then when I tell the profiler to "Start using Profile Project", it causes Visual Studio to do a build (which is not needed), but does not actually launch the application.
Is this a known bug, or have I missed something?
SciTech Software AB
Users browsing this forum: Bing [Bot], Google [Bot] and 25 guests