Problems with AzureUpload method

Hi Guys,

I'm kind of tearing my hair out here working out what might be wrong.
I have a file manager component defined as :
<div class="filemanagerContainer">
  <ejs-filemanager id='overview'
    #fileObj
    [ajaxSettings]='ajaxSettings'
    [view]='view'
    [path]="detailsViewPath"
    [contextMenuSettings]='contextMenuSettings'
    [navigationPaneSettings]='navigationPaneSettings'
    [toolbarSettings]='toolbarSettings'
    [uploadSettings]='uploadSettings'
    [showFileExtension]='showFileExtension'
    [showHiddenItems]='showHiddenItems'
    [allowDragAndDrop]='allowDragAndDrop'
    (success)="success($event)"
    (menuOpen)="menuOpen($event)"
    (menuClick)="menuClick($event)">
  </ejs-filemanager>
</div>

I have a backend based on Volosoft's Zero framework.
To get the component to work I first downloaded and worked with the github code for filemanager into a sandbox project and everything was going well.
I then copied the code to my own project and the method "AzureFileOperations([FromBody] FileManagerDirectoryContent args)".
This gave me great functionality on "read", "delete", "create" and so on.
However, when it came to implementation of the "AzureUpload(FileManagerDirectoryContent args)" I am getting stackoverflow errors before the request meets the MVC pipeline.
My logs show that the the method has been hit and accepted so I have no CORS problems.
I use the upload button as per:


And an error is thrown in my controller:


There is nothing in my logs to suggest what has happened.
After the stackoverflow error is thrown my network tab looks as below:


I can actually run my own server project and the syncfusion project in tandem and have my project server the url value and thye syncfusion project serve the uploadUrl but I cannot, for the life in me, get the AzureUpload function to work in my won own project.  I'm sure it's something to do with Volosoft's abp or Zero framework and have dropped a line in their forum too.
Can you guys suggest anything at all I should look for - it's a shame because I have all other functionality working except for this one problem.


3 Replies 1 reply marked as answer

SP Sowmiya Padmanaban Syncfusion Team August 14, 2020 01:43 PM UTC

Hi Bob,  
 
Greetings from Syncfusion support. 
 
We have checked your reported issue with FileManager component. Based on your shared details, you are using Azure MVC file provider for accessing files in FileManager component.  But the Azure MVC file provider is working fine in our side.  
 
Refer to the below attached video, upload functionality is working properly in Azure File provider. 
 
 
Refer the sample  and service links below. In our service, we have used the .NET framework version as 4.5. 
 
 
 
We suspect that you reported issue may occur due to some .NET framework limitation. Because, we are facing some similar issue in Azure .NET Core file provider. Could you please share the below details regarding your reported issue. 
 
1.     Share the .NET Framework version of your application. 
2.     Confirm whether you are using Azure MVC file provider or Core file provider. 
 
Please share the above details, it will help us to resolve your issue at the earliest. 
 
Please let us know, if you need any further assistance. 
 
Regards,  
Sowmiya.P 
  



BI bob ingham August 14, 2020 02:33 PM UTC

Hi Sowmiya,

Yes, I believe you have found the core of the problem.
The sandbox application I have used to build a sandbox project for Syncfusion is the ej2-aspcore-file-provider-master303517317.zip taken from your git hub site.
This runs on .netcore 2.1.  I have this sandbox running with an instance of the document editor controller and everything works fine.

Unfortunately my Zero/ABP project is old and due an upgrade, for now it works on aspnet 4.6 with dotnet core compatibility set to 2.2.
I hope that helps in your diagnosis of what may be wrong and where to look or how to rectify the situation.

Thanks very much for your help in this matter.
Bob





SP Sowmiya Padmanaban Syncfusion Team August 17, 2020 07:51 AM UTC

Hi Bob ingham,  
 
Based on your shared details you are using Azure ASP.NET Core file provider in the .NET version 2.2. We have already logged this as a bug from our end. This bug fix will be included in our Volume 3 Release which is expected to be released at the end of September 2020. Until then, track the below feedback link for bug status. 
 
 
This issue occurs due to framework limitations and only when you are using the .NET version as 2.2. Since the upload functionality of FileManager component will be working fine in recent .NET Core3.0 versions, we suggest you to use the .NET Core 3.0. 
 
We appreciate your patience. 
 
Regards,  
Sowmiya.P 


Marked as answer
Loader.
Up arrow icon