Activities of "jtallon"

Thanks, We're using aspnetzero . I ended up placing the Dtos in that shared project as it made most sense. Thank you.

From my understanding of the documents, a new Dto is needed for each entity we want to cache. Is that correct?

We now inherit from an out of the box class like this and migrations adds Discriminator column and RoleId which makes sense now because when we look at ef query generated with our extended repo it adds this on the query

Adding [NotMapped] Public string Discriminator {get; set;} gives the correct migration... but is that ok?

Thanks for this @ismcagdas , If we were to integrate the fix into our own application , would it be the changes made to AppPreBootstrap.ts ?

I resolved the problem by creating a method to add/update/remove the list of items manually. GraphDiff looks interesting.

Thanks

Posting this for the next person that comes across this issue.

Our dotnet backend was treating the DateTime object kind as local

and the abp.timing.timeZoneInfo.iana was set to Etc/UTC

This missmatch seems to have caused the issue.

Adding Clock.Provider = ClockProviders.Utc; to the PreInitialize() method of our WebCoreModule.cs file was the fix to match Angular App and API.

Kind updated to Utc:

@ismcagdas do you know why the abp.timing.timeZoneInfo would have been set to Etc/UTC?

Ok, from what I can see I needed to set the Clock Provider in PreInitialize method of the Core web module.

That then set the "kind" portion of the datetime object in the backend and it's now behaving as expected.

I'm not sure why the angular client to Etc/UTC as a default?

I just downloaded a fresh project ( v10.2 )from the ASPNetZero website and checked the demo ui components datepicker. See issue below when i click submit: I selected 2 Feb 1970 but posted value is 1 Feb 1970

Hi, this is the result when execute that:

We haven't specified a clock provider in the dotnet core API project so assuming it's using the unspecifiedclockprovider