Do any microsoft buildtime dependancies C#/C/c++/VB/etc. need to be updated
for the 2007 policy on daylight savings time?
I know the OS needs to be updated but I care now about C libraries, .net
binaries, etc. that microsoft maintains which have coded in them logic
around datetime. e.g. the C# and c++ datetime objects that microsoft
maintains, do these have any logic that needs to be updated reguardless of
the OS being updated? Or is all such functinality 100% derived off the OS so
no library  or development or build time tool updates nessicary?

This is an assumption only, based on my experience with .NET, the time
is always derived from the system. Now saying this, I believe .NET
actually retrieves time information from the bios instead of the OS.
However I could be completely wrong on that. However, the time for
either the OS or bios are all held via the bios, using the clock
"crystal" as it was so fondly referred to many years ago as the actual
timing keeping device to sync, and updated with in the bios. The
"crystal" is just a timing piece, that counts in nano or micro
seconds, I can't remember which, but the actual time for the system is
stored in the bios.

A fun little activity, change the time and or date in Windows. Reboot
and check the time/date in the bios. See if it changes. ;)

To test the daylight saving time, move your date ahead to the new
daylight saving time start day and see if your applications report
back the "right" date/time. Which it should.

Randy

Client Certificate Selection
Books on .net security
Client certificates do not show up installing the last Root Update
Defender has to be turned on every time computer is turned on
Retrieving the private key associated with a certificate
Could not establish secure channel for SSL/TLS.
Impersonation in .NET 2.0
Display of encrypted data
windows defender
DSA signing