dotPeek 1.2 EAP: Introducing Process Explorer

Have you ever wanted to dig deeper into a process running on your machine? We have. That’s the reason why the new dotPeek 1.2 EAP build introduces Process Explorer.

The Process Explorer window provides you with the list of all currently running processes and allows decompiling those of them that are .NET processes. Once you locate a process to decompile, you can add it to Assembly Explorer for further investigation by clicking the “+” button. From there, you can export decompiled code to a Visual Studio project if necessary.

Process Explorer window in dotPeek 1.2

You can see native processes in this window as well although you naturally shouldn’t expect dotPeek to be able to decompile them. To display native processes, click Show Native Processes in the Process Explorer toolbar.

To display additional details about a process, for instance the .NET framework version used or MVID (which can be useful to double check that you are going to debug the right application), press F4, which should bring up a tool window displaying process properties.

dotPeek 1.2 Process Properties tool window

In case you’ve missed it, note that dotPeek 1.2 EAP can now work as a symbol server and supply Visual Studio debugger with the information required to debug assembly code. Download dotPeek 1.2 EAP and give it a try!

This entry was posted in dotPeek Tips&Tricks, News and Events and tagged , . Bookmark the permalink.

6 Responses to dotPeek 1.2 EAP: Introducing Process Explorer

  1. Lex Li says:

    Well done. But notice that even native processes, such as Outlook/Visual Studio, can host CLR on their own (even multiple CLR side by side) and then load managed assemblies, so hope in a later build dotPeek can support such native processes as well.

    • Daria Dovzhikova says:

      @Lex,

      Thanks, but native processes that load managed assemblies (such as devenv.exe) are shown in the Process Explorer even if you don’t click “Show Native Processes”.

  2. Lex Li, it seems dotPeek already handles this scenario: VS and Outlook are present in my list with the CLR loaded into it.

    The module list even shows which assemblies are natively loaded (NGen’d) or domain neutral! Great job, JetBrains.

  3. Pingback: Dew Drop – June 11, 2014 (#1795) | Morning Dew

  4. Joe White says:

    “Process Explorer” seems like an unfortunate choice of name, since many of your users (myself included) also use another tool called Process Explorer.

    • Daria Dovzhikova says:

      @Joe,

      Thank you for pointing on this. Unlike the tool, Process Explorer in dotPeek is just a window and we wanted it to have quite a self-descripting name. We’ll think it over how to avoid possible confusion.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">