Activities of "jtallon"

Not only that, the "Date" portion of the DateTime object is also incorrect.

2/1/1970 in first screenshot - where I picked 2/2/1970 using the ngx-datepicker angular component (incorrect)

10/10/1970 in second screenshot - I picked 10/10/1970 using the component (correct)

More information,

The TimeOfDay property on the DateTime model property is "23:00" for the incorrect date (2 Feb 1970)

but "00:00" for the correct date

When I set a breakpoint at the entry point of the AppService

Hi,

For example, i pick 10th October 1970 - Saved in database as "1970-10-10 00:00:00.0000000" - Correct

I pick 2nd February 1970 - Saved in database as "1970-02-01 23:00:00.0000000" - Incorrect - 1 hour off

Hi , I've seen this bug replicated on another project also (v9.0.1) specifically around the dates 19 Feb 1968 -> 31st Oct 1971.

The bug doesn't manifest itself on later dates.

Hi @ismcagdas, would it make sense that this bug is only affecting some date ranges if the clock provider was incorrectly set? It doesn't make sense to me.

I set the clock provider in webcoremodule.cs in pre initialize method using this line of code, is this the correct way to do it?

Clock.Provider = ClockProviders.Utc;

I see some documation here; https://aspnetboilerplate.com/Pages/Documents/Timing I will try setting clock provider and retest.

Hi, It doesn't look like we've configured Clock.Provider in the API project. I've searched in all .cs files for "Clock.Provider", Do we need to configure clock provider?
Thanks

Also, this is not limited to the first date of the month.

For example, i picked 11th March 1971 and it saved as "1971-03-10 23:00:00.0000000" in the database.

It also renders incorrectly in the UI

Ok, so I managed to get this working by injecting the UOW manager into the Authorization Handler:

using (var uow = _unitOfWorkManager.Begin())
{
	var exampleEntity = await  _entityRepository.FirstOrDefaultAsync(entityId);

	var teamId = exampleEntity?.TeamId;

   ........
}

That link is not reachable.