i am working in C# with visual studio 2008. can any one help me please ASAP

sridharchanda

i want to save a file/image into folder on the server with an unique filename so, that files with same should not overwrite.

ican store the file/image into file but not with the unique file name ...

ex:- if i got an image file as

jhony.jpg while saving it should save as 1234567J_Jhony.jpg into the folder on a button click

and at the same click the name of the file should go into the database.

tlhintoq

You can check if a file name already exists:

Expand|Select|Wrap|Line Numbers

bool AlreadyExists = System.IO.File.Exists(szFileName);

If it does exist, give it a new name.

cloud255

I normally append a timestamp to the original file name to create unique file names. Something like:

Expand|Select|Wrap|Line Numbers

string newFileName = oldFileName + DateTime.Now.ToString();

This will almost always provide a unique filename, if it fails you can always use the DateTime.Now.Ticks.ToString(), to ensure a unique file name.

tlhintoq

Long ago I created a function called "UniqueName(string FilePath)" that mimic the Windows scheme of:
MyFile.jpg
MyFile(1).jpg
MyFile(2).jpg

It's little more than an incrementing loop:
Does file exist "MyFile(2).jpg"
Yes: increase the suffix. Check again
No: Write a zero k file here to reserve the new name. Return the new name

cloud255

Quote:

Originally Posted by tlhintoq

Long ago I created a function called "UniqueName(string FilePath)" that mimic the Windows scheme of:
MyFile.jpg
MyFile(1).jpg
MyFile(2).jpg

It's little more than an incrementing loop:
Does file exist "MyFile(2).jpg"
Yes: increase the suffix. Check again
No: Write a zero k file here to reserve the new name. Return the new name

Hmmm, how did your execution time compare to the standard Windows version of this functionality? It sure would make my file names more user friendly...

tlhintoq

Quote:

Originally Posted by cloud255

Hmmm, how did your execution time compare to the standard Windows version of this functionality? It sure would make my file names more user friendly...

How does one test the actual speed of how the OS does this? For that matter, I don't know a way to ask the OS for the next available name. So I can only go by how it feels, and it feels fast. Well, as fast Windoze can be expected I guess.

All of my file save functions use the "UniqueFileName" method. More or less to this effect:

Expand|Select|Wrap|Line Numbers

 tlhintoq.GDI.Graphics.Save(Image ImageObjectToSave, String FilePath)

{

      if (MakeDirForFIle(FilePath)) /* return true if folder exists, making if needed */

      {

      string NewFilePath = UniqeFilename(FilePath);//This reserves the name

      switch (System.IO.Path.GetExtension(FilePath).ToLower().TrimStart('.'))

   {

      case "jpg":

         SaveJPG(ImageObjectToSave, NewFilePath);

         break;

      case "bmp"

         // Call bitmap save function

         break;

      case "tga"

         // Call Targa save function

         break;

      }

   }

}

And they seem to be working quite fast. Lets face it, most times there isn't an existing file. How many times is the loop going to execute MOST times? 3 maybe?

cloud255

Quote:

Originally Posted by tlhintoq

And they seem to be working quite fast. Lets face it, most times there isn't an existing file. How many times is the loop going to execute MOST times? 3 maybe?

I really like this approach, I'll play around with it on our systems (we often have dozens of files with the same name) and see if the performance hit is not too bad.

I suppose that I could create some sort of dictionary which will store the 'base' file names ('myImage') and also then the last generated name ('myImage(3)'), which leaves me needing to do only a lookup, string manipulation and insert instead of the loop. But that might be an overkill just to generate unique file names :)

MrMancunian

Quote:

and at the same click the name of the file should go into the database.

If you are going to put it in the database, why don't you return the primary key for that record (which should be unique) and use that as a prefix for your file? That way, you don't have to check if the file already exists.

Steven

tlhintoq

Quote:

Originally Posted by MrMancunian

If you are going to put it in the database, why don't you return the primary key for that record (which should be unique) and use that as a prefix for your file? That way, you don't have to check if the file already exists.

Steven

If you write 5 files, all to the same database, wouldn't they all have the same primary key and thus still be returned with the same name?

cloud255

Quote:

Originally Posted by tlhintoq

If you write 5 files, all to the same database, wouldn't they all have the same primary key and thus still be returned with the same name?

No, primary key is a unique identifier per record (row) in a table. So appending the primary key, or using it as a file name will create a unique name for the entire application. But for this to work you need to design a table specifically for this purpose...

i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

re: i am working in C# with visual studio 2008. can any one help me please ASAP

Similar C# / C Sharp bytes

/bytes/development

/bytes/it

/bytes/about