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

Page 1 of 2 12 LastLast
  1. #1

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

    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:

    Click image for larger version. 

Name:	Annotation 2020-11-09 151324.jpg 
Views:	78 
Size:	46.9 KB 
ID:	25459

    in comparison within the original application deployed on local environment:

    Click image for larger version. 

Name:	Annotation 2020-11-09 151453.jpg 
Views:	63 
Size:	74.9 KB 
ID:	25460

    Can you help me please.

    Regards,
  2. #2
    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.
    Geoffrey McGill
    Founder
  3. #3
    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
  4. #4
    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!
    Fabrício Murta
    Developer & Support Expert
  5. #5
    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,
  6. #6
    Can you try adding the following path with the ~ application root relative path instead?

    // Existing
    new NavItem("Dashboard", "/", "dashboard"),
    
    // Revised
    new NavItem("Dashboard", "~/", "dashboard"),
    Geoffrey McGill
    Founder
  7. #7
    Hello,

    I tried also but with no success.

    Regards,
  8. #8
    Hello @Geovision!

    Can you tell us what you configure on your web server to prepend that /ffmsadmintoolmvc path to your published website?

    I would expect the ~/ substitution to work but if it doesn't, there is most likely a way to get that path as it will always be / on localhost and /ffmsadmintoolmvc/ in production. I just need to know what is that setting name so I can research how we can programmaticaly get that value so that the website works on both local and different public hosting environments.

    Are you, maybe, using a public hosting company to host your website, or doing that straight from your own Windows Server?
    Fabrício Murta
    Developer & Support Expert
  9. #9
    In _Navigation.cshtml, replace the <a> tag with the following @Url.Content(...) call:

    // Old
    <a href="@item.Path" class="@(cls)">
    
    // New
    <a href="@Url.Content(item.Path)" class="@(cls)">
    And you would still require the ~/ prefix as suggested above.

    The paths used to build those html navigation links are not controlled by Ext.NET, so you would just need to resolve using whatever ASP.NET technique you prefer.

    Hope this helps.
  10. #10
    Hello,

    I tried all the above suggestions and it doesn't work for me.

    Regards,
Page 1 of 2 12 LastLast

Similar Threads

  1. Ext.NET 7.0 Classic for ASP.NET Core Now Available
    By geoffrey.mcgill in forum Open Discussions
    Replies: 0
    Last Post: Oct 08, 2020, 4:36 PM
  2. [CLOSED] Ext.Net.MVC.Demo v1.x IIS deployment issues
    By vadym.f in forum 1.x Legacy Premium Help
    Replies: 13
    Last Post: Jun 07, 2013, 11:41 AM
  3. [CLOSED] IIS 7.5 deployment
    By tanky65 in forum 2.x Legacy Premium Help
    Replies: 4
    Last Post: Jan 25, 2013, 2:51 PM
  4. [CLOSED] Deployment to IIS guide
    By zwf in forum 2.x Legacy Premium Help
    Replies: 1
    Last Post: Oct 09, 2012, 11:21 AM
  5. [CLOSED] EXT is not defined on IIS deployment
    By CMA in forum 1.x Legacy Premium Help
    Replies: 4
    Last Post: Jan 14, 2011, 10:30 AM

Posting Permissions