Ticket T150618
Visible to All Users

Usability.Web - Improve the Error.aspx page to be able to restart the application after a critical error

created 10 years ago

When the application show error page, I have to clear the cache of application. If I not do that, I can't load anything to the screen  because I will always direct me to the error page.

How can I solve this problem using better solution than clear browser cache?

Answers approved by DevExpress Support

created 10 years ago (modified 9 years ago)

We have implemented the functionality described in this ticket. It will be included in our next update(s).

Please check back and leave a comment to this response to let us know whether or not this solution addresses your concerns.

Additional information:

Starting with v14.2.6 we added a new "restart the application" link to the default error page that allows you to restart the app after a critical error.

Take special note that this functionality will be available by default in new XAF projects created using the Solution Wizard.
If want the same thing in existing XAF projects, just replace the three old Error page files in in YourSolutionName.Web project with the new ones copied from our demos (e.g., C:\Users\Public\Documents\DevExpress Demos 1X.X\Components\eXpressApp Framework\MainDemo\CS\MainDemo.Web) or a newly created XAF solution.
Refer to the http://dennisgaravsky.blogspot.com/2015/03/improved-erroraspx-page-that-allows-you.html blog for more details.

    Comments (2)
    GM GM
    Gustavo Marzioni 10 years ago

      In 14.2.6, using VB this functionality is not available

      Dennis Garavsky (DevExpress) 10 years ago

        @Gustavo: It seems that you forgot to update the Error page files in your existing project as per the blog post instruction:

        "it will be available in new XAF projects created using the Solution Wizard. If want the same thing in existing XAF projects, just replace the old Error page files in in <YourSolutionName.Web> project with the new ones copied from our demos or a new XAF solution."

        created 10 years ago (modified 10 years ago)

        Hello Tanakorn,

        Presently, you can use one of the following alternative options:

        1. Close your browser and reopen the failed XAF web site;
        2. Implement a custom Error.aspx solution outlined in the Q453492 ticket (the idea is to programmatically close the broken ASP.NET session and start over).
          We will see to improving UX in this situation in the future.

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.