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

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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...