Hi,
We are thinking of this topic and we will work on it after releasing Angular2 version. This is a really hard topic and we will be very happ to hear your suggestions as well.
Hi,
Can you try to create your project with a project name other thatn "App" ? So you can build and run the project in this case. If you really want to use "App" as project name, we will consider this case.
Hi,
Can you move the line for adding background worker after this line and try again ?
await SignInAsync(loginResult.User, loginResult.Identity, loginModel.RememberMe);
Hi,
It's better to store all dates in UTC in this case. But if you are using UtcClockProvider as Clock.Provider, the value on the server side should be converted to UTC, you don't have to do anything.
If you are using moment timezone library (<a class="postlink" href="http://momentjs.com/timezone/">http://momentjs.com/timezone/</a>), it handles client side timezone operations. Even if you set timezone to UTC+1, because of the Daylight Saving Time, the selected date might be in UTC+2 timezone.
For example in Turkey we are in UTC+2 timezone but in summer time we move to UTC+3 and now we are in UTC+3. So I think 7:00 AM you are getting on server is probably the UTC date.
If this is not clear for you, please send the name of UTC+1 timezone you are setting on your app, then we can take a look at your case more deeply.
Hi,
I have uploaded the metronic v4.7 template to latest release. You can find it here <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/releases/tag/v1.13.0">https://github.com/aspnetzero/aspnet-ze ... ag/v1.13.0</a>
Hi,
I write a simple unit test to simulate your case, but it worked as expected. Can you share your code for this case ? So we can understand the problem better.
Hi,
Can you share the error details ? It should be in the Logs.txt file under your web project.
Hi,
Can you share the code you register background worker ? Or even better if you can send your project with email.
It might help to solve problem more quickly.
Hi,
new Claim(ClaimTypes.NameIdentifier, empid)
is correct but you you have to set a valid userId instead of your empid.
To do that, you can add an empid into AbpUsers table (<a class="postlink" href="https://aspnetzero.com/Documents/Extending-Existing-Entities">https://aspnetzero.com/Documents/Extend ... g-Entities</a>) and find the appropriate userId for the "empid" in http request.
Hi,
The first issue is related to ISoftDelete interface. You can see the related issue in ABP repository here <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/issues/274">https://github.com/aspnetboilerplate/as ... issues/274</a>.
For the second issue with ShouldCreateFornecedorAndGetFornecedoresPaginado, we are still working on it :)