We are migrating an existing application to run under ASP.NET Core MVC. We want to use the Upload feature, but the assembly we currently use, Infragistics45.Web.jQuery.v16.2, only works when the IIS App Pool using .NET CLR Version v4.0. .NET Core requires that the App Pool be set to "No Managed Code". We've tried using the new Upload Middleware we've found described on various Infragistics websites but can't seem to get any of them to work. We are running the .NET Core with the full 4.6.2 Framework due to functionality we need that is not available in the .NET Core Standard.
Can anyone provide a detailed example of both configuration, server-side and client-side code examples, to help us achieve what we need to do. We want to continue using the client-side igniteUI JQuery to perform the Uploads, but we need the server-side to run under .Net Core using the full 4.6.2 Framework.
Hello,
Thank you for contacting Infragistics!
The dll you are using is specifically for ASP.NET and not MVC so you wouldn’t want to use that any more. Instead you would use the jQuery/Ignite UI version of the control which uses JavaScript for most of its functionality. For using the igUpload in JavaScript/MVC please see the following documentation and samples:
https://www.igniteui.com/help/igupload-using-http-handler-and-modules
https://www.igniteui.com/help/igupload-using-server-side-events
https://www.igniteui.com/file-upload/aspnet-mvc-helper
https://www.igniteui.com/file-upload/upload-progress-manager
To use ASP.NET Core MVC you would have to get the correct NuGet package, as .Net Core only supports 3rd party references through NuGet packages. You can see the following on getting NuGet packages setup:https://www.igniteui.com/help/using-ignite-ui-nuget-packages
We implemented what is described in the pages 'igupload-using-http-handler-and-modules' and 'using-ignite-ui-nugget-packages'. Since we already have the upload code working on the client-side, we did not implement any of the server-side code described by the other web pages.
Unfortunately, after issuing the igUpload command at the client, the calls to the server fail with 404 errors. We've used the same client-side code with the ASP.NET version of the server-side dll and everything works fine.
The following is what we have in the web.config.
<system.webServer>
<validation validateIntegratedModeConfiguration="false" />
<modules runAllManagedModulesForAllRequests="true">
<remove name="WebDAVModule" />
<add name="IGUploadModule" type="Infragistics.Web.Mvc.UploadModule" preCondition="managedHandler" />
</modules>
<handlers>
<remove name="WebDAV" />
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
<add name="IGUploadStatusHandler" path="IGUploadStatusHandler.ashx" verb="*" type="Infragistics.Web.Mvc.UploadStatusHandler" preCondition="integratedMode" />
</handlers>
<aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false"></aspNetCore>
<security>
<requestFiltering>
<!--OPTIONAL: Set the maximum request length. By default the request lenght is ~30 MB. More info: http://www.iis.net/configreference/system.webserver/security/requestfiltering/requestlimits-->
<requestLimits maxAllowedContentLength="2097151000" />
</requestFiltering>
</security>
<customHeaders>
<add name="X-Frame-Options" value="ALLOW-FROM http://www.microsoft.com" />
<add name="X-Frame-Options" value="ALLOW-FROM http://www.google.com" />
</customHeaders>
</httpProtocol>-->
</system.webserver>
Our Dependencies include both NuGet packages IgniteUI and IgniteUI.MVC (version 16.2.20162.2040 for both).
The client-side script to perform the upload is as follows:
$("#ATigUpload1").igUpload({
mode: 'multiple',
multipleFiles: true,
autostartupload: true,
progressUrl: "/IGUploadStatusHandler.ashx",
uploadUrl: "/ig_fua34sf345sdf13sdf3454erdsf2345asd3425df5235d54df345.aspx",
maxSimultaneousFilesUploads: 2,
controlId: "serverID1",
fileUploading: function (evt, ui) { ... },
fileUploaded: function (evt, ui) { ... },
fileSelected: function (evt, ui) { ... },
fileSelecting: function (evt, ui) { ... },
onError: function (evt, ui) { ... },
fileUploadAborted: function (evt, ui) { ... }
});
I found the hander in your solution. Apparently it didn't get published, so I copied it manually. However, it still doesn't work.
I left the handler file in the folder but it was excluded from the project as it should not be used. And the upload will have its own created. What happens when you exclude the handler.
You may get several posts from me. Once I do a post I keep getting the message that the forum is managed and that my posts must first be approved. Other times it gets added automatically.
However, running the solution as sent also returns the 504 error.
Thank you for the update. If you are getting the moderation message it is likely that you are posting many times in a short period of time so the system thought your post were spam. In the future it would be better to post all your updates in one response/post. Concerning the 594 error I have done some looking into and it appears it may be a timeout issue try increasing your timeout:
https://forums.asp.net/t/2081506.aspx?+Fiddler+ReadResponse+failed+The+server+did+not+return+a+complete+response+for+this+request+Server+returned+0+bytes+for+an+asp+net+application+
I also found the following post which suggests the handler is not returning anything. I read the other post and changing the timeout didn't appear to fix the other persons problem. The file is getting uploaded (although with a 504 response). But the handler isn't returning what is expected.
http://www.telerik.com/forums/fiddler-readresponse()-failed-the-server-did-not-return-a-response-for-this-request-server-returned-0-bytes
We did get the ASP.NET code that supports an Upload to work with our app (even though we are running in a .net core environment, meaning we are using Kestrel). The call to the handler works fine in this case.
It is unclear why everything is working fine in your setup but not ours when using the MiddleWare. I would think it should be straightforward to configure and use, but that doesn't appear to be the case for us.
Thank you for the update. Can you tell me more about your setup? What is your OS? What browser are you using? What version of the browser? Do you have a full network log of the traffic when that error occurs that you can attach?