ansaurus

Question

Answer 1

+4 A:

try this

Application.ExecutablePath

or

System.Diagnostics.Process.GetCurrentProcess().MainModule.FileName

or

System.Reflection.Assembly.GetExecutingAssembly().Location

Bye.

RRUZ 2009-09-22 15:11:11

Ok, but Application is in System.Windows.Forms. Is this a WinForm app?

Steven Sudit 2009-09-22 15:13:08

Thank you so much for adding my answer.

Steven Sudit 2009-09-22 15:25:44

RRUZ, I think Oplopanax has a good point about using GetEntryAssembly instead of GetExecutingAssembly. Likewise, CodeBase is a better choice than Location, since it doesn't also include the path.

Steven Sudit 2009-09-22 16:04:01

Bye!!

jeffamaphone 2009-09-22 17:02:25

Answer 2

+1 A:

Process.GetCurrentProcess().MainModule

edit

Another way might be to use Environment.GetCommandLineArgs()[0], but I prefer using Process.

Steven Sudit 2009-09-22 15:12:16

Steve must be Process.GetCurrentProcess().MainModule.FileName

RRUZ 2009-09-22 15:30:33

That's not entirely correct: you have a choice between getting the FileName or the ModuleName.

Steven Sudit 2009-09-22 15:45:32

ModuleName Gets the main module for the associated process. not the filename.

RRUZ 2009-09-22 16:18:22

Depending on what you need, that may be more useful.

Steven Sudit 2009-09-22 16:46:12

Answer 3

A:

You should find it in the property: Application.ExecutablePath

Rowland Shaw 2009-09-22 15:12:25

I didn't downvote you, but you might notice that RRUZ provided th is answer before you did.

Steven Sudit 2009-09-22 15:20:31

Ah, But I'd included a link to the documentation, which is why I kept my answer up (and also why he beat me by a few seconds)

Rowland Shaw 2009-09-22 16:25:17

Fine, I'll upvote you to neutrality.

Steven Sudit 2009-09-22 16:46:45

Answer 4

+3 A:

This has been answered before.

From anywhere in your code you could be in an assembly that was loaded by the originating EXE. You also may not have a reference to the Application singleton, so using the Assembly class is your best bet.

Safest way is Assembly.GetEntryAssembly().Location gets the location on the filesystem where the Assembly is currently. If it is shadow copied then this is the Shadow-copy location. If it is click-once deployed, then this is a crazy path to a file in the sandbox area.

The original location of the assembly will be at Assembly.GetEntryAssembly().Codebase

Oplopanax 2009-09-22 15:28:41

In the case of click-once deployment, will the Process method return a useful result?

Steven Sudit 2009-09-22 15:31:46

I am not entirely certain, but I think the Process method will get the name of the clickonce launcher process in much the same way as for a web app it would get the IIS worker process.

Oplopanax 2009-09-22 17:58:40

ansaurus

tags:

views:

answers:

How to get file name of .EXE

related questions