Skip to main content

Calcule cu DateTime

By
Trebuia sa afisez durata intre un startDate si un endDate. Aceasta trebuia sa fie afisata sub forma:
Durata este de: [years], [months], [days]
Problema a aparut cand trebuia sa determin daca 28,29,30 sau 31 de zile reprezinta o luna? Problema este ca nu am putut determina numarul de zile pentru o luna. Daca as alege 28, as ajunge ca sa calculez ca luna ianuarie contine si ea 28 de zile, cea ce este complet eronat. O alta situație in care pot sa ajung este sa aleg durata unei luni de 30( sau 29) de zile si atunci as ajunge intr-o situatie similara pentru luna februarie.
Problema apare in jurul date de 28 februarie. Rotunjirile care se fac in jurul acestei date(+/- o unitate de masura - care poate sa fie zi sau luna). Valoarea de tip TimeStamp sau DateTime pe care o adun sau o scad nu reprezinta mereu o valoarea buna, deoarece o luna poate sa aibe 28,29,30 sau 31 de zile.
Problema a apărut cînd am ajuns pe cazurile de mai jos:
30/01/2011 + 0 luna = 28/02/2011
29/01/2011 + 0 luna = 28/02/2011
28/01/2011 + 0 luna = 28/02/2011
30/01/2012 + 0 luna = 29/02/2012
29/01/2012 + 0 luna = 29/02/2012
28/01/2012 + 0 luna = 29/02/2012
28/01/2011 + 0 luna + o zi = 01/03/2011
29/01/2011 + 0 luna + o zi = 01/03/2011
01/03/2011 - 0 luna - o zi = 30/01/2011
01/03/2011 - 0 luna - o zi = 30/01/2011
Labels:

Comments

  1. NicuDecember 2, 2010 at 1:28 PM

    This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

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

By
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(
Post a Comment
Read more

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

By
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
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 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
Post a Comment
Read more