Skip to main content

How to get a valid daylight saving time - Part 2

Intr-un post anterior am povestim putin despre TimeZone si daily light saving. Prin metoda "IsDaylightSavingTime" a unui TimeZoneInfo spuneam ca se poate verifica daca pentru o anumita data avem ora de vara sau de iarna.
Lucrurile se complica putin cand nu cunoastem TimeZoneInfo pe care il are clientul. In acest caz, pe baza orei trebuie sa identificam pe ce time zone se afla clientul. Acest lucru nu se poate determina in totalitate, dar putem identifica un time zone care partial asemanator.
Un obiect de tip TipZoneInfo contine metoda "GetAdjustmentRules" care ne returneaza o lista de reguli care se folosesc pentru a ajusta ora (de exemplu ora de vara sau de iarna). Fiecare regula defineste perioda de inceput si de sfarsit dar din pacate perioada nu este definita la nivel de zi ci doar de luna. De exemplu ni se specifica ca in luna martie se termina perioada in care se aplica regula, dar nu se specifica data exacta cand aceasta se termina.
A doua problema apare in cazul in care aplicatia ruleaza pe un server care are setat time zone-ul pe "Coordinated Universal Time". Pentru acest time zone nu exista ora de vara sau de iarna, din aceasta cauza incercati sa verificati daca ora data este de vara sau de iarna folosind metoda "IsDaylightSavingTime" o sa va trezici cu rezultate ciudate.
In unele cazuri nu avem altceva de facut decat sa ne vazam de ora pe care clientul o trimite si pe baza careia sa obtinem un time zone. Acesta solutie trebuie aplicata doar daca este ultima solutie, deoarece niciodata nu trebuie sa ne bazam pe ora clientului si sa o comparam cu cea a serverului, dar in unele cazuri aceasta este singura optiune.
Pentru a obtine ultima duminica dintr-o luna va recomand sa folositi urmatoarea metoda:
public static DateTime LastDay(this DateTime current, DayOfWeek dayOfWeek)
{
DateTime lastDay = current.Last();
return lastDay.AddDays(Math.Abs(dayOfWeek - last.DayOfWeek)*-1);
}
Dupa ce comparam ora clientului cu cea a serverului trebuie sa verificam daca data curenta este cu ora de vara sau de iarna. Pentru acest lucru putem sa ne folosim de metoda data mai sus si sa verificam data data este cuprinsa intre ultima duminica din luna Octombrie si ultima duminica din luna Martie.
Acesta nu este cel mai sigur mecanism, dar in unele cazuri poate sa fie singura solutie pentru a putea determina in ce time zone se afla clientul.

Comments

  1. Ciudat.. Cum fiecare tara (culture in .NET terms) poate avea propriile reguli legate de ora de vara, si unele tari sunt in mai multe timezones (GMT+n), nu prea vad cum ai putea afla daca o data&ora e in summer time sau nu fara a sti macar si culture-ul din care provine.. (multe tari de la ecuator sau Rusia nu folosesc DST, evident, chiar daca sunt in GMT+2 de ex).

    Sa nu mai vorbim de ciudateniile din USA, unde state din acelasi timezone folosesc sau nu DST dupa cum cred de cuviinta.. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too