This is a cross platform issue with .Net. TimeZoneInfo.GetSystemTimeZones() returns different time zones between different OS platforms. There is no built in mapping between those in the .Net framework. My guess is this will be tough to fix without totally getting away from TimeZoneInfo class (EDIT: Fix may be the wrong word here lol...it's working perfectly as coded :) )
Here is a little bit of the talk on stackoverflow.
<a class="postlink" href="https://stackoverflow.com/questions/41566395/timezoneinfo-in-net-core-when-hosting-on-unix-nginx">https://stackoverflow.com/questions/415 ... unix-nginx</a>
Another link if you want to look at the code itself and see that the Unix flavor gets the IANA timezones:
<a class="postlink" href="https://github.com/dotnet/coreclr/search?utf8=%E2%9C%93&q=PopulateAllSystemTimeZones&type=">https://github.com/dotnet/coreclr/searc ... ones&type=</a>
On one of our projects we are using version 4.6 of asp.net zero. We can't upgrade to 5 because of the theme changes so we are going to stick with this version.
I always like to give new developers a link to your documentation and have them go through the Step by Step development guide. The current documentation now looks different with newer screenshots. I am wondering if you have old version of the documentation that I can link to for the specific version of the framework we are using.
Also, I still have some projects on the Angular 1.x version which it would be nice to have links to that documentation as well. So, anyway, any help would be appreciated.
Thanks
Thank you! I was looking for that on the wrong screen.
If they don't let you post any code, maybe you could just describe your solution so maybe we can take a stab at it. Then you could maybe review our code :)
I am actually going through this same process right now and it's a bit cumbersome. Just for reference if anyone wants to know, we are using this to generate entities (we only generate them once):
<a class="postlink" href="https://github.com/ErikEJ/SqlCeToolbox/wiki/EF-Core-Power-Tools">https://github.com/ErikEJ/SqlCeToolbox/ ... ower-Tools</a>
We generate them once because we have to change them to be ABP entities (Base Classes, Interfaces, etc). It's possible but difficult to update the output of that process so we generate them up front, then all changes going forward are done code first.
But, back to my struggle. I am really debating on going back to EF 6 simply to be able to use some T4 templates to generate code. Going from an existing database with varying degrees of standards across the tables (primary keys, audit columns) is difficult when coming from an existing database. So, we are creating several workarounds to get it to play nicely with ABP. Plus, ABP system is merely one system in several so there are some database objects that really shouldn't be a part of this code base. I know, that's not ideal, but this is a large client, with many years of technology in production.
So, my question is can we take the current version of the downloaded Angular project that uses the full framework and switch out to use the EF6 libraries and not the Core libraries. I would have to code the seeds differently and a few things but I have all that code in other projects so I am just wondering if the EF 6 and EF Core projects are somewhat interchangeable???
Thoughts?
I thought about that as well but it seems a little hackish. Although I can't say other things I am doing don't feel the same way.
So we have to generate a couple things right, first the entities and then the context. The context needs to be generated with .net core code because the fluent API is different in core. The Entities could be generated in EF 6. I don't know, maybe I will try that tomorrow. I am already using a T4 template (ReversePocoGenerator) for EF6 in another project so I could generate entities with it, and generate the first round of Context code with the one I am using above.
Ugh, sounds fugly just saying it out loud lol.
Do you do this currently? I would be curious to know what process you follow.
So, through the day to day you are right, we are not using fluent API for much of anything, but in the beginning, the generator kicks out some items in the OnModelCreating event that adds all the indexes and other model stuff that isn't easily represented in attributes. I could for the most part generate the entities in T4, then true up anything that is left in the OnModelCreating. Does that make sense? Just talking about the code that is generated within the context class.
I'll give the entities a try today and see how it goes. I very much appreciate the input and links. I will check back in once I am done.
Thanks
Well, hopefully that T4 template generates much more of the attributes needed so there won't be a need for the API. The system that I am using to generate it doesn't do terribly well at using data annotations so you have to use the API a little.
One last question, then you can move on with your day....do you continue to use the T4 and not do code first? If yes, then you just use Code First for the ABP entities, then tie in your own Context for the other data?
Again, appreciate the advice and help.
@ismcagdas
Is there any update on timeline for this? We are fixing to kick off a big upgrade of our big aspnetzero project and would be nice to know how this might factor into the equation. Just general update works for me, doesn't need to be specific. I promise I won't hold it against you if you are off a bit (mostly lol) :)
Thanks
{ "claim": "name", "key": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name" },
I added that as a claims mapping to fix the issue on my side.