[CLOSED] Ext.NET Classic V7 - IIS deployment issue

[Geovision]

Dear,

Please note that I am trying to deploy an EXT.NET Classic WEB Application (EXT.net 7.1) on IIS including a valid License key but with no success.

Steps Achieved:
1- Add the license key into appsettings.json file
2- Publish application into IIS Profile.
3- Install on application server the .NET Core 3.1.9.
4- then deploy the published Application into the application server.

the problem is in displaying the EXT components as per the screenshot below:



in comparison within the original application deployed on local environment:



Can you help me please.

Regards,

[geoffrey.mcgill]

Looks like it might be related to the following issue:

https://forums.ext.net/showthread.ph...plication-name

The issue is fix and will be available in the next release of Ext.NET Classic.

As a temp work-around, you can try setting the custom root path in your production (non-localhost) build.

https://forums.ext.net/showthread.ph...l=1#post286047

Hope this helps.

[Geovision]

Dear,

Please note that the fix that you post later, it doesn't work for me.
please find below the Configure method in my startup.cs:

  public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
        {
            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
                app.UseLiveReload();
            }
            else
            {
                app.UseExceptionHandler("/Error");
            }

            app.UseResponseCompression();

            // 2. Use Ext.NET resources
            //    To be added prior to app.UseStaticFiles()
            app.UseExtNetResources(config =>
            {
                config.UseEmbedded();
                config.UseCharts();
                config.UseThemeSpotless();
            });

            // Re-map the Ext.NET resources to a custom root path, 
            // and configure Debug/Rtl parameters
            app.UseExtNetResources("/extnet7/extnet", config =>
            {
                if (env.IsDevelopment())
                {
                    config.UseDebug(true);
                }
            });


            //app.UseExtNetResources("/extnet7/extnet", config =>
            //{
            //    if (env.IsDevelopment())
            //    {
            //        config.UseDebug(true);
            //    }
            //});

            // 3. Enable Ext.NET localization [not required]
            //    If included, localization will be handled automatically
            //    based on client browser preferences
            app.UseExtNetLocalization();

            app.UseStaticFiles();
            app.UseRouting();
            app.UseAuthorization();

            // 4. Ext.NET middleware
            //    To be added prior to app.UseEndpoints()
            app.UseExtNet(config =>
            {
                config.Theme = ThemeKind.Spotless;
            });

            app.UseEndpoints(endpoints => endpoints.MapRazorPages());

thank you

[fabricio.murta]

Hello @Geovision!

Have you tried changing the block starting at line 26 to the following?

app.UseExtNetResources("/FFMSADMINTOOLMVC/extnet7", config =>
{
    if (env.IsDevelopment())
    {
        config.UseDebug(true);
    }
});

Hope this helps!

[Geovision]

Dear,

Please note that the problem is fixed.
by updating the code as per below:

            app.UseExtNetResources("/ffmsadmintoolmvc/extnet", config =>
            {
                if (env.IsDevelopment())
                {
                    config.UseDebug(true);
                }
            });

in other hand, after deployment all subpages added in MenuData.cs class are stopped :

         public static List<NavItem> Items = new List<NavItem>
        {
            new NavItem("Dashboard", "/", "dashboard"),
            new NavItem("DirectEvent", "/directevent/", "flash_on"),
            new NavItem("GridPanel", "/gridpanel/", "grid_on")

        };

I noticed that, we need to add also a prefix as same as added in Startup.cs page as per the below:

     public static List<NavItem> Items = new List<NavItem>
        {
            new NavItem("Dashboard", "/ffmsadmintoolmvc/", "dashboard"),
            new NavItem("DirectEvent", "/ffmsadmintoolmvc/directevent/", "flash_on"),
            new NavItem("GridPanel", "/ffmsadmintoolmvc/gridpanel/", "grid_on")

        };

my question, is their another solution to avoid the case adding prefixes based on deployment path since the project can be deployed on multiple servers with different paths?

Regards,

[geoffrey.mcgill]

Can you try adding the following path with the ~ application root relative path instead?

// Existing
new NavItem("Dashboard", "/", "dashboard"),

// Revised
new NavItem("Dashboard", "~/", "dashboard"),