Is this still not supported yet? We are interested in migrating our CORE 1.x MVC/jQuery Zero solution to CORE 2 + Angular, but we use OpenId Connect for Single Sign-On to an external provider.
Thanks, Bryan
Thanks. This worked!
While I am doing some stuff server-side (not with Moment), I figured it out. However, I think you have a typo in your docs. On the page about Timing at <a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/Timing#DocTimeZones">https://aspnetboilerplate.com/Pages/Doc ... cTimeZones</a>, you state:
ABP assumes that value of timezone setting is a valid Windows timezone id.
When I attempted to use the numeric Windows Timezone ID as documented by MS at <a class="postlink" href="https://msdn.microsoft.com/en-us/library/gg154758.aspx">https://msdn.microsoft.com/en-us/library/gg154758.aspx</a>, it starting giving me errors. When I changed the Abp.Timing.TimeZone setting to the Timezone Name (e.g. "Pacific Standard Time") everything was fine.
Bryan
Thanks. I used your first suggestion. I wasn't able to use the second approach because I had to add a reference to the parent OU in my query and it appears that there is no parent navigation property built into AbpOU, so I couldn't use Include().
Thanks again, Bryan
Thanks!
Thanks!
Sorry, ASP.NET Core & jQuery. (Zero version 4.1.1 -- just downloaded).
I think this issue came up because of the time difference between when the general packages were updated and the release of Zero 4.1. I just downloaded 4.1.1 from the web site but haven't been able to try it yet. I will let you know.
Bryan
I am using EF CORE on the Asp.Net Core + jQuery template.
Did you get this working? I too must extend the OU class, adding a bunch of custom fields as well as creating one-to-many relationships with other new classes that I am creating. If the ForeignKey attribute did not work, did using the Fluent API take care of this? Just starting this new project, so any tips would be appreciated.
thanks, Bryan