Getting own filename

[PIEBALDconsult]

Yes, of course. OK, here's what I use: System.Windows.Forms.Application.ExecutablePath and sometimes I pass that through System.IO.Path.GetFileNameWithoutExtension()

modified on Thursday, January 22, 2009 10:40 PM

[Lost User]

PIEBALDconsult wrote:

Yes, of course.

:laugh:

Why is common sense not common? Never argue with an idiot. They will drag you down to their level where they are an expert. Sometimes it takes a lot of work to be lazy Individuality is fine, as long as we do it together - F. Burns

[_Superman_]

Get the current process using Process.GetCurrentProcess() Then use the ProcessName or MainModule property.

«_Superman_»

[PIEBALDconsult]

I don't think that'll work reliably.

[_Superman_]

You mean, we would not always get the filename ?

«_Superman_»

[vaghelabhavesh]

You can use Assembly.GetExecutingAssembly().GetName() in .Net and if you want file path then you can use this one[^]

[PIEBALDconsult]

Is there a guarantee that the process name is the filename? On the other hand I just tried it and it seems to be reliable. At least it knows if I change the file name. I may need to look into it further.

[_Superman_]

I guess you might as well you the GetModuleFileName API

«_Superman_»

[PIEBALDconsult]

If main calls a library routine in another assembly and that routine does that, you'll get the name of the library assembly, not the assembly containing main.

[PIEBALDconsult]

That may have a problem if called from a different assembly? I guess stick with System.Diagnostics.Process.GetCurrentProcess().MainModule.FileName. I suppose might System.Windows.Forms.Application.ExecutablePath call that.