|
Member 8279445 wrote: Can you show an example?
Of what - concatenating the id with the file name - simple string concatenation.
First save the record to the database and get the ID value from the returned value or record,
create the filename string using string.format("{0}{1}",ID,filename) then update the record with the filename string.
There are a number of ways to do this in one transaction in the database if performance is an issue (I have a limited requirement and the extra call to do the update is inconsequential).
Then write the file to the virtual folder or rename the already written file.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
string strImage = "";
if (!File.Exists) (Server.MapPath("D:/Virtual Directory")));
if(FileUpload1.HasFile)
{
strImage = FileUpload1.FileName.ToString();
System.Guid desiredGuid = System.Guid.NewGuid();
FileUpload1.SaveAs (Server.MapPath("D:/Virtual Directory/" + desiredGuid.ToString()));
}
I had something like this but how do I link to the database?
|
|
|
|
|
Ah my mistake - I am so database centric that I assume everyone is.
If you have no requirement to use a database then why do you need it. You need to look at your design requirements. I think you need to look at your design!
What is your goal in uploading images?
Can each user manage their own images (separate folder or prefix with user key)?
Why do you need a GUID in the first place?
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I need to use database to store all the images as well as a virtual directory becuase I need to host to the web in the future. I need GUID to uniquly identified a image so no two images will have the same name.
|
|
|
|
|
You don't need a database just because you want to write a web app, they can use the file system too (only within the IIS web root but that is fine).
|
|
|
|
|
|
Uh, just use the System.IO classes like you would in a normal application, and make sure that you're looking in a folder for which you have set up permissions,
|
|
|
|
|
Ok so I was right, you need a record in the database with the filename and the filename needs to unique across multiple users - therefore the GUID (or in my case the numeric ID).
It still comes down to design of your app. Your user needs to be able to decide if he wants to manage an existing image and selects that image from a list/control in which case YOU know the record (you used it to populate the control/list) or upload a new image. Change you viewpoint from the user magicking in an image to managing your data.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I'm letting the users to upload the image so I need to store it in the virtual directory as well as the database. But there is error with my virtual directory -
'D:/Virtual Directory is a physical path, but a virtual path was expected.
if (@File.Exists(Server.MapPath("D:/Virtual Directory")))
How do I solve this error?
|
|
|
|
|
Greeting Gurus,
More fun with datetime...
The question:
How do you convert the string 20110325 to a datetime with a "yyyy-mm-dd" format?
The goal:
Convert a retrieved string value into a datetime for insertion in to a sql db.
The output:
20110325
System.FormatException: String was not recognized as a valid DateTime (etc.)
The code:
RegistryKey Regkey = Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall");
{
if (Regkey != null)
{
foreach (string subKeyName in Regkey.GetSubKeyNames())
{
RegistryKey subKey = Regkey.OpenSubKey(subKeyName);
string oDate = subKey.GetValue("InstallDate",String.Empty).ToString();
Console.WriteLine(oDate);
DateTime nDate = DateTime.Parse(oDate);
if (!String.IsNullOrEmpty(oDate))
{
Console.WriteLine(nDate.ToShortDateString());
}
subKey.Close();
}
Regkey.Close();
}
}
If I use
DateTime nDate;
nDate = DateTime.TryParse(oDate, out nDate);
I get "Cannot implicitly convert type 'bool' to 'System.DateTime'"
I have also tried the TryParseExact & ParseExact methods and met with failure.
|
|
|
|
|
CCodeNewbie wrote: If I use
DateTime nDate;
nDate = DateTime.TryParse(oDate, out nDate);
I get "Cannot implicitly convert type 'bool' to 'System.DateTime'"
I have also tried the TryParseExact & ParseExact methods and met with
failure.
That's because TryParse returns a bool => true on success and false otherwise.
Use something like
bool b = DateTime.TryParse(oDate, out nDate);
Then you'll have the value in nDate cause it's an out parameter.
All the best,
Dan
|
|
|
|
|
Hi Dan,
I had tried something similar...
DateTime nDate;
bool b = DateTime.TryParse(oDate, out nDate);
{
Console.WriteLine(nDate);
}
but the dates are converted to 01/01/0001.
I am currently thinking I need to format oDate first...
|
|
|
|
|
You may need to use this method[^] which allows you to tell the parser the format of the string.
|
|
|
|
|
Hi Richard,
Same problem. Dates show as 01/01/0001 00:00:00.
RegistryKey subKey = Regkey.OpenSubKey(subKeyName);
string oDate = subKey.GetValue("InstallDate", String.Empty).ToString();
CultureInfo culture;
DateTimeStyles styles;
DateTime nDate;
culture = CultureInfo.InstalledUICulture;
styles = DateTimeStyles.None;
DateTime.TryParse(oDate, culture, styles, out nDate);
Console.WriteLine(nDate);
|
|
|
|
|
I used:
culture = CultureInfo.CurrentCulture;
styles = DateTimeStyles.AssumeLocal;
but I also had to ensure the date was in the format of the local style. If you wish to use a non-standard representation of the date then you need to provide your own implementation of the IFormatProvider[^] interface.
Alternatively, since you know this date is YYYYMMDD you could just split it into its constituent parts and recreate it in the default format for your culture.
|
|
|
|
|
Either use the method as Richard said or make up your own conversion logic,
given that you know that the date in string fromat will always be like "YYYYMMDD" or what have you.
All the best,
Dan
|
|
|
|
|
If you know you are always going to get back date in a particular format, though as a string, for e.g. 20110325, you can insert date separators on your own.
Simply insert separators at the end of the fourth and sixth character and then you can use Convert.ToDate, TryParse or any other method you like on this string.
|
|
|
|
|
As it represents a date/time, it should be a DateTime type. Please don't advise people to perform string operations on objects that represent numbers, DateTime.Parse/TryParse/ParseExact/TryParseExact are easy enough to do it right.
|
|
|
|
|
You can also use the ParseExact[^] method for which you can specify the date format of the string to be parsed.
CultureInfo provider = CultureInfo.InvariantCulture;
DateTime.ParseExact(oDate, "yyyyMMdd", provider);
0100000101101110011001000111001011101001
|
|
|
|
|
Snap!
There is also TryParseExact as well.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
Something else I've learned today. 
|
|
|
|
|
I hope the other was rather more interesting! 
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
It would struggle to be less so! 
|
|
|
|
|
Hi André
Tried that too... "01/01/0001".
I think the problem is that the parser doesn't recognise 20110325 as a date
If I do this
DateTimeFormatInfo myDTFI = new DateTimeFormatInfo();
myDTFI.DateSeparator = string.Empty;
myDTFI.FullDateTimePattern = "yyyymmdd";
string oDate = subKey.GetValue("InstallDate", String.Empty).ToString();
DateTime nDate = DateTime.ParseExact(oDate,"yyyymmdd", null);
Console.WriteLine(oDate);
Console.WriteLine(nDate);
I get this
20110325
25/01/2011 00:03:00
System.FormatException: String was not recognized as a valid DateTime.
|
|
|
|
|
Use 'MM' instead of 'mm'.
'MM' is for months and 'mm' is for minutes.
0100000101101110011001000111001011101001
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
