Some addtional notes on our experience with upgrading to V6.0:
FreezeUI has replaced the spinner. When using the previous spinner component, we would pass the div id to it (when used programatically), so that only that component would be blocked. Since JQuery was removed, that code broke, and the default CRUD grids also did not localize the spinner correctly (blocked the whole screen instead). In order to get FreezeUI to function on any arbitrary component that required a loading indicator, we choose to add position:relative to the CSS class attached to the desired div and set the [busyif].
Since JQuery was removed, our metronic Accordian control ceased to expand. IMHO, Metronic's accordian that is better than Angular's, so we simply re-added JQuery (also requires BootstrapJS) back in specifically for that control.
@rnguyen, glad to hear you found the problem.
Some additional info for other users is that the ASP.NET core environment can also be set right in the Windows environment under Control Panel > System > Advanced system settings | Environment variables.
I'm unable to support you via Teamviewer, but you need to ensure your CORs settings are correct. As @mumfie suggested check your apppool permissions for the site. Ensure whatever account you're running under has read/write access to your host database.
Also, check your app_data log folder (ensure your apppool account has modify/write access to this folder as well), the logs should provide more info.
Hi @rnguyen, I see from your request screenshot(s) you are hitting the url http://aixem.com. Your ServerRootAddress, ClientRootaddress CorsOrigin must be set according to the url requested (i.e. http://aixem.com).
Your other screen indicates http://xyz.com which would of course be incorrect given the screenshots you've provided. In this case, this would definitely produce a CORs pre-flight access error.
Can you provide a screenshot of your network tab under the F12 tools? This would indicate any access errors.
@yekalkan thanks for the reply - just tried this this morning and it is not the RAD tool, but rather a bad model column in the migrations snapshot.
