Ticket T655717
Visible to All Users
Duplicate

Visual Studio Designer has very slow performance on opening and saving changes

created 7 years ago

[DevExpress Support Team: CLONED FROM KA18788: Visual Studio 2017, 2015, 2013, 2012, 2010 performance is very slow when a page with ASP.NET controls is opened in Designer]

Here is a page with very slow Performance when is opened in Designer

Comments (2)
DevExpress Support Team 7 years ago

    Hi Dirk,

    Your page refer to a master page that is not attached. Would you please attach all necessary pages? This will help me to test your layout.

    DevExpress Support Team 7 years ago

      Hello,

      I do not see any of our controls in the provided project. Please make sure that you provided us with a correct sample. Would you please modify it or send us another project where the issue is reproduced? We will research it and offer you the most suitable solution.

      Answers approved by DevExpress Support

      created 7 years ago (modified 7 years ago)

      Hello Dirk,

      Thank you for your sample project. I was able to see the issue. I've noticed that your "Default.aspx" page has a lot of components. Because of this, Visual Studio performance is extremely slow if the Designer is enabled. Our controls have numerous properties that allow detailed customization of components. However, it looks like the Visual Studio Designer still uses old algorithms that serialize all properties of all controls. If a control has several properties, the designer processes it quicker than a control with many properties. Microsoft has not upgraded the designer for years; the designer still uses IE7 inside. At the same time, the web form Designer's efficiency is much less than that of the Windows Forms one. So, I recommend you add controls directly into ASPx page markup and check the page layout in a browser instead of the designer as Paul Usher suggested in the ASP page saving / upadting is very slow with DevExpress controls thread, so you can try utilizing it in your application:
      One workaround for this problem that does not require the additional work of user controls is to edit the code only, NOT using the split (source|design) screen. You don't need the designer window open in Visual Studio at all. To see changes you are making in the markup almost instantly, simply run up a copy of the web application, when the browser has your pages displayed, stop the application from running. This still leaves the instance if IIS Express running still serving up the web page. When you make changes to the markup, CTRL+S (or file, save) is instant, and then a refresh on the browser page renders the new page layout almost instantly (depending on your data bindings).
      Other things to note, in my tests I am running VS2012 with Update 4, and I also tested on VS2013. I was able to get the same speed and performance on my testing VM (running on 4gb ram on laptop*) as I did on my main dev machine.*
      If you still wish to use the Visual Studio Designer, please refer to the following articles that might be helpful:
      ASP page saving / upadting is very slow with DevExpress controls
      Saving an ASP.NET page at design time is very slow in Visual Studio 2013, 2012, 2010
      In the Visual Studio 2013, 2012, 2010 performance is very slow when a page with ASP.NET controls is opened in Designer article, Vladimir suggested the approach that allows resolving this issue. However, in your code I do not see the use of it. So try separating a page layout into several UserControls.

      UPDATED:
      While Vladimir is out of the office these days, I've modified your sample project to demonstrate the idea from the mentioned KB article. I did the following:

      1. Inspected your markup and noticed that the "frm_Charter" ASPxFormLayout control takes more than 1000 lines there.
      2. Isolated this control into a separate UserControl and placed this user control inside the "pnl_Chartermanagement" panel.
        I've attached a video and the modified sample project to demonstrate that making and saving changes operates much faster. It's not necessary to put exactly this "frm_Charter" into a user control. You could do this with any component on the page, but the idea remains the same: reducing the page's markup by moving some controls or groups of controls into UserControls.
        Let me know if you have further questions.
        Show previous comments (6)
        DevExpress Support Team 7 years ago

          I am happy to hear that! Let me know if you face any issue after upgrading.

            Can you say me, when Version 18.1.5 will be publish?

            DevExpress Support Team 7 years ago

              If all goes as expected, version 18.1.5 will be released in a week.

              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.