indeed for the cors.
thanks, i'll test it in a few days & be back to you if it's not ok
To make it work, I also had to change :
and create a :
Maybe there was another way ? If not, you can close this topic :)
Thanks anyway !
It could do the trick but it's more for inherited class that i was speaking.
More like this one in fact : https://github.com/aspnet/EntityFrameworkCore/issues/11314
It's scheduled for EF CORE 3.0 (second half of 2019)
I close the ticket & we'll wait until 3.0 release.
(sorry, I was tired yesterday; i found it in 30seconds today)
thanks !
+1 for powerBI.
i've coupled it with ODATA
nevermind, case 2 works with :
"remoteServiceBaseUrl": "http://PRODUCTION-public-ip:5000", "appBaseUrl": "http://localhost:4200",
(+ port forwarding 4200 from router to my local pc)
I don't know why it wouldn't work the 1st time, that's will stay a mystery.
Subject closed :)
Thanks for your reply ;)
i'll think a little bit more about that; but I think it will be easier for me to maintain the ANZ MVC 5.X in my project for few more months, & try to migrate my whole app in angular2 in the same time.
it will save me/you some time :)
<cite>joshBoilered: </cite> "Default": "Server(localdb)\mssqllocaldb;Database=ProjectName;Trusted_Connection=True;MultipleActiveResultSets=true"
But received the following error. I don't have SQL so I spun up a quick db in Azure, changed my connection string and re-ran the migrator, same issue.
your connection string is incorrect. it's for self hosted mssql database. chose one of those :
Please do a search on the forum, there is plenty threads about this topic ;)
<a class="postlink-local" href="http://forum.aspnetboilerplate.com/search.php?keywords=oracle">search.php?keywords=oracle</a>
In .web project, use /App for ABP dasbhoard. create a new folder for your new angular app, like /App_Name .
From the documentation <a class="postlink" href="https://www.aspnetzero.com/Documents/Development-Guide#sms-verification">https://www.aspnetzero.com/Documents/De ... rification</a>
SMS Verification
This is available if the user has a confirmed phone number. Note that SMS sending is not fully implemented because it requires an integration to an SMS vendor. The current implementation just writes security codes to logs. You should complete the IdentitySmsMessageService class in the solution to make it usable. Otherwise, disable SMS verification in the settings.