We will try and report back.
https://docs.aspnetzero.com/documents/zero/latest/Version-Differences
It appears that adfs support is available for all versions except Angular 6!!!
Are there any plans to support this?
Why not Angular 6??
We are trying to use a MySql database as described on this article
https://aspnetboilerplate.com/Pages/Documents/EF-Core-MySql-Integration
After following the steps on the article, we are able to build and deploy our app pointing to a mysql database server
However, when the application starts, we get this error
System.InvalidOperationException: No coercion operator is defined between types 'System.Int16' and 'System.Boolean'
This is caused by this line on method DefaultEditionCreator.CreateEditions()
context.Editions.IgnoreQueryFilters().FirstOrDefault(e => e.Name == EditionManager.DefaultEditionName);
This is found on the class "DefaultEditionCreator" on the ourAppName.EntityFrameworkCore project from the asp.net zero template
EntityFrameworkCore.Migrations.Seed.Host.DefaultEditionCreator
Note: The same problem does not happen if we generate the migrations for MS SQL server
Our MySql server is version 5.7, running on Linux The MySql.Data and MySql.Data.EntityFramework client libraries are version 8.0.13 Our web app is built for .net core 2.1 and published as a Linux application
Hey,
I'm trying to allow users to log out of the system and register with another OAuth account.
For example, if you logged in with your Office 365 Account <a href="mailto:[email protected]">[email protected]</a>, I want to be able to say no, I want to login with a different Office 365, say <a href="mailto:[email protected]">[email protected]</a>.
Currently, what happens is, even tho I logged out, I am still logged into my Microsoft Account via the session. When I press the button to try to login with Microsoft OAuth, it goes, oh I can tell you're already authenticated and proceeds to log me in with the user I just tried to logout with <a href="mailto:[email protected]">[email protected]</a>.
Is there any way around this. The end result is that users are stuck with the first account they logged in with unless they go to the microsoft.com website and log in there. But I don't want to do that.
I'm trying to use this component of metronic.
<a class="postlink" href="http://keenthemes.com/preview/metronic/theme/admin_1/components_bootstrap_multiselect_dropdown.html">http://keenthemes.com/preview/metronic/ ... pdown.html</a>
I'm expecting it to work like on the metronic website.
It doesn't - it looks like this instead.
[attachment=0:1gxht3u7]trash.PNG[/attachment:1gxht3u7]
To produce this, I have copied verbatim the sample code from the metronic website.
I checked and I have the same version of bootstrap as the metronic sample so it is very confusing to me as to why this doesn't work. When you say that there are 1000+ components available with asp.net zero..... are they metronic components or something else? Am I wrong to expect this to work?
<select class="mt-multiselect btn btn-default" multiple="multiple" data-width="100%">
<option value="cheese">Cheese</option>
<option value="tomatoes">Tomatoes</option>
<option value="mozarella">Mozzarella</option>
<option value="mushrooms">Mushrooms</option>
<option value="pepperoni">Pepperoni</option>
<option value="onions">Onions</option>
</select>
Adding this
Configuration.Modules.AbpWeb().AntiForgery.IsEnabled = false;
XXXXWebApiModule::Initialize() fixed for development.
Since we will not be using ASP.NET to make calls to the API we need to understand what involved in getting this to work for production.
Q: Do we need to read a cookie and then submit that as an X-Header in the call to the API?
The changes listed here.
<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/commit/a9170c0d9728bea63ffdadca10bb1eb7347191f8">https://github.com/aspnetzero/aspnet-ze ... b7347191f8</a>
Are already in my existing release.
Also, im trying this from REST Console plugin for Chrome. Dont see why that should matter?
Thanks. Were in to github now. Will try the fix in an hour.
Since that last update was in October, I'm assuming this was fixed? Were using 2.1.0??