CODEWITHSUNDEEP
c#io
Goober
Goober

Reputation: 13506

C# WriteDirectory Issue

I have an application that writes to a folder on the C:\ drive. The program works fine on my computer, but on another laptop when running the .exe (The other laptop has no visual studio etc.), i get a filenotfoundexception and i cannot pinpoint the line of code where this happens from the error report.

Here is the code for creating the directory (assuming this is the issue)

        try
        {
            WriteDirectory = new DirectoryInfo(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) + @"\SMS Notifier\");
            if (!WriteDirectory.Exists)
                WriteDirectory.Create();
        }
        catch (Exception e)
        {
            throw e;
        }

Any ideas what the problem could be? Should i check for write permission ?!

Help greatly appreciated!

Upvotes: 0

Views: 155

Answers (6)

Steve Cooper
Steve Cooper

Reputation: 21490

My guess is that this isn't the real issue; neither DirectoryInfo.Create nor Directory.CreateDirectory throw a FileNotFoundException.

Best bet is to build the app for debug, then copy the file along with all it's .pdb files; hopefully this'll give you the methods and line numbers in your error message.

You might also consider adding a handler for any unhandled exception; the AppDomain.UnhandledException can be handled so that you can add your own event handler for any unhandled exception running anywhere in the app;

Add something like this to your Main function;

 System.AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(MyHandler);

And then write your own handler for the error;

static void MyHandler(object sender, UnhandledExceptionEventArgs args) {
   Exception e = (Exception) args.ExceptionObject;
   Console.WriteLine("MyHandler caught : " + e.Message);
}

Upvotes: 2

rockeye
rockeye

Reputation: 2773

Is .Net framework installed on the laptop ?

other possibility : the plateform doesn't support this directory. Check compatible plateforms on msdn

Upvotes: 0

Matt Howells
Matt Howells

Reputation: 41276

If you deploy the .pdb files along with your .dlls, you will get line numbers in the exception messages!

Your try..catch block isn't doing anything useful, all it is doing is swallowing the stack trace so you cannot see what is going on! I'd suggest removing the try..catch block entirely.

throw e; causes the stack trace to be lost, use throw; to preserve it.

Also you should use System.IO.Path.Combine() to append the directory root and the sub-directory name, that way you don't have to worry about doing the \'s yourself and possibly making a mistake.

Upvotes: 5

Steve Gilham
Steve Gilham

Reputation: 11277

Using throw; rather than throw e; will preserve the original stack trace in the exception.

Putting a Console.WriteLine(e.ToString()); (or a MessageBox equivalent) in the catch block will output the stack trace then and there (you will want a debug build for most information).

If all else fails, the old standard of trace statements Console.WriteLine("about to do x"); will help -- with the app launched from a command line.

Upvotes: 1

Calanus
Calanus

Reputation: 26307

First thing I might do (for debugging purposes) is to insert a

MessageBox.Show(WriteDirectory.FullName);

before you try and create the directory just to see if that "Special" path is what you think it is!

Upvotes: 1

chugh97
chugh97

Reputation: 9992

Does this path exists on the Laptop?

Environment.SpecialFolder.ApplicationData

Do a debug.writeline on this line like a messagebox.show and see what the path is? Also if the path exists it may be a permissions issue..most likely

Upvotes: 1

Related Questions