[Mono-bugs] [Bug 333741] [Windows] System.Diagnostics.Process.GetCurrentProcess(). ProcessName returns 'mono' instead of process name

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Nov 5 09:45:36 EST 2007


Dick Porter <dick at novell.com> changed:

           What    |Removed                                         |Added
           Severity|Minor                                           |Enhancement

--- Comment #5 from Dick Porter <dick at novell.com>  2007-11-05 07:45:36 MST ---
I'm not sure it's possible to fix on windows in the general case while we run
applications by executing 'mono foo.exe' - the windows apis only see that
mono.exe is the process.  Using EnumProcessModules doesn't work, because it
only sees the modules (exe and dlls) of the mono process itself, not the loaded
assemblies.  Other suggestions for windows API to investigate would be welcome.
 (On Linux we store the assembly name in the equivalent of the task list,
overwriting 'mono'.)

For the specific "my own process name" case, we can always add a hack that
returns the assembly name of the entry point, as we already know that, but it
won't correspond with what the windows task list says.

Downgrading the severity again to 'Enhancement' until I know more.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list