[Fixed] Hangs on "waiting for profiled process to start"

[gigios]

Hello everyone, this is my first post.

I'm evaluating the ver 4.5 to investigate on memory leaks in my WPF application (exe application).
The problem is that each time I try to start the profiling, in VS2012 or standalone, the profiler show always the progress window with the message "waiting for profiled process to start" and it is not possible to execute the snapshots to profile the memory.

My system is:
- Windows 7 64bit
- Visual Studio 2012 Premium
- The application is forced to build as x86 application (I have tried also with 'Any CPU' without success).

Have you any idea on how solve this problem?

Thanks
(sorry for my english)

[gigios]

I fixed the problem! Sorry for double post but I prefer to put in a separate post the steps used to solve the problem.
During some search in the forum I found a post with the suggestion to remove the installation, I tried this suggestion with success!

1. Close all the Visual Studio instances
2. Close all the .NET Memory Profiler instances
3. Uninstall the .NET Memory Profiler
4. Reboot windows
5. Reinstall the .NET Memory Profiler
6. Enjoy your profiler

Regards
(sorry for my english)

[Andreas Suurkuusk]

OK, it's good that you got it to work. I was going to suggest that you should try to reinstall the profiler, since a failure to connect to a .NET process is usually caused by a failed installation.

[gigios]

Ok! Thanks.