The most recent version has not modified the password complexity related functions.
Do you see if there is a problem with the password complexity setting?
<a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/Entity-History#reason-property">https://aspnetboilerplate.com/Pages/Doc ... n-property</a>
You can take a look at the documentation for [Entity-History]
We are configuring our JobStorage in the PreInitialize function of the Abp startup module.
What is the specific code? I want to reproduce this problem.
You're welcome.
If this website (<a class="postlink" href="https://www.certigreen.be/">https://www.certigreen.be/</a>) is not yours, you cannot modify his cross-domain strategy.
<a class="postlink" href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS">https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS</a>
<a class="postlink" href="http://www.certigreen.be/public/visits/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX">http://www.certigreen.be/public/visits/ ... XXXXXXXXXX</a>
This site does not support cross-domain access. You cannot change this.
This may be some of the problems with the VS compiler, and I am not very clear about this.
Do you see if the solution here is right for you? <a class="postlink" href="https://github.com/select2/select2-bootstrap-theme/issues/41">https://github.com/select2/select2-boot ... /issues/41</a>
You can see detailed information in the VS output window: E.g:
3> Consider app.config remapping of assembly "System.Runtime.Serialization.Xml, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6.1\Facades\System.Runtime.Serialization.Xml.dll] to Version "4.1.3.0" [C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\net461\lib\System.Runtime.Serialization.Xml.dll] to solve conflict and get rid of warning.
3> Consider app.config remapping of assembly "System.Data.Common, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "0.0.0.0" [] to Version "4.2.0.0" [C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\net461\lib\System.Data.Common.dll] to solve conflict and get rid of warning.
3> Consider app.config remapping of assembly "System.Net.Requests, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6.1\Facades\System.Net.Requests.dll] to Version "4.0.11.0" [C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\net461\lib\System.Net.Requests.dll] to solve conflict and get rid of warning.
I manually follow the output information to add dependentAssembly under App.Config to eliminate this prompt. E.g:
<dependentAssembly>
<assemblyIdentity name="System.Runtime.Serialization.Xml" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.1.3.00" newVersion="4.1.3.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Data.Common" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.2.0.00" newVersion="4.2.0.0" />
</dependentAssembly>
Maybe after adding all the items, you can completely eliminate the warning, of course, warning that these will not affect the function of the program.
Ok, I will download it and check it out.