Using Ignite UI for Asp.Net Core

Topic Overview

This topic explains how to get started with Ignite UI for Asp.Net Core™ components in an ASP.NET Core Web Application built with ASP.NET Core 3.0.

In this topic

This topic contains the following sections:

• Referencing the Infragistics Web MVC NuGet package
• Configuring the igUpload Middleware for file upload handling
• Related Content

Referencing the Infragistics Web MVC NuGet package

Using local feed

With the ASP.NET Core most modules are now wrapped as NuGet packages. This allows you to retrieve and use only the specific modules you need for your application, without having to depend on a common assembly. All dependencies of the specific module will be restored out of the box.

As such our new Ignite UI for Asp.Net Core built on top of ASP.NET Core will also ship as a NuGet package. When you are installing the product make sure to include the NuGet packages module that will create a local feed for you to install the required packages from. For more information, please refer to the topic: Using Ignite UI for jQuery NuGet packages.

Control's declaration follows the same syntax as the previous MVC versions. You can refer to the following topic for more information and examples: Adding Controls to an MVC Project

Using online private feed

You can also install Infragistics Web MVC NuGet package using the Infragistics hosted NuGet server. Checkout Installing Ignite UI for MVC packages from the online private feed topic for more information.

Configuring the igUpload Middleware for file upload handling

In the old ASP.NET in order to handle more robust file uploading capabilities as multiple file uploads, large file uploads and reporting of the progress of an upload you would have to implement an HttpModule and/or HttpHandler in order to plug into the HTTP Request process.
ASP.NET Core introduces a new request pipeline built around a new middleware definition. The Ignite UI for Asp.Net Core file upload fully utilizes the new middleware definition model and can be directly plugged into the pipeline. There are two middleware modules - one for handling uploads and one for receiving commands from the client and returning status feedback to the client. In order to add them to the pipeline they need to be include in the Configure method of the Startup.cs class before the MVC module.

In C#:

     public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory) 
        { 
            ... 
            app.UseUploadModuleMiddleware(); 
            app.UseUploadHandlerMiddleware(); 

            app.UseMvc(routes => 
            { 
                routes.MapRoute( 
                    name: "default", 
                    template: "{controller=Home}/{action=Index}/{id?}"); 
            }); 

            ...
        }

Additional settings for the upload can be set in the ConfigureServices method. The options can either be set declaratively or retrieved from the configurations file.

In C#:

    public void ConfigureServices(IServiceCollection services)
        {
            ...
            services.Configure<UploadAppSettings>(options => {
                options.FileUploadPath = Configuration["UploadAppSettings:fileUploadPath"]; 
            });
        }

Related Content

• Adding Controls to an MVC Project