C# File Handling: Create file in directory where executable exists

Question

I am creating a standalone application that will be distributed to many users. Now each may place the executable in different places on their machines.
I wish to create a new file in the directory from where the executable was executed. So, if the user has his executable in :

C:\exefile\

The file is created there, however if the user stores the executable in:

C:\Users\%Username%\files\

the new file should be created there.

I do not wish to hard code the path in my application, but identify where the executable exists and create the file in that folder. How can I achieve this?

The user may choose to place the file in a location that requires elevation to access, or maybe place it on a read-only filesystem. That same elevation won't necessarily occur when your program runs. It would be better to place any files you're creating in the appropriate part of the file system. — Damien_The_Unbeliever
– Damien_The_Unbeliever, Commented Aug 15, 2012 at 10:03
Use IsolatedStorage instead...you would be able to access that even with the lowest permissions — Anirudha
– Anirudha, Commented Aug 15, 2012 at 10:15
@Damien_The_Unbeliever: True. I had forgotten to consider that. Tigran's solution incorporates what you suggest. Thanks! And thanks for that pdf too. Quite useful! — darnir
– darnir, Commented Aug 15, 2012 at 10:20

Tigran · Accepted Answer · 2012-08-15 10:37:18Z

30

Never create a file into the directory where executable stays. Especially with the latest OSes available on the market, you can easily jump into the security issues, on file creation. In order to gurantee the file creation process, so your data persistancy too, use this code:

var systemPath = System.Environment.
                             GetFolderPath(
                                 Environment.SpecialFolder.CommonApplicationData
                             );
var complete = Path.Combine(systemPath , "files");

This will generate a path like C:\Documents and Settings\%USER NAME%\Application Data\files folder, where you guaranteed to have a permission to write.

edited Aug 15, 2012 at 10:37

answered Aug 15, 2012 at 10:00

Tigran

62.3k8 gold badges90 silver badges124 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

darnir Over a year ago

Thanks a lot! I had forgotten about the privilege escalation in the new OSes. That solves my problem.

Maifee Ul Asad · Accepted Answer · 2022-09-08 06:59:05Z

13

Just use File.Create:

File.Create("fileName");

This will create file inside your executable program without specifying the full path.

Don't forget to add:

using System.IO;

edited Sep 8, 2022 at 6:59

Maifee Ul Asad

4,68910 gold badges52 silver badges120 bronze badges

answered Aug 15, 2012 at 9:59

Saeed Amiri

22.6k5 gold badges49 silver badges86 bronze badges

4 Comments

Henk Holterman Over a year ago

No, it will be created in the "current folder" which can be changed by the prog.

Saeed Amiri Over a year ago

@HenkHolterman, You are right, but if the OP was able to change the current folder, he never asks this question.

Henk Holterman Over a year ago

It could happen by some lib. Even by using a FileDialog I think.

Steve Smith Over a year ago

If the user has the command prompt open and is in, say, c:\otherdir, and runs "c:\exefile\my.exe", it will create the file in c:\otherdir, not c:\exefile.

Steve Smith · Accepted Answer · 2017-05-10 09:07:35Z

8

You can get the full path to your new file with:

string path = Path.GetDirectoryName(Application.ExecutablePath) + "\\mynewfile.txt"

answered May 10, 2017 at 9:07

Steve Smith

2,2862 gold badges19 silver badges24 bronze badges

Comments

bizl · Accepted Answer · 2012-08-15 10:00:06Z

2

string path;
   path = System.IO.Path.GetDirectoryName( 
      System.Reflection.Assembly.GetExecutingAssembly().GetName().CodeBase );
   MessageBox.Show( path );

http://msdn.microsoft.com/en-us/library/aa457089.aspx

answered Aug 15, 2012 at 10:00

bizl

1,5732 gold badges12 silver badges22 bronze badges

Comments

Ryan Naccarato · Accepted Answer · 2020-06-15 19:12:22Z

2

In modern operating systems, the accepted answer of:

var systemPath = System.Environment.GetFolderPath(
    Environment.SpecialFolder.CommonApplicationData
);
var complete = Path.Combine(systemPath , "files");

will produce a user agnostic path like: "C:\ProgramData\files"

To produce a user-based path similar to: "C:\Documents and Settings\%USER NAME%\Application Data\files"

You should use SpecialFolder.ApplicationData or SpecialFolder.LocalApplicationData instead.

answered Jun 15, 2020 at 19:12

Ryan Naccarato

1,37117 silver badges16 bronze badges

Comments

Chris Brooks · Accepted Answer · 2020-07-07 16:01:31Z

0

I like to give the user the choice. I would default the directory to something like Environment.SpecialFolder.CommonApplicationData and let them read and edit the path at will. If in a console app display the path in help and allow them to pass it via command line argument. This saves them the hassle of hunting for the folder. If they point to a path you cannot write to then you throw the error and let them decide what to do.

answered Jul 7, 2020 at 16:01

Chris Brooks

1

Collectives™ on Stack Overflow

C# File Handling: Create file in directory where executable exists

6 Answers 6

1 Comment

4 Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

1 Comment

4 Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related