Re: File Date and Time stamp after FileStream.Write(), C#

It means that what time gets put on the file depends on what filesystem the
file is being stored to. It might be different on a storage card and in the
object store, for example. I seem to remember some traffic about this in a
thread in another group. You might use GoogleGroups advanced groups search
to search all of microsoft.public.windowsce.* for something about file time
stamps being UTC or not...

Paul T.

"Neville Lang" <neville@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eEUJXM7mHHA.3952@xxxxxxxxxxxxxxxxxxxxxxx
Hi Chris,

Thank you for that information. Does that mean that whenever a new file is
created, it always get stamped with the UT time stamp? I felt sure that
newly created files had the time stamp of the local time.

If a new file always gets stamped with UT time, what do I need to do in CF
(or P/Invoke) to change the time to local time when new files are created?

Sorry for these questions but something must have changed recently. I do
not remember having this problem before. This app has been around for over
3 years and I feel sure time stamps were OK previously.

Regards,
Neville Lang



9848 2678
"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message
news:e09Eok6mHHA.4412@xxxxxxxxxxxxxxxxxxxxxxx
The time stamp is handled by the OS's File System Driver, so the CF has
nothing to do with how it gets stamped.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com


"Neville Lang" <neville@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Oe2ykJ0mHHA.960@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I have just noticed in my CF app on a Pocket PC (PPC) that when I create
a new file and write some bytes to it on the PPC using FileStream's
FileMode.CreateNew (and Create), FileAccess.Write, the date and time
stamp displayed in the Modified column in Windows Explorer on the
desktop, accessing the Mobile Device, suggests that the Modified time is
set for UT and not my local time. I have just noticed this and so do not
know whether it has occurred in the past.

I automatically thought that the date and time stamp would use the PPC's
current date and time (I seem to remember that it did so in the past)
but evidently not.

Any ideas?

My app is currently using CFv1 on VS2005. I will be changing it to CFv2
soon.


Regards,
Neville Lang








.

Relevant Pages

  • Re: fsck died with nexit status 8
    ... time of install the system clock is not set in some distros or your ... local time gets set as EST which means that at next boot in terms ... behaving presumably because your local time stamp is now atleast equal ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: File Date and Time stamp after FileStream.Write(), C#
    ... running app tests on my Dell Axim Pocket PC device, ... It has been the memory card installation that has been the change and is ... where I noticed the time stamp differences. ... in device memory uses local time. ...
    (microsoft.public.dotnet.framework.compactframework)
  • File Date and Time stamp after FileStream.Write(), C#
    ... I have just noticed in my CF app on a Pocket PC that when I create a ... new file and write some bytes to it on the PPC using FileStream's ... displayed in the Modified column in Windows Explorer on the desktop, ... I automatically thought that the date and time stamp would use the PPC's ...
    (microsoft.public.dotnet.framework.compactframework)
  • Storing Date/Time with Daylight savings
    ... it will have a Time Stamp column and other columns to save real ... saved in the Time Stamp; I can use either System Time or Local Time; ... Local Time, I can have problems with Daylight saving. ...
    (microsoft.public.dotnet.framework.adonet)
  • convert time string in UTC to time in local time
    ... This was working fine now, but if I do it for a date next week, it breaks because my local time moves to daylight savings time this weekend. ... I'm guessing if I try this next week it will work okay because time.timezone will be give a different value next week - is that correct? ... Is there a direct way to convert that timestamp in UTC to a local time stamp that will always work? ...
    (comp.lang.python)