You should always use an external file service for apps hosted in azure (and for apps in general, in my opinion.)
Files stored locally on an azure website are not permanent. Redeploying or scaling events that rebuild the VM hosting your app will wipe out existing files (or the new VM could be on a completely different physical machine to begin with.)
<a class="postlink" href="https://stackoverflow.com/questions/26365590/avoid-deleting-files-on-azure-cloud-service-publish">https://stackoverflow.com/questions/263 ... ce-publish</a>
You didn't post your controller code, but I suspect what's happening is that your definition for your get controller does not take a parentId, and your post controller does expect a parentId.
When the parentId is null, then web api tries to resolve to the get action, because it has the closest matching parameters.
You should be able to either make the parameter optional in the post controller, or force it to be included with a null value in your javascript service.
The error you posted doesn't appear to have anything to do with your database.
It looks like you are sending a 'get' request to a web api method that's defined as a 'post' method.
<cite>ismcagdas: </cite> Hi @AndrewT,
This solution is offered by community, maybe they can provide a sample for core version as well. Have you asked it to <a class="postlink" href="https://github.com/princeppy">https://github.com/princeppy</a> ?
Thanks.
Given that you are releasing major changes almost monthly to the platform, I think it would be really beneficial to your users to provide a means to upgrade via nuget.
I know this is possible, even with content pages, as Umbraco provides this feature.
I also know it is a big undertaking, but I think for long term growth of Zero, it would be a strong investment for your company, especially since most of the complaints about the framework are in regards to the upgrade process.
This is probably a silly question, but did you enable the google+ api when you set up your google account? (it is disabled by default) This is the thing that's caused me to experience logininfo being null.
Version 4.5 was released last week, and it upgrades the framework to core 2.0.
4.5.1 Isn't compatible with .net core 1.1... it's a .net core 2.0 project.
The code in your website differs from the source code I have in my project.
If you took the time to debug the javascript error, you would see that there is a syntax error in your minified js.
window.paypal.request.addHeaderBuilder(()=>{"X-XSRF-TOKEN":abp.security.antiForgery.getToken()});
That is not valid arrow syntax.
It should be:
window.paypal.request.addHeaderBuilder(()=>{return {"X-XSRF-TOKEN":abp.security.antiForgery.getToken()}});
Javascript files are not minified in development, which might explain why you don't have the issue locally.
I can't find the _PayPal.min.js file in the solution, so I'm not sure how it's being generated.
Most of those updates are for .Net Core 2.0 I suspect, and should not be updated.
The better approach, while painful, would be to download the new 4.5 version that includes the .net core 2.0 upgrade, and apply your customizations to that.
We are currently going through that process our self.
<a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues/380">https://github.com/aspnetzero/aspnet-ze ... issues/380</a>
