Topic: best practice when using dialog result OK

[Ken Alexander]

Oh, and as another point, you're using a MessageBox in the inner "catch" statement.  That's OK, but it forces the user to hit OK to continue.  Imagine what would happen if the user selected 100 files, and they all start erroring out - the user might have to hit "OK" 100 times before the routine finally exits.

Another point to go along with this is allowing the user to cancel out of the copy.  Depending on the number and size of files, this could take a while.  You might look at copying files/directories using My.Computer.FileSystem namespace.  My.Computer.FileSystem.CopyFile gives options for this.

[It's Alive!]

Don't worry about multiple exit points in .NET... it's got one of them managed stacks 

[Glenn R]

You could also use Path.Combine(string1, string2) as well...

[David Hall]

Thanks eveyone, I will look into the Path options

[Bobby C. Jones]

I recommend using it with wanton abandon

Me too.  But I'm also a huge fan of jump statements.  I do this all the time.

Code: [Select]

   static void Main(string[] args)
    {
      int i = 0;
      loop_begin:
        if (i == 10)
          goto exit;

        Console.WriteLine(i++);
      goto loop_begin;

      exit:
      Console.ReadKey();
    }


[David Hall]