Thank you - you are right.
The link to Metronics 5 from <a class="postlink" href="https://aspnetzero.com/Download">https://aspnetzero.com/Download</a> is incorrect (404).
Can you please update it.
Hi.
Using the latest ASP.NET Core / Angular template and following the step by step guide we get this when we are trying to add a migration. We used the migrator to setup the database originally, and that worked just fine. Running Database-Update gives the exact same issue.
PM> Add-Migration "Added_Core_Entities" System.IO.FileLoadException: Could not load file or assembly 'Newtonsoft.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'Newtonsoft.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'
How do we resolve this? There is an old related post, but its unclear exactly what to do.
Regards
Kristian
Hi.
We are using the latest ASP.NET Zero ASP.NET Core / Angular template and locally it runs all fine. When deploying to IIS (both backend and frontend) we are running into CORS issues - but not everywhere.
aspnet-core parts run on <a class="postlink" href="http://api.domain.com">http://api.domain.com</a> , where domain is one of our domains. angular part runs on <a class="postlink" href="http://administration.domain.com">http://administration.domain.com</a>, where domain is the same domain as above.
Both run on port 80.
We are able to login, edit users etc... everything seems working just fine - except Administration / Settings. When we click save on this page only we get a CORS error like this.
Failed to load resource: the server responded with a status of 405 (Method Not Allowed) tenantSettings:1 XMLHttpRequest cannot load <a class="postlink" href="http://api.somerandomdomain.com/api/services/app/TenantSettings/UpdateAllSettings">http://api.somerandomdomain.com/api/ser ... llSettings</a>. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://administration.somerandomdomain.com' is therefore not allowed access. The response had HTTP status code 405.
We tested it multiple browsers and all fails. Running locally with IISExpress and Nodejs it works just fine.
Could there be some issue with the implementation causing CORS problems on some pages, while the rest works fine?
Regards
Kristian
I will let you know as soon as I figured out how to enable / disable it ;)
Hi.
We replaced the logging framework with nLog as described in the documentation, and we are currently logging to a file.
Basically all SQL commands executed by EF Core seems to be logged which makes the log files huge.
Regards
Kristian
It appears that by default all SQL statements are logged by the backend. We can't seem to figure out where this is configured.
Is there a way to turn of logging of SQL statements?
We are unable to get login to work in IE - it works just fine in Chrome, Firefox and Edge.
When you have entered credentials you are redirected back to the login screen with all fields cleared.
We original used version 4.0 of the ASP.NET Core / Angular template, but to be sure we did not break anything we have just downloaded and setup the lastest version of the template - and it has the exact same problem.
We tried from different machines, cleared the browser cache etc. but we simply can not get it to work.
We are using IE 11.413.15063.0
Kindly help us solve this blocking issue.
Hi.
We are using NLog instead of Log4net and it is working just fine - but we can not get logging to a database to work.
We are using a standard nlog configuration which works just fine in all our other systems which are not based on ASP.NET Zero. But when we try to do it in ASP.NET Zero we get the following error (when setting throwExceptions="true" in the nlog config)
"NLog.NLogConfigurationException: 'Connection string 'nlogdatabase' is not declared in <connectionStrings /> section.'"
The connection string IS configured correctly in the nlog.conf. We also tried to add it to the appsettings.json using this article but we get an exception when we try to set the connection string.
<a class="postlink" href="https://damienbod.com/2016/09/22/setting-the-nlog-database-connection-string-in-the-asp-net-core-appsettings-json/">https://damienbod.com/2016/09/22/settin ... ings-json/</a>
We even tried to set it in web.config and finally tried a nasty hack using reflection to add the connection string at runtime to System.Configuration.ConfigurationManager which got us past the initial error but then throw a null reference exception somewhere in the NLog / Castle frameworks.
Could you kindly guide us on the right way to get logging to database to work with NLog?
Regards
Kristian Leonhard
Hi.
We are trying to add danish language, but it breaks the frontend because no localization for jTable exists in the node module.
zone.js:2176 GET <a class="postlink" href="http://localhost:4200/assets/localization/jtable/jquery.jtable.da.js?_=1499286192984">http://localhost:4200/assets/localizati ... 9286192984</a> 404 (Not Found)
Could you tell us what the proper way of adding our own localization file would be, if we wish to keep it private and not do a pullrequest on github.
/Kristian
