• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 477
  • Last Modified:

Visual Studio 2010 ASP Design View Performance

I'm developing an ASP.Net website in Visual Studio 2010.  The design view is extremely sluggish.  Making minor adjustments to a page in the design view literally maxes CPU use for up to five minutes or longer.  

Are there any third party editors that offer a design view editor with better performance or are there any settings that can improve VS 2010 performance?
  • 5
  • 3
1 Solution
Bob LearnedCommented:
Is it only one web site?  How complex are your pages?  What kind of hardware are you working with?
MDKIMZEYAuthor Commented:
I have found that this occurs on any page that uses a MasterPageFile.  
If I remove the the MasterPageFile attribute, the designer performance is orders of magnitude better.  The MasterPageFile is moderately complex.  When the MasterPageFile is included, anything done in Design view takes at least 5 minutes of hard disk churning activity before the next thing can be done.
Intel(R) Core(TM) 2CPU
6700 @ 2.66GHz
2.66 GHz, 2.00 GB of RAM
239 GB Hard Drive Capacity - 79 GB Free
All other applications perform fine.
Currently the best workarounds seem to be:
  1. Temporarily remove the MasterPageFile attribute from the Source before switching to the Design view.
  2. Only work in Source (Ignore Split and Design Views)
The next thing I will try is commenting out sections of the MasterPageFile to see if there are specific items that impede Designer performance.
Bob LearnedCommented:
Can you give me some kind of idea what the master page looks like?  You haven't indicated anything yet that sets off any alarm bells, other than the 5 minutes thing.
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

MDKIMZEYAuthor Commented:
The site master includes:

  • script src statements for jQuery dialog and calendar
  • Html.DevExpress().RenderStyleSheets(...) for Menu, NavBar, PageControl, Tab Control and GridView
  • Html.ActionLink for the main site pages.
I suspect that the Html.DevExpress().RenderStyleSheets(...) is the prime suspect.
Bob LearnedCommented:
It now appears that you are using the MVC pattern, and I guess at version 2.0.  The MVC pattern with the DevExpress tools is an unknown, so anything is possible.  What happens if you don't call the RenderStyleSheets?
MDKIMZEYAuthor Commented:
Actually DevExpress has released a GridView and a few other controls for MVC.
I suspect the RenderStylesheets are the cause.  I will try this.
MDKIMZEYAuthor Commented:
Thus far, it seems to happen when:

  • The page contains a MasterPageFile that contains items such as:
    • RenderStyleSheet

  • The page contains style sheet
I have found that if you need the designer, the best approach by far is:

  1. Comment out all references to MasterPageFiles and StyleSheets prior to opening the page in the VS 2010 Designer

  2. Or - always edit the page as source.  - All developers at my work place use source - precisely because the performance of the VS 2010 designer is so poor.
MDKIMZEYAuthor Commented:
Still something of an open issue with workarounds.

Thus far:
1. This issue is easy to reproduce - simply add a MasterPageFile with style sheets or RenderStyleSheets

2. Most web developers that I have talked to avoid the VS Designer precisely because the performance is so poor.

3.  I don't know of any third-party alternatives to the VS Designer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now