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) { ... }       

});

Hi,

Thank you for the update. I had missed the link that Mike H. sent. I sent the other links as an example of setting up NuGet not the specific NuGet package you would have to get. I have some follow up questions concerning this matter.

If you are in a .Net core environment why are you trying to use the full framework?
Why can you not instead work in an environment with the full framework?
Or use the .Net core framework in the .Net core environemnet?

There are many aspects of the .net core environment in Visual Studio which we like. However, the .net core framework is missing a lot of functionality we need (we just converted over to an MVC app and needed to port over all functionality from the other application). We cannot use the .net core framework without major changes to our application.

We like the idea of using the Middleware, but it appears that Infragistics only supports them when using the .net core framework. We are using a lot of other Middleware with not problems.

Hi,

The version of the Infragistics controls you will use will want to be matched to the version of .Net you are using for the project. If you are creating a .Net Core project you will want to use the .net core version of our assembly. If you are creating a regular .net project you would use the regular assembly for out controls.

We've already gotten NuGet packages IgniteUI and Ignite.MVC working with our new MVC application. They require us to run the web site with a pool configured for .NET CLR v4.0 rather than No Managed Code, as is typical for a .NET Core MVC application. These are the only NuGet packages we have as a dependency that forces the pool to be configured this way. We are using Middleware to perform several other tasks.

We were hoping to use the Middleware documented for Infragistics Uploads as well using NuGet package Infragistics.Web.MVC, however, we were never able to get it to work. A sample solution to perform Uploads using the Infragistics.Web.MVC package would be greatly appreciated.

Hello,

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?

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.

I initially ran with the handler omitted from the published project and got the same 504 errors. So I put it in and it got the same error. Didn't seem to make any different one way or another.

I've been unable to get the app to run in IISExpress through VS 2017. It fails trying to find the web.config. It keeps trying to find it in c:\Users\mpeterson\Downloads\UploadTest\UploadTest\UploadTest. I can't find a reference to that anywhere, but I assume that is where you placed it for testing.

I can only run by publishing locally.