locked
Visual Studio 2008 HTML Designer unusably slow in source mode. RRS feed

  • Question

  • I was recently experiencing very slow performance in the designer (in source mode) in VS2008.  I had operated fine for 18 months in VS2005 and figured it was some sort of interoperability problem with either 2005 or one my other applications.  So I decided it was time for a fresh install.

     

    I wiped my laptop (Compaq nc8430 with 2GB RAM, T2500 (2Ghz) processor) and reinstalled XP with all the latest patches, installed office 2007 ultimate, visual studio 2008, Essential Object EO.MENU controls, google toolbar, windows search 3.01, magicdisk and that is it.

     

    But VS2008 is still unusable.  The performance problems are usually msot evident when Intellisense is doing it's thing with autofilling code or presenting members.

     

    The project I'm working on fairly large, but not hugely so.  It was written on vs2005 and I have NOT upgrade it to .net framework 3.5.

     

    I'm at loss at how I can address my performance problem.  Any help would be greatly appreciated.

     

    Jason

    Sunday, December 30, 2007 10:09 PM

Answers

  • FYI, we think we may have isolated the cause somewhat.  If you disable all HTML validation, this problem seems to either go away entirely or have its frequency of occurance reduced significantly.

     

    You can go to Tools --> Options --> Text Editor --> HTML --> Validation and clear the 'Show errors' checkbox to completely disable any HTML validation at all.  When this is done, the indiscriminate pause seems to go away on at least the few PCs we have initially tested on.

     

    If the cause of this is related to the HTML validation engine somehow blocking on the main IDE UI thread as it parses the HTML in source view, then that would seem to be further supported by the posts that suggest this 'bug' gets worse the larger the HTML file.  Perhaps the validation engine can parse smaller files before you might notice the blocking, but in larger files the processing time is long enough that you notice it and in really large files it gets downright unusable due to the lag from the slow parsing/validation process.

     

    Other thoughts?  Anyone?  Agree that this pretty much renders the VS 2008 HTML editor all but unusable...seems hard to imagine that noby thought to test this against anything but small HTML files before its release Sad

    Saturday, January 5, 2008 1:47 AM
  • Not it's very slow is source mode. This with no 3rd party controls installed.  It is the same issue mentioned here:

     

    https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=320146


     

    And here:

     

    http://forums.asp.net/t/1194031.aspx?PageIndex=1


     

     

    Monday, January 7, 2008 1:44 PM
  • From Scott Guthrie (in Comments):

     

    "There is a hotfix you'll be able to download that we think fixes the slowness in source mode that some people have reported with certain large HTML files.  This will hopefully be available late this week or next week.  I'll blog about it once it is available."

     

    http://weblogs.asp.net/scottgu/archive/2008/01/24/jan-24th-links-asp-net-asp-net-ajax-visual-studio-net-iis.aspx

     

     

     

    Tuesday, January 29, 2008 2:53 PM
  • Per this post, the hotfix to address this issue is now released...

     

    http://weblogs.asp.net/scottgu/archive/2008/02/08/vs-2008-web-development-hot-fix-roll-up-available.aspx

     

    "One of the things we are trying to do with VS 2008 is to more frequently release public patches that roll-up bug-fixes of commonly reported problems.  Today we are shipping a hot-fix roll-up that addresses several issues that we've seen reported with VS 2008 and Visual Web Developer Express 2008 web scenarios."

     

    Bravo to MS for responsiveness on this issue; no wait for SP1 Smile

    Saturday, February 9, 2008 2:13 AM
  • I think I found the problem.

     

    I had some third-party controls added to the toolbox and reference section.

     

    Gaia and Developer Express

     

    I removed them and my designer/text editor is normal now.

     

    Hopefully, I won't need these controls and problem will not resurface. You never know.

    Monday, March 24, 2008 4:56 AM
  • I have the same problem with performance, in Designer and Source View. When I applied the hotfix, things got better, but the performance is still not good, especially during save in Source View. I have Developer Express controls, and I happen to need them, so removing the toolbox and reference section is out of the question.

    Any solutions if I truly want to use third party controls?

    * UPDATE * It seems that the solution that was given in http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=657867&SiteID=1 also works for the specific issue! After disabling checks for certificate revocation, the save in VS 2008 takes up normal time again...
    Saturday, March 29, 2008 10:57 AM

All replies

  • More information:

     

    In my aspx file (not code behind), I have ~4000 lines of code -- mostly HTML with some javascript interspersed.  I tried delting the last 3000 lines to test if it was some weird indexing problem.  Sure enough the extreme lag Intellisense was exhibiting disappeared.

     

    Is there some kind option that I can set can prevent this from happening?  If it helps I very rarely use the design view so I can do without that.

     

    Jason

     

    Monday, December 31, 2007 2:19 PM
  • Hi Jason

     

    I understand so far is that when you only switch to design view of the pages in VS2008, it suddenly slows down, if any misunderstanding here, please correct me.

     

    I'd like to isolate something.

    What version of .NET Framework assemblies does your website reference? (Have you successfully installed .NET Framework 3.5, please use .NET Framework 3.5 Installation validation tool: http://blogs.msdn.com/aaronru/archive/2007/11/29/net-framework-3-5-installation-validation-tool.aspx to look into it)

    Does a plain HTML page have this problem? Does simply drag an ASP.NET control say textbox onto a blank page within a new website project have problem?

     

    Meanwhile, you can try to

    1. Reboot the machine into Safe Mode. Do we still have the problem? This can isolate some third party application/driver’s interference.
    2. If we switch to try a new user account, do we have the problem? This can rule out the possibility of corrupted user profile.
    3. Do we have any third party add-ins loaded? Disable them with “Tools” | “Add-in Manager…”.

    4. Check is there "Microsoft Visual Studio Web authoring Component" in ARP(Add/Remove Program), if it does, uninstall it and go to your installation CD install it again from \WCU\WebDesignerCore\WebDesignerCore.EXE

     

    Thanks

    Tuesday, January 1, 2008 4:03 AM
  • Hi,

    We are have the same exact problem in our development group - tested on a bunch of dev machines, some of which also have VS2005 installed, some others are brand new (most are XP but also one Vista Business) - the aspx file has 1000 lines and editing xml markup is perfectly fine in VS 2005 but it constantly freezes for seconds to minutes in VS 2008 - sometimes just after moving cursor positon, sometimes it allows to type a word or two and then starts freezing... while freezing you can see hard drive working - memory swap? All machines are intel core 2 duo (1.8 Ghz and up) and all have 2 Gig of ram...

    It's clearly an issue with VS 2008. I hope microsoft comes up with a fix... currently we have to use an  external xml editor to make changes to that file, which is bizzare (why the hell do we need an IDE then?)...

    Andrey
    Wednesday, January 2, 2008 4:16 PM
  • This is incredibly annoying. Anyone find a solution for this?

    • Proposed as answer by Slacker144 Wednesday, December 2, 2009 10:00 AM
    Thursday, January 3, 2008 7:15 PM
  • Anyone form Microsoft? Figo Fei? We love VS2008 and realy want to use it, but with its current state we just can't...
    If I don't find a solution to the problem by next week, we'll have to reverse th eproject back to VS2005 and ship hundred of boxed VSS 2008 back to microsoft...

    Please Microsoft give us your clients some attention!

    • Proposed as answer by Slacker144 Thursday, December 3, 2009 3:01 AM
    Friday, January 4, 2008 12:37 AM
  • Hi Muzzzy

     

    Thank you for your feedback, and could you help me to do some narrow down steps:

    Please try to use .NET Framework 3.5 Installation validation tool: http://blogs.msdn.com/aaronru/archive/2007/11/29/net-framework-3-5-installation-validation-tool.aspx to look into it)

    Does a plain HTML page have this problem? Does a newly created ASP.NET website has this problem?

    If the problem doesn't happen to a new simple ASP.NET web page created in VS2008, I could narrow down the cause within your project or page, in this case could you supply the reproduce page (perhaps with thousands of HTML lines)

     

    Meanwhile, you can try to

    1. Reboot the machine into Safe Mode. Do we still have the problem? This can isolate some third party application/driver’s interference (Note that some features (like IIS) are not available under safe mode. Please check whether this can apply or not. In addition to safe mode, we can also suggest “clean boot”: http://support.microsoft.com/kb/310353.)
    2. If we switch to try a new user account, do we have the problem? This can rule out the possibility of corrupted user profile.
    3. Do we have any third party add-ins loaded? Disable them with “Tools” | “Add-in Manager…”.

    4. Check is there "Microsoft Visual Studio Web authoring Component" in ARP(Add/Remove Program), if it does, uninstall it and go to your installation CD install it again from \WCU\WebDesignerCore\WebDesignerCore.EXE

     

    Thanks

    Friday, January 4, 2008 3:22 AM
  • Guys,

     

    I can't work like this!

     

    I love the product but the delays in the html source are unbearable!

     

    Please help...

     

    Mick

     

    Friday, January 4, 2008 2:36 PM
  •  

    Same here! Two machines running Vista Ultimate x64 edition. One completely clean install with no VS.net 2005 the other with it and we both have the same problem!

     

    This is brutal! We need to get this fixed ASAP!

    Friday, January 4, 2008 2:43 PM
  • Figo,

    I know these are standard steps you have to ask for, but isn't it obvious from the multiple posts that the problem is not isolated to just my particular machine? You can see other people reporting the same issue; aslo as I've mentioned we have over 30 machines running VS2008, some of which are clean installs over brand new and shiny windows xp (some are windows vista) so the steps you posted are not relevant at all - this is not a probelm with a computer, this is a problem with the product!

    Please lets not play the game of going back and forth as you can easily reproduce this in any environment - just try to work with an aspx file which is over 1000 lines in VS 2008 and you will feel our pain...

    Interesting enough, I took a brand new machine running intel core 2 extreme (QX9650) which is the fastest so far and I see the same exact issue - I have a very strong feelng that it does some twisted thing with read/write (looks like IntelliSence or editor highlighter) - you can see the hard drive working hard during these freezes (doesnt look like memory swapping as I have plenty memory left out of my 3 Gb of RAM)

    Microsoft - please lets try to find some resolution!

    - Andrey (and a whole bunch of other frustrated developers all over the world)

    Friday, January 4, 2008 3:07 PM
  • I have to report that I can also confirm this problem on at least three separate PCs in our company.  During the 'pause' the processor utilization doesn't 'spike' to 100%, but definitely increase in load.  Some of these are 'plain vanilla' VS 2008 installs and others have add-ins present so that would seem to not be a differentiator for the problem.

     

    BTW, we don' t need anything approaching a 1000-line HTML file to recreate the problem in our environment; the following file (204 lines) evidences the problem on our systems and I think we all have to agree that there is nothing terribly unusual about this file (its just a tab control from the asp.net ajax toolkit plus some hrefs on each tab -- the code-behind is near-empty).

     

    Code Block

    <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="WebSite._Default" %>

    <%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="ajaxtoolkit" %>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head runat="server">
        <title>Microdesk Development Group Launch Page</title>
        <link href="WebSite.css" rel="stylesheet" type="text/css" />
    </head>
    <body>
        <form id="form1" runat="server">
        <asp:ScriptManager runat="server">
        </asp:ScriptManager>
        <div>
            <img src="Microdesk_Logo_Plus_Name.gif" alt="Microdesk Logo" />
        </div>
        <div>
            Software Development Group</div>
        <br />
        <ajaxtoolkit:TabContainer ID="TabContainer1" runat="server" ActiveTabIndex="0" ScrollBars="Auto">
            <ajaxtoolkit:TabPanel ID="tabDevTools" runat="server" HeaderText="Dev Web Tools">
                <ContentTemplate>
                    <ul>
                        <li><a href="http://development.microdesk.com/projects" target="_blank">Target Process</a></li>
                        <li><a href="http://development.microdesk.com/projects/tptray/tptray-setup.zip">Download
                            Target Process TPTray Utility (latest)</a></li>
                    </ul>
                    <ul>
                        <li><a href="http://development.microdesk.com/vaultservice" target="_blank">Vault Home
                            Page (download Vault Client, etc.)</a></li>
                        <li><a href="http://development.microdesk.com/VaultService/VaultWeb/login.aspx" target="_blank">
                            Vault Web Client</a></li>
                    </ul>
                    <ul>
                        <li><a href="http://development.microdesk.com/forum" target="_blank">Development Group
                            Forum</a></li>
                        <li><a href="http://forum.microdesk.com/cs" target="_blank">Weekly Workload Blog</a></li>
                    </ul>
                    <ul>
                        <li><a href="http://development.microdesk.com/bugs" target="_blank">Gemini Bug Tracking
                            (depricated)</a></li>
                    </ul>
                </ContentTemplate>
            </ajaxtoolkit:TabPanel>
            <ajaxtoolkit:TabPanel ID="tabMiscTools" runat="server" HeaderText="Misc Tools">
                <ContentTemplate>
                    <ul>
                        <li><a href="http://www.launchy.net" target="_blank">Launchy</a></li>
                        <li><a href="http://www.pnotepad.org" target="_blank">Programmer's Notepad</a></li>
                        <li><a href="http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm" target="_blank">
                            Toad for SQL Server</a></li>
                    </ul>
                </ContentTemplate>
            </ajaxtoolkit:TabPanel>
            <ajaxtoolkit:TabPanel ID="tabVS2008Addins" runat="server" HeaderText="Visual Studio 2008 Addins">
                <ContentTemplate>
                    <ul>
                        <li><a href="http://development.microdesk.com/downloads/GhostDoc2.1.2for2008.zip">GhostDoc
                            for Visual Studio 2008</a></li>
                        <li><a href="http://development.microdesk.com/downloads/DXCore-3.0.5.zip">DevExpress
                            DXCore v3.0.5</a></li>
                        <li><a href="http://development.microdesk.com/downloads/Misc_PlugIns_DXCore-3.0.5.zip">
                            Miscellaneous PlugIns for DevExpress DXCore v3.0.5</a></li>
                        <li><a href="http://development.microdesk.com/downloads/CoolCommands40.zip">Cool Commands
                            4.0</a></li>
                        <li><a href="http://development.microdesk.com/downloads/StudioToolsSetup.zip">Studio
                            Tools</a></li>
                        <li><a href="http://development.microdesk.com/downloads/SpellChecker2008.zip">Spell-Checker</a></li>
                    </ul>
                </ContentTemplate>
            </ajaxtoolkit:TabPanel>
            <ajaxtoolkit:TabPanel ID="tabVS2005Addins" runat="server" HeaderText="Visual Studio 2005 Addins">
                <ContentTemplate>
                    <ul>
                        <li><a href="http://msdn2.microsoft.com/en-us/vstudio/aa718340.aspx" target="_blank">
                            Visual Studio 2005 PowerToys: Homepage</a></li>
                        <li><a href="http://www.codeplex.com/PackInstaller" target="_blank">Visual Studio 2005
                            PowerToys: Manager</a></li>
                        <li><a href="http://www.codeplex.com/SourceCodeOutliner" target="_blank">Visual Studio
                            2005 PowerToys: Source Code Outliner</a></li>
                        <li><a href="http://development.microdesk.com/downloads/GhostDoc2.1.2for2005.zip">GhostDoc
                            for Visual Studio 2005</a></li>
                        <li><a href="http://development.microdesk.com/downloads/DXCore-2.2.2.zip">DevExpress
                            DXCore v2.2.2 (depricated)</a></li>
                        <li><a href="http://development.microdesk.com/downloads/Misc_PlugIns_DXCore-2.2.2.zip">
                            Miscellaneous PlugIns for DevExpress DXCore v2.2.2 (depricated)</a></li>
                        <li><a href="http://development.microdesk.com/downloads/SpellChecker2005.zip">Spell-Checker</a></li></ul>
                </ContentTemplate>
            </ajaxtoolkit:TabPanel>
            <ajaxtoolkit:TabPanel ID="tabTestingTools" runat="server" HeaderText="Unit Testing Tools">
                <ContentTemplate>
                    <ul>
                        <li><a href="http://development.microdesk.com/downloads/mbunit-2.4.197.zip">MbUnit 2.4
                            RTM</a></li>
                        <li><a href="http://development.microdesk.com/downloads/mbunit.documentation.zip">MbUnit
                            chm-format documentation package</a></li>
                        <li><a href="http://development.microdesk.com/downloads/Testdriven.net-2.11.2177_personal.zip">
                            Testdriven.NET 2.11.2177 installer</a></li>
                        <li><a href="http://development.microdesk.com/downloads/Ncover-1.5.8.zip">NCover 1.5.8
                            installer</a></li>
                    </ul>
                </ContentTemplate>
            </ajaxtoolkit:TabPanel>
            <ajaxtoolkit:TabPanel ID="tabBlogPosts" runat="server" HeaderText="SkillPortal Blog Posts">
                <ContentTemplate>
                    <div>
                        Following is a list of all the blog posts from the 'Inside the Sausage Factory'
                        series on Steve Bohlen's blog.</div>
                    <ul>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!147.entry"
                            target="_blank">Inside the Sausage Factory: PART 01 (Preamble)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!148.entry"
                            target="_blank">Inside the Sausage Factory: PART 02 (Buy vs. Build?)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!150.entry"
                            target="_blank">Inside the Sausage Factory: PART 03 (_DD)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!151.entry"
                            target="_blank">Inside the Sausage Factory: PART 04 (Feature Driven Development)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!152.entry"
                            target="_blank">Inside the Sausage Factory: PART 05 (Ranking Features)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!168.entry"
                            target="_blank">Inside the Sausage Factory: PART 06 (Data by Design)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!177.entry"
                            target="_blank">Inside the Sausage Factory: PART 07 (Refining the Data Model)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!178.entry"
                            target="_blank">Inside the Sausage Factory: PART 08 (Scripting the Database)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!185.entry"
                            target="_blank">Inside the Sausage Factory: PART 09 (Layers and Foundations)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!186.entry"
                            target="_blank">Inside the Sausage Factory: PART 10 (Choosing The Vietnam of Computer
                            Science...on purpose!)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!195.entry"
                            target="_blank">Inside the Sausage Factory: PART 11 (Dynamic Data Transfer Layer)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!208.entry"
                            target="_blank">Inside the Sausage Factory: PART 12 (UI Mockup)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!209.entry"
                            target="_blank">Inside the Sausage Factory: PART 13 (Data Access Design)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!210.entry"
                            target="_blank">Inside the Sausage Factory: PART 14 (One-liners: the power of libraries)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!219.entry"
                            target="_blank">Inside the Sausage Factory: PART 15 (Strategies for dynamic, ad-hoc
                            run-time queries)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!222.entry"
                            target="_blank">Inside the Sausage Factory: PART 16 (burn-down rates -- reality-check!)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!225.entry"
                            target="_blank">Inside the Sausage Factory: PART 17 (Approach to testing the DAL)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!226.entry"
                            target="_blank">Inside the Sausage Factory: PART 18 (Building Data-dependent Unit
                            Tests)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!231.entry"
                            target="_blank">Inside the Sausage Factory: PART 19 (Coding the Data-dependent Unit
                            Tests)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!236.entry"
                            target="_blank">Inside the Sausage Factory: PART 20 (Detour to fix NDbUnit Foreign
                            Keys)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!239.entry"
                            target="_blank">Inside the Sausage Factory: PART 21 (On Model-View-Presenter Patterns)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!242.entry"
                            target="_blank">Inside the Sausage Factory: PART 22 (Mocking the View)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!243.entry"
                            target="_blank">Inside the Sausage Factory: PART 23 (Detour...derailed by CIFactory)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!244.entry"
                            target="_blank">Inside the Sausage Factory: PART 24 (NAnt MbUnit task filter detour)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!247.entry"
                            target="_blank">Inside the Sausage Factory: PART 25 (Arrested by an FxCop)</a></li>
                        <li><a href="http://unhandledexceptions.spaces.live.com/blog/cns!FC56A7CB585DF52F!256.entry"
                            target="_blank">Inside the Sausage Factory: PART 26 (Building The Dumb View)</a></li>
                    </ul>
                </ContentTemplate>
            </ajaxtoolkit:TabPanel>
            <ajaxtoolkit:TabPanel ID="TabDD2008" runat="server" HeaderText="Dine + Discuss 2008">
                <ContentTemplate>
                    <h3>
                        Dine + Discuss Schedule of Topics for 2008</h4>
                        <div>
                            Following is a list of topics for 2008's Dine + Discuss sessions; after each session
                            is completed, the session topic text will become a link to the download(s) from
                            the session (ppt files, etc.).
                        </div>
                        <ul>
                            <li>01/09/2008: if you're not using VS 2008 right now, YOU SHOULD BE (and here's why)</li>
                            <li>01/16/2008: Effective unit testing (mbunit), mock objects (rhino mocks), and database
                                testing tools (NDbUnit)</li>
                            <li>01/23/2008: recipe: the 10-minute DAL (starring NHibernate and the usual cast of
                                characters)</li>
                            <li>01/30/2008: C#3.0/VB.NET9.0 language changes including lambda methods, extension
                                methods, and more</li>
                            <li>02/06/2008: .NET 3.0 Pillar Number 1: the oft-delayed WF (windows workflow) session</li>
                            <li>02/13/2008: .NET 3.0 Pillar Number 2: WCF (Windows Communication Foundation)</li>
                            <li>02/20/2008: .NET 3.5 enhancements including LINQ</li>
                            <li>02/27/2008: ASP.NET MVC ins, outs, pros, cons</li>
                        </ul>
                </ContentTemplate>
            </ajaxtoolkit:TabPanel>
        </ajaxtoolkit:TabContainer>
        <div class="footer">
            Comments, additions, suggestions for content for this site, please <a href="mailto:sbohlen@microdesk.com">
                e-mail Steve Bohlen</a>.</div>
        <div>
            <a href="http://www.searchdotnet.com" target="_blank">
                <img src="searchnet50.jpg" alt="SearchDotNet.com" /></a></div>
        </form>
    </body>
    </html>

     

     

    Friday, January 4, 2008 3:21 PM
  • Just out of curiosity, is everyone here experiencing the problem using AJAX or the AJAX Toolkit?

    Friday, January 4, 2008 3:29 PM
  • BTW, I think these two posts are related:

     

    http://forums.asp.net/p/1194031/2073430.aspx

    Friday, January 4, 2008 4:20 PM
  • just to register on this forum also that I have the same problem.

     

    Friday, January 4, 2008 5:38 PM
  • I certainly am in the page sample I provided.  I can try to remove the AJAX toolkit (and the ajax extensions) from my page, but its hard to see how that contributes to this problem.  What are you thinking might be the contributing aspect re: the ajax toolkit/extensions?

     

    -Steve B.

    Saturday, January 5, 2008 1:20 AM
  • FYI, we think we may have isolated the cause somewhat.  If you disable all HTML validation, this problem seems to either go away entirely or have its frequency of occurance reduced significantly.

     

    You can go to Tools --> Options --> Text Editor --> HTML --> Validation and clear the 'Show errors' checkbox to completely disable any HTML validation at all.  When this is done, the indiscriminate pause seems to go away on at least the few PCs we have initially tested on.

     

    If the cause of this is related to the HTML validation engine somehow blocking on the main IDE UI thread as it parses the HTML in source view, then that would seem to be further supported by the posts that suggest this 'bug' gets worse the larger the HTML file.  Perhaps the validation engine can parse smaller files before you might notice the blocking, but in larger files the processing time is long enough that you notice it and in really large files it gets downright unusable due to the lag from the slow parsing/validation process.

     

    Other thoughts?  Anyone?  Agree that this pretty much renders the VS 2008 HTML editor all but unusable...seems hard to imagine that noby thought to test this against anything but small HTML files before its release Sad

    Saturday, January 5, 2008 1:47 AM
  • Hi

     

    Thank you for your feedback and you can submit the issue to the connect project portal : http://connect.microsoft.com/VisualStudio with detail description.

    And our developer can evaluate seriously and check if it is a product issue.
    Additionally, I also suggest you to input the feedback link here later, so that it will benefit other members in the community.

    Thanks
    Monday, January 7, 2008 4:02 AM
  • Not it's very slow is source mode. This with no 3rd party controls installed.  It is the same issue mentioned here:

     

    https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=320146


     

    And here:

     

    http://forums.asp.net/t/1194031.aspx?PageIndex=1


     

     

    Monday, January 7, 2008 1:44 PM
  • All of our current projects are still using the 2.0 framework.  I have run the validation tool and it says the 3.5 framwork is installed successfully.

     

    You can easily reproduce this problem.  Create a sample project and throw 20 or 30 controls on the form and then try typing in source mode.  Honestly, I'm not sure how this got past QA.

     

    Monday, January 7, 2008 1:47 PM
  • I see almost no increase in CPU, but I do see a lot of drive activity.  I also see solution explorer flashing like it is being rebuilt.  Closing solution explorer helps some.  I believe this has to do with the synch between the source view and the design view.  Part of what supposed to make the design view so fast is killing the performance of the source view.  Personally I can do without the design view -- I almost never use it.

     

    Monday, January 7, 2008 1:51 PM
  • JDWilson:

     

    Have you experimented with my suggestion of disabling the HTML validation at all--?  This seems to mitigate the problem somewhat for us on several of our systems though not entirely.

     

    We are continuing further testing and, yes, the links to both the asp.net forum post and the existing VS 2008 bug report are indeed this same issue.

     

    I would again reiterate that the frequently-mentioned aspect of this needing to involve 3rd-party controls is a red herring -- it occurs for us with nothing but built-in (MS-provided) controls unless we want to consider the ASP.NET AJAX toolkit a 3rd-party control (and maybe we should, since its technically not exclusively by MS but also contains controls by others -- the our problem occurs even if we use only MS-authored controls from the AJAX Toolkit).

     

    -Steve B.

     

    Tuesday, January 8, 2008 1:09 AM
  • I did.  I also tried disabling intellisense.  Both work to some extent.  Although larger applications still are almost unusable in 2008.  I've gone back to 2005 until this issue is resolved.

    Tuesday, January 8, 2008 1:52 PM
  • I have been experiencing this as well. It doesn't matter if I'm using .NET 3.0 or 3.5. I do not have any 3rd party utilities installed. Moving from source to designer gets exponentially longer the larger and more complex the page. Even when I was working on relatively simple pages I found the transition to be annoying.

    After going into Tools - Options - Text Editor - Html - Validation. Then unchecking show errors it goes nice and fast. It does seem that this error checking during the transition is causing the hesitation. I also did not experience any kind of noticable CPU activity while it waited.
    Wednesday, January 9, 2008 2:51 PM
  • WOW, I was about to take the VS2008 Team Suite edition CD and throw it out the window;  as performance was absolutely horrible.  Then I found this post and I turned off HTML validation show errors and BOOM, I decided to keep the CD.

     

    Thanks!

    Joe

     

    Saturday, January 12, 2008 6:14 PM
  • I turned off HTML validation as well, but unfortunately the problem did NOT go away for me. Did anyone else turn off HTML validation and still see this issue?

    Monday, January 14, 2008 7:27 PM
  •  

    Same here. validation off does NOT solve it for me either.
    Monday, January 14, 2008 7:29 PM
  • I had the same problem and after turning off the HTML validation, it seems to be better but it is not completely resolved.

    I was working with a 1400 line aspx page targeting 2.0 framework from VS2008.

     

     

    Monday, January 14, 2008 10:47 PM
  • As I mentioned in my post where I suggested this approach (disabling HTML validation) this isn't a silver bullet but is something that seems to help somewhat on some of our computers.  Whatever is going on here is much more complex than just slow HTML validation though disabling validation seems to remove a contributing factor.

     

    So far, we know the following...

    • its not related to 3rd-party controls (happens without non-MS controls)
    • large files are not required to demonstrate the issue tho larger files evidence the problem to a larger degree
    • its not related to multiple versions of VS installed SxS since a fresh install of VS2008 by itself in a fresh vm the issue
    • its not something about the aspx/html files being tested per-se since the same file demonstrates the issue on my desktop but refuses to demonstrate the issue on my laptop
    • its not exclusively about HTML validation, tho disabling this seems to help to varying degrees on some systems
    • its not about available RAM as the problem appears with plenty of avail. RAM on my 3GB desktop
    • its not about hard drive thrashing as there is very little change in drive activity when it happens
    • its not about processor utilization as there is very littel change in this when it happens either

    Here's a thought I just had tho as I look back at this laundry list of observations: the desktop PC this happens on is core-2 duo (dual-core CPU) whereas the laptop this doesn't happen on is an older P4 (single core) chip.  Since it acts a lot like a thread deadlock (even if its sort of only a temporary deadlock condition) its possible this is a resource-contention problem instead of a resource-limit problem.  Can anyone else on this thread report whether there is consistency across single vs. multi-core processors in re: the problem existing or not?

     

    Perhaps we can (all) gather enough info to better pinpoint the problem's cause.

     

    -Steve B.

     

    Tuesday, January 15, 2008 12:45 AM
  • Jason I completely agree with you. VS2008 is prohibitively slow. I hope the MS developers and listening and fix this promptly ASAP.....

     

    Tuesday, January 15, 2008 8:19 PM
  •  

    Steve, my machine is just a Pentium 4 (albeit, it has hyperthreading).

     

    From what I read, I believe MS was able to reproduce this problem. The question is, will they release this fix in sp1 or sooner? I ask because I seriously doubt they will release SP1 so soon after the release of 2008.

     

    -Jeff

    Wednesday, January 16, 2008 12:21 AM
  •  

    Jeff:

     

    I agree that they claim to have been able to reproduce it (which is -- in general -- good news for us that are having the issue) but I also agree with you that SP1 for VS 2008 may be a long way off (we all recall the Year + before 2005 SP1 was released).  There is hope that a pre-SP1 hotfix would be available sometime soon since the definition of a hotfix is typically "a patch for an issue a number of people are experiencing but that doesn't affect everyone" and that sure seems to be this one though I share your question too re: "will they actually fix it?".

     

    My reason for still continuing to try to isolate the problem is that there are also a (pretty large) number of bugs that were reported (and flagged as reproducible) that the VS 2008 team was well-aware of from the BETA and still didn't fix in the RTM.  From this I (sadly) conclude that 'reported and reproducible' does not on its face deterministically lead to 'fixed' in the next release/SP and so I have every reason to believe its at least possible that even after an SP1 for VS2008 this issue may still be unaddressed by the VS team.

     

    If I can find a work-around then not only do I get it working pre-hotfix/pre-SP1, but I also ensure that if MS doesn't consider this bug to be a high-priority I won't have to wait for VS 2011 to use the blasted HTML source editor Big Smile

     

    -Steve B.

    Wednesday, January 16, 2008 11:51 AM
  •  

    We despirately need a hotfix for this right away. Every one of our computers is experiencing this making Vs.net 2008 unusable at this point.

     

    I'd be willing to test the hotfix and let Microsoft know (i've done this before with .net 2.0 rewritting issues) if it solves the issues and work with them. We are Microsoft Partners as well.

     

    Thanks!

    Thursday, January 17, 2008 3:51 PM
  • I thought it would be useful for everyone to know that I volunteered to test this issue for Microsoft when I reported it via Connect and that they have provided me with a pre-release version of a hotfix which has indeed fixed the issue (on my setup at least).

     

    so shouldn't have to wait too long before the full hotfix is released.

     

    thanks.

    dave

     

     

    Friday, January 18, 2008 2:13 PM
  •  

    Sweet.

     

    I just finished a project that this issue became a major thorn in my side. I ended up doing most of my design in VS 2005 and the coding in VS 2008. I couldn't believe it when I would make one minor change in the source HTML and VS 2008 would take 3 minutes before I could work again. This is with those validation things turned off.

     

     

    Friday, January 18, 2008 3:08 PM
  •  

    Guys,

              Just been speaking to the DevExpress guys about the issue as it happens regularly with one of their controls.  They speak of 'testing' a preHotfix from Microsoft and that it fixes the issue.  Here is the blog post.

     

    http://community.devexpress.com/blogs/aspnet/archive/2008/01/17/vs-2008-issue-makes-aspxgridview-slow-in-design-mode.aspx

     

    I just hope Microsoft Release this patch publically ASAP.

     

    Chris

    Sunday, January 20, 2008 10:11 PM
  • Painfully frustrating! Hurry up with the fix.

     

    If I hit Save in VS, I still see a * next to the filename. Why are we seeing this kind of bug in version 9!?!

    Tuesday, January 22, 2008 4:26 PM
  •  

    ... because microsoft runs unit tests now and has few if any real QA people to TEST the software properly. (see Joel on Software for details)

     

    Oh, and they had 2 betas and then released it without bother to test it before release even with major new functionality being added between beta 2 and release and major bugs being fixed (i.e. the entire code designer was so buggy as to be unusable in a lot of cases in Beta 2, so there are stll major bugs left (go figure) in the final version because of things that were introduced because of bug fixes for the original bugs)

     

    Dumb development cycle, dumb testing, and a predicable outcome.  (See Windows Vista Shutdown procedure for more examples of the result of Microsoft's new testing methodology.)

    Tuesday, January 22, 2008 5:08 PM
  • I cannot even get this far. I just downloaded all the VS 2008 Express programs and created my Setup DVD. I first installed VB 2008 and it worked fine. After a reboot I tried to install the Web Authoring Component. It runs for about 2 minutes, then it freezes for a minute, then runs for a while and then freezes again. It never completes. I have tried three times, all with the same problem.

    I cannot even cancel the install. I cannot close down or restart. I have to power down the system. I am running Vista 32 on a 2Gb system with 170GB 15,000 rpm system drive. I have VS 2005 installed and working "fine", (some exceptions.)

     

     

    Wednesday, January 23, 2008 6:43 PM
  • I've seen exactly that with anti-virus software enabled (eg CA eTrust).  Make sure the real time scanner etc are not running.  Best of luck!

    Thursday, January 24, 2008 6:48 AM
  •  

    disabled the Virus scanner everything... and Microsoft have acknowledged its an actual bug and have a fix to some private developers... we want a public fix!
    Thursday, January 24, 2008 6:55 AM
  • Hi,

     

    Just wanted to let MS know .... I have the same issue. When typing in the HTML designer, each letter takes about 2 seconds. Can't use VS 2008 at all.

     

    How the hell did this pass beta test?????????

     

    MS ... THIS NEEDS TO BE FIXED NOW!

     

     

    M O J O
    Friday, January 25, 2008 6:20 AM
  • Another vote. I turned off validation, doesn't seem to help too much. The HTML file I am woking with as I write this has - get this - only 62 lines. This is very painful. Also, there are some bugs in the designer, which I have reported to MS already. Sometimes it's impossible to select a control in the designer, cursor movement is incorrect, and I can't paste text. I would attribute all these problems to the new Office 2007 designer now used by VS 2008, which has to be a huge bonehead mistake on the part of MS, to rely on some Office 2007 component like that. I don't know what's got into them.

     

    Speaking of Office 2007, I just uninstalled it and reinstalled Office 2003. It was just torture.

    Friday, January 25, 2008 7:37 PM
  • From Scott Guthrie (in Comments):

     

    "There is a hotfix you'll be able to download that we think fixes the slowness in source mode that some people have reported with certain large HTML files.  This will hopefully be available late this week or next week.  I'll blog about it once it is available."

     

    http://weblogs.asp.net/scottgu/archive/2008/01/24/jan-24th-links-asp-net-asp-net-ajax-visual-studio-net-iis.aspx

     

     

     

    Tuesday, January 29, 2008 2:53 PM
  •  

    I have this probelm on my Dual core laptop. Its slow in both HTML designer and when cutting code in the code editor. My laptop has 2gig ram and have noticed that vs2008 beta 2 seems to constantly hog more and more memory. I only have a light project but taskmanager reports it uses over 1.2 gig. Looks like some kind of memory leak problem. If I restart vs then the problem goes away for around 15mins before it becomes a problem again and gets worse as time goes on. Just thought I would throw my 2 pennies worth in. (Have disabled validation)
    Monday, February 4, 2008 7:08 AM
  • Per this post, the hotfix to address this issue is now released...

     

    http://weblogs.asp.net/scottgu/archive/2008/02/08/vs-2008-web-development-hot-fix-roll-up-available.aspx

     

    "One of the things we are trying to do with VS 2008 is to more frequently release public patches that roll-up bug-fixes of commonly reported problems.  Today we are shipping a hot-fix roll-up that addresses several issues that we've seen reported with VS 2008 and Visual Web Developer Express 2008 web scenarios."

     

    Bravo to MS for responsiveness on this issue; no wait for SP1 Smile

    Saturday, February 9, 2008 2:13 AM
  • The hotfix did not resolve my issue and made no noticeable changes whatsoever.

    I find myself being 50% less efficient because of this problem and I'm extremely frustrated at this point!
    Saturday, February 23, 2008 6:24 PM
  • Giovanni8089

     

    I had no luck either after installing it. However, it turns out that sometimes the installation fails silently. Check the date on this file:

     

    C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Microsoft.VisualStudio.Web.dll

     

    This is one of the 4 files the hotfix updates. Should be 2/1/2008, not 11/8/2007.

     

    Jim

    Saturday, February 23, 2008 6:46 PM
  • I have the very same problem in VS 2008, even after installing and checking the hotfix. When I click on an item in the designer, VS2008 hangs for at least 30 seconds, no matter how large the HTML source. This is very frustrating...

    Any new insights?


    Tuesday, February 26, 2008 10:28 AM
  • Friday, March 7, 2008 3:14 PM
  • Hi Everyone

     

    I've got exactly the same problem here - the hotfix did not make things better. I only use some small html-code with some databindings (No Ajax and so on). VS2008 freezes for about one minute or more - this after some clicks ! TERRIBLE!

     

    It's very frustrating, i can't work with this problem any longer... please fix it!

     

    Is there any Solution?

     

    Thank you

    Martin

     

    Tuesday, March 11, 2008 11:47 AM
  • Same problem here. Especially when working with grids and objectdatasources. When either clicking save or changing between views visual studio hangs..

     

    I have ended the Visual Studio 2008 task multiple times just today.. Installing the fix didn`t change anything.

     

    Using VS2008 Team System on a intel core 2 duo 3GHz, 4GB RAM machine running Win xp sp2.

    Tuesday, March 11, 2008 12:22 PM
  • I would guess that your design mode database settings are wrong and it's just timing out on the database access. I've had that happen and been cursing VS and it's been my own stupid fault because I"m not hooked up to the dev sql server or something.

    Tuesday, March 11, 2008 1:29 PM
  • Thanks for the reply, but it doesn`t seem like that is the problem. I have full access to the dev sql server. (The grids are using columns from a datatable and the objectdatasource is using methods from the tableadapter on the same datatable. the datatable is in a dataset class in the same solution. It shouldn`t access the server when saving the grid?)

     

    Did a simple test now and after running vs2008 for less than an hour I added a dropdownlist to a big aspx page, with two grids and two objectdatasources, in source view. And then saved. After 10 min of "saving" I ended the vs2008 task. When I started vs2008 once again and did exactly the same it works fine.. I`ll try again in an hour or so to check again

     

    Tuesday, March 11, 2008 2:00 PM
  • Stuck on saving once again..

     

    Tuesday, March 11, 2008 3:47 PM
  • I have been having this problem since yesterday - curiously since I started playing around with LINQ - but by turning off all accessibility checking in the IDE it seems to have fixed it.  Well, so far, so good anyway Smile

    Hope this helps.
    Wednesday, March 19, 2008 10:15 AM
  • Ok I am seeing very similar problems as all of you. This happens in both source and design modes (esp when saving or switching from one mode to the other). In general a simple control to select date/time causes a crash when switching to design mode or trying to work with. I all the hot fixes installed, I disabled validation, used all the tips to optimize everything else, and no luck. Absolutely impossible to work....


    Code Snippet

    <%@ Control Language="C#" AutoEventWireup="true" CodeBehind="DateTimeSelector.ascx.cs" Inherits="Blah.Blah.DateTimeSelector" %>
    <table width="400">
                    <tr>
                        <td>
                            <asp:DropDownList ID="ddlStartDateMonth" runat="server">
                                <asp:ListItem Value="1">01</asp:ListItem>
                                <asp:ListItem Value="2">02</asp:ListItem>
                                <asp:ListItem Value="3">03</asp:ListItem>
                                <asp:ListItem Value="4">04</asp:ListItem>
                                <asp:ListItem Value="5">05</asp:ListItem>
                                <asp:ListItem Value="6">06</asp:ListItem>
                                <asp:ListItem Value="7">07</asp:ListItem>
                                <asp:ListItem Value="8">08</asp:ListItem>
                                <asp:ListItem Value="9">09</asp:ListItem>
                                <asp:ListItem>10</asp:ListItem>
                                <asp:ListItem>11</asp:ListItem>
                                <asp:ListItem>12</asp:ListItem>
                            </asp:DropDownList>
                            <asp:DropDownList ID="ddlStartDateDay" runat="server">
                                <asp:ListItem Value="1">01</asp:ListItem>
                                <asp:ListItem Value="2">02</asp:ListItem>
                                <asp:ListItem Value="3">03</asp:ListItem>
                                <asp:ListItem Value="4">04</asp:ListItem>
                                <asp:ListItem Value="5">05</asp:ListItem>
                                <asp:ListItem Value="6">06</asp:ListItem>
                                <asp:ListItem Value="7">07</asp:ListItem>
                                <asp:ListItem Value="8">08</asp:ListItem>
                                <asp:ListItem Value="9">09</asp:ListItem>
                                <asp:ListItem>10</asp:ListItem>
                                <asp:ListItem>11</asp:ListItem>
                                <asp:ListItem>12</asp:ListItem>
                                <asp:ListItem>13</asp:ListItem>
                                <asp:ListItem>14</asp:ListItem>
                                <asp:ListItem>15</asp:ListItem>
                                <asp:ListItem>16</asp:ListItem>
                                <asp:ListItem>17</asp:ListItem>
                                <asp:ListItem>18</asp:ListItem>
                                <asp:ListItem>19</asp:ListItem>
                                <asp:ListItem>20</asp:ListItem>
                                <asp:ListItem>21</asp:ListItem>
                                <asp:ListItem>22</asp:ListItem>
                                <asp:ListItem>23</asp:ListItem>
                                <asp:ListItem>24</asp:ListItem>
                                <asp:ListItem>25</asp:ListItem>
                                <asp:ListItem>26</asp:ListItem>
                                <asp:ListItem>27</asp:ListItem>
                                <asp:ListItem>28</asp:ListItem>
                                <asp:ListItem>29</asp:ListItem>
                                <asp:ListItem>30</asp:ListItem>
                                <asp:ListItem>31</asp:ListItem>
                            </asp:DropDownList>
                            <asp:DropDownList ID="ddlStartDateYear" runat="server">
                                <asp:ListItem>2007</asp:ListItem>
                                <asp:ListItem>2008</asp:ListItem>
                                <asp:ListItem>2009</asp:ListItem>
                                <asp:ListItem Selected ="True">2010</asp:ListItem>
                                <asp:ListItem Value="2100">2100</asp:ListItem>
                            </asp:DropDownList>
                        </td>
                        <td width="50">&nbsp;</td>
                        <td>
                            <asp:DropDownList ID="ddlStartDateHour" runat="server">
                                <asp:ListItem Value="1">01</asp:ListItem>
                                <asp:ListItem Value="2">02</asp:ListItem>
                                <asp:ListItem Value="3">03</asp:ListItem>
                                <asp:ListItem Value="4">04</asp:ListItem>
                                <asp:ListItem Value="5">05</asp:ListItem>
                                <asp:ListItem Value="6">06</asp:ListItem>
                                <asp:ListItem Value="7">07</asp:ListItem>
                                <asp:ListItem Value="8">08</asp:ListItem>
                                <asp:ListItem Value="9">09</asp:ListItem>
                                <asp:ListItem>10</asp:ListItem>
                                <asp:ListItem>11</asp:ListItem>
                                <asp:ListItem Selected="True">12</asp:ListItem>
                            </asp:DropDownList> :
                            <asp:DropDownList ID="ddlStartDateMinute" runat="server">
                                <asp:ListItem>00</asp:ListItem>
                                <asp:ListItem>01</asp:ListItem>
                                <asp:ListItem>02</asp:ListItem>
                                <asp:ListItem>03</asp:ListItem>
                                <asp:ListItem>04</asp:ListItem>
                                <asp:ListItem>05</asp:ListItem>
                                <asp:ListItem>06</asp:ListItem>
                                <asp:ListItem>07</asp:ListItem>
                                <asp:ListItem>08</asp:ListItem>
                                <asp:ListItem>09</asp:ListItem>
                                <asp:ListItem>10</asp:ListItem>
                                <asp:ListItem>11</asp:ListItem>
                                <asp:ListItem>12</asp:ListItem>
                                <asp:ListItem>13</asp:ListItem>
                                <asp:ListItem>14</asp:ListItem>
                                <asp:ListItem>15</asp:ListItem>
                                <asp:ListItem>16</asp:ListItem>
                                <asp:ListItem>17</asp:ListItem>
                                <asp:ListItem>18</asp:ListItem>
                                <asp:ListItem>19</asp:ListItem>
                                <asp:ListItem>20</asp:ListItem>
                                <asp:ListItem>21</asp:ListItem>
                                <asp:ListItem>22</asp:ListItem>
                                <asp:ListItem>23</asp:ListItem>
                                <asp:ListItem>24</asp:ListItem>
                                <asp:ListItem>25</asp:ListItem>
                                <asp:ListItem>26</asp:ListItem>
                                <asp:ListItem>27</asp:ListItem>
                                <asp:ListItem>28</asp:ListItem>
                                <asp:ListItem>29</asp:ListItem>
                                <asp:ListItem>30</asp:ListItem>
                                <asp:ListItem>31</asp:ListItem>
                                <asp:ListItem>32</asp:ListItem>
                                <asp:ListItem>33</asp:ListItem>
                                <asp:ListItem>34</asp:ListItem>
                                <asp:ListItem>35</asp:ListItem>
                                <asp:ListItem>36</asp:ListItem>
                                <asp:ListItem>37</asp:ListItem>
                                <asp:ListItem>38</asp:ListItem>
                                <asp:ListItem>39</asp:ListItem>
                                <asp:ListItem>40</asp:ListItem>
                                <asp:ListItem>41</asp:ListItem>
                                <asp:ListItem>42</asp:ListItem>
                                <asp:ListItem>43</asp:ListItem>
                                <asp:ListItem>44</asp:ListItem>
                                <asp:ListItem>45</asp:ListItem>
                                <asp:ListItem>46</asp:ListItem>
                                <asp:ListItem>47</asp:ListItem>
                                <asp:ListItem>48</asp:ListItem>
                                <asp:ListItem>49</asp:ListItem>
                                <asp:ListItem>50</asp:ListItem>
                                <asp:ListItem>51</asp:ListItem>
                                <asp:ListItem>52</asp:ListItem>
                                <asp:ListItem>53</asp:ListItem>
                                <asp:ListItem>54</asp:ListItem>
                                <asp:ListItem>55</asp:ListItem>
                                <asp:ListItem>56</asp:ListItem>
                                <asp:ListItem>57</asp:ListItem>
                                <asp:ListItem>58</asp:ListItem>
                                <asp:ListItem>59</asp:ListItem>
                            </asp:DropDownList>
                            <asp:DropDownList ID="ddlStartDateAMPM" runat="server">
                                <asp:ListItem>AM</asp:ListItem>
                                <asp:ListItem>PM</asp:ListItem>
                            </asp:DropDownList>
                        </td>
                    </tr>
                </table>



    Thursday, March 20, 2008 6:30 PM
  • Hot fix doesn't work either. This is very frustrating. Everytime I delete a control or add a few spaces or type in the designer it goes into this hourglass mode.

     

    Someone please help me out or I am moving back to VS 2005.

     

    Thank you  in advance.

     

    Friday, March 21, 2008 9:44 PM
  • Another 2 cents, working in split mode does seem to help a lot.
    Friday, March 21, 2008 9:55 PM
  • Split mode doesn't solve the issue.

     

    Disabling accessibility checking (from project's properties dialog box) doesn't solve the issue.

     

    Disabling HTML validation doesn't fix it.

     

    Any MS employee listening to us?

     

    If VS hangs for 15-20 seconds between each small code change, how is one supposed to write all that code?

     

    Someone please help. I have a deadline and just can't keep wasting time on this issue.

     

    Any help is appreciated.

     

    Malay

     

    Sunday, March 23, 2008 7:07 PM
  • I think I found the problem.

     

    I had some third-party controls added to the toolbox and reference section.

     

    Gaia and Developer Express

     

    I removed them and my designer/text editor is normal now.

     

    Hopefully, I won't need these controls and problem will not resurface. You never know.

    Monday, March 24, 2008 4:56 AM
  • I have the same problem with performance, in Designer and Source View. When I applied the hotfix, things got better, but the performance is still not good, especially during save in Source View. I have Developer Express controls, and I happen to need them, so removing the toolbox and reference section is out of the question.

    Any solutions if I truly want to use third party controls?

    * UPDATE * It seems that the solution that was given in http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=657867&SiteID=1 also works for the specific issue! After disabling checks for certificate revocation, the save in VS 2008 takes up normal time again...
    Saturday, March 29, 2008 10:57 AM
  • I guess Dev Express needs to improve their integration with VS. You can't even blame MS or Dev Express because you don't really know what's happening behind the scene?

     

    Btw.. that 'update' part, is it relevant to this issue?

     

    Monday, March 31, 2008 5:25 PM
  •  

    Mpellos,thanks!

    It's working normally when I Uncheck  "Check for publisher's certificate revocation" checkbox from my IE Interet Options dialog->Advanced Page。

    It's very cool, my VS2008 become very soon when I change the HTML source view to the Design view!

    Saturday, April 12, 2008 4:40 PM
  • That setting does not change anything on my machine..

     

    Still extremely slow when working with large web applications, but works great when working with wcf, console apps, windows apps etc..

     

    Tuesday, April 15, 2008 7:23 AM
  •  Ian Oxley wrote:
    I have been having this problem since yesterday - curiously since I started playing around with LINQ - but by turning off all accessibility checking in the IDE it seems to have fixed it.  Well, so far, so good anyway

    Hope this helps.

     

    How do you turn off all accessibility checking?

    Thursday, April 17, 2008 7:08 AM
  • Can anyone please write exact steps for 'turning off accessibility checking' please? Where the hell is this setting?

     

    Thursday, April 17, 2008 2:55 PM
  • Nobody who knows where to find the setting ??

     

    Monday, April 21, 2008 9:02 AM
  •  

    Is there another fix for this? When I went from Source view to Design view for a very simple aspx page, it took me, literally, 3 minutes and 54 seconds before VS came back from hanging and eating up the cpu.

     

    Thanks for any help.

     

    -robert

     

     

     

     

     

     

     

     

    Monday, April 21, 2008 3:09 PM
  • Could this be related to the csc.exe? I've noticed that when VS2008 begins to hang and not respond, I see the csc.exe popup, even when I'm not compiling (just switching to Design view, or Source view).

     

    Even the simplist of pages hang for minutes.

     

    Has this been solved? I noticed there was a lot of talk about this and now nothing, so it makes me think that there's a solution but I can't find it. I've tried the hotfix and the other 2 suggestions in this thread.

     

    Please help if you have an answer. I'm really at a loss.

     

    Thanks for any help,

     

    robert

     

    Monday, April 21, 2008 9:40 PM
  • I am wondering if Office 2007 has anything to do with this problem.

     

    Does anyone having the problem use Office 2007?

     

    We have one developer that has no problems using VS2008, but he has Office 2003. Three of us have problems with VS2008 but are using Office 2007. So far, it's the only difference we can find.

     

    Just a thought. Still not working for us even after the two suggestions in this forum and the hot fix.

     

    Sigh.

     

    Wednesday, April 30, 2008 9:43 PM
  •  

    We're experiencing the same problem when saving files, opening files, loading between tab *.aspx page browsing, and simple editing at times.  These hangs truly make no sense to me... I've stripped down my VS '08 version to the bare essential components and still experience the same problem. 

     

    I've monitored Task Manager and see no increase in mem. usage (We're running 3.5G usable RAM out of 4x1G sticks)  Our processors are by no means low quality.  Our entire IT department switched over to VS '08 and experience this problem on pages that don't even reference the new 3.5 Framework objects.  The lag spikes last up to 45 seconds and makes it unbearable to work on pages. 

     

    Like many other dev's here I never use the designer for anything, this is all in the Source view of the files.  Does MS have a solution or are we all doomed to have to go back to VS '05 because Microsoft can't seem to reach a solution for this problem!?

     

    The hotfix did nothing to fix the problem, I disabled all validation checking for HTML... I've cut the IDE down to almost textpad and still have the same problem.

     

    Come on seriously...  The newest and best Development Enviroment out and it's been months of being plagued with these problems and still no proposed solution.  This is not that hard of a thing to reproduce, and should have been fixed by now.

     

    Please advise.

     

    ~Aqua~

    Thursday, May 1, 2008 7:19 PM
  •  

    Aqua, do your developers having the problem have Office 2007? The handful or so of developers with no problems don't have Office 2007. Maybe it's nothing, but it is the only difference between those with VS2008 issues and those without.

     

    We're in a similar or worse boat. We committed to going to 3.5 and there's no going back to 1.1 and 2.0 doesn't have the things we need to move forward. I am very surprised that this made it out of QA.

     

    I uninstalled GrooveMonitor (an Office 2007 thing) with mixed results. It's not the answer. I'm going to try a full uninstall Office 2007 today and see if that helps.

     

     

    Friday, May 2, 2008 1:32 PM
  •  

    The only 2k7 Office product we're using is Visio.  The rest of our office Suite is 2k3....   I tried the hotfix yesterday with no results.  I'm at the end of my rope here and we are getting no help from MS on this one.  I'm going to submit a formal Trouble ticket with them when I get a chance today.  We have some 3.5 components but you can install 3.5 into VS 2005, so that shouldn't stop you from going back to VS 2005.

     

    I'm going to run VS 2008 again today and try to figure it out... but if not I'm going to have to go back to 2k5 and wait for an official fix from Microsoft to fix this.  It's been a problem now for 3 months, and is only getting more annoying ever day.  Too much work to do to be waiting 45 seconds between page transitions and up to 2 to 5 minutes between saves.  Its just rediculous.

     

    Let me know if you make any head way and I'll do the same for you.

     

    ~Aqua~

    Friday, May 2, 2008 2:34 PM
  • Well, that shoots the theory of Office2007 being the problem I guess. I'd read in another place that the VS2008 designer is different than previous versions, that is is an Office 2007 component called Visual Web Developer.

     

    MS said they're working on a fix but don't know when it will be released. I'd heard that it has something to do with the loading of the toolbox.

     

    I spent 2 weeks migrating to 3.5 from 1.1. Changes have been made in the 3.5 code, thinking we're moving forward on it. Now, I have to migrate from 1.1 to 2.0, and figure out the changes from 3.5 and add them to 2.0. Grrrrr. Then, assuming they fix 2008, I'll have to migrate from 2.0 to 3.5. Heavy Sigh. Sorry to vent, but man...

     

    I think I'll try a repair from the discs before I uninstall Office07. I'll keep you updated.

     

    Friday, May 2, 2008 3:00 PM
  •  

    I'm having the same problem in the source view but the design view is even worse. It's so incredibly slow, especially when using FormViews/Multiviews. I found out that hiding the toolbox helps a llittle bit though it's not a real solution. I Hope Microsoft will release a ServicePack soon, the hotfix just didn't help. It's a shame they realased a product full of bugs like they did with Visual Studio 2005. I don't understand why they never remove all bugs BEFORE shipping the product. It sucks so much when you depend on it and have to work with it every day. VS2008 even got some bugs back that had already been fixed in VS 2005. One example: when working in the asp.net design view and clicking on a control, occasionally the property windows just doesn't update. You have to switch to source view and back to design view and try again. The same thing happened in the first release of VS 2005 but got fixed later. An the same bug exists again!!

     

    VS 2008 has the potential to be a great product but all these bugs make me hate it. Thank you, Microsoft!

    Friday, May 23, 2008 9:03 AM
  •  

    SP1 of VS.net 2008 mostly fixes this, although it has an anoying habit when you open a file to rebuild the javascript intellisense thus hanging the editor until it's done (which takes minutes on my Core2Quad 3.0ghz processor with 8 gigs of ram and a 10,000 RPM hard drive!)

     

    It seems to do this EVERY. SINGLE. TIME. YOU. OPEN. A. FILE.  Very anoying.

    Friday, May 23, 2008 12:58 PM
  • This is a bug and there's hotfix for this:
    https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=10826

    However, after applying hotfix, it is still the same. The CPU load is pike to 50% and computer freeze for about 5-10 seconds, every time I change a single line. It is VERY.ANNOYING !

    When can we have SP1 VS2008 release and fix these performance bugs ?
    Thursday, June 19, 2008 6:12 AM
  • Got tired of reading through this forum checking to see if I could find the portion that I know fixes this.

    Destroy your sln and suo file from the Projects Project folder.  This solved the intellisense lag for me..Matter of fact, got real peppy after that.

    Peace be with you all!

    Pat
    Thursday, June 19, 2008 2:36 PM
  •  I think MS finally fixed the problem!  I just now downloaded and installed Microsoft Visual Studio 2008 Service Pack 1 Beta without making any other changes suggested above in the numerous posts.  I'm happy to report that the extreme slowness during saves and switching between Source and Design views went away!  In fact, saves of my very large ascx & aspx files happen almost instantly.  Same with switching between Source & Design modes. 
    Wednesday, July 16, 2008 4:14 PM
  • PnJSinc, What folder precisely did you mean?
    • Edited by CezaryK Saturday, August 9, 2008 6:28 PM A reason
    Saturday, August 9, 2008 6:27 PM
  • Installed/reinstalled vs web designer components stuff
    Installed hotfix
    Installed the new SP1 (not beta).
    Cleared error checking settings in vs.
    Cleared certificate check in IE.


    All still don't change anything for me.

    When I open a webpage in my project I get the source code and that works fine (enough).
    But at the moment I click design or split view the whole view area just freezes.
    In worst case VS crashes and I can start all over.

    It's not an office 2007 thing, because I still have Office 2003 pro installed.

    I hoped sp1 would finally fix the problem.. but stil!!!
    Thursday, August 14, 2008 3:15 PM
  • I'm having the same Design View Freezes issue when switching from Source to Design mode.  Vista Ultimate SP1 x64 / Office 2007 / Visual Web Developer 2008 SP1 (and SP1 Beta had same problem)
    Saturday, August 16, 2008 5:54 AM
  • I was having the same same problem.   I unchecked DevExpress tools from the Add-In Manager and that solved it.  It seems that there are some issues with the DevExpress tools integration into VS2008.
    • Proposed as answer by Yardy1 Thursday, September 4, 2008 8:38 PM
    • Edited by Yardy1 Thursday, September 4, 2008 8:46 PM Solution
    Thursday, September 4, 2008 11:20 AM
  • I have been having most of the same problems described previously. I don't use design view, but opening, editing, saving, closing aspx or ascx files randomly takes full minutes. At this point, about 50% of my editing efforts result in 30 to 60 seconds waits.


    I have had an open MSDN tech support incident for two full weeks now, with no clues or progress, or acknowlegment of a known problem.

    I applied SP1, and there was no change.

    It sounds like a few people were helped by the various hotfixes and the SP, but definitely not everyone.

    My very small business is basically shutdown until a solution is found.

    Are others still having this problem? Is there any news or hope of help?

    Monday, September 15, 2008 2:43 AM
  • Whenever I'm using the Asp.NET Designer (with pages more complicated than a few labels) it gets incredibly slow when I change properties. If I change a value the IDE locks up, sometimes for minutes, the CPU goes up to 50% (I'm running on a dual core) and VS2008's memory consumption goes up by 50-75Mb (per property change). Eventually VS2008 crashes, on my last test when it reached about 1Gb of memory used.

    I have installed the service pack but sadly it didn't improve much. I'm running on XP SP3, Dual core 2.66GHz, 2 Gb RAM.

    This is incredibly irritating and reduces productivity. Any solutions?

    Microsoft Visual Studio 2008  
    Version 9.0.30729.1 SP  
    Microsoft .NET Framework  
    Version 3.5 SP1  
     
    Installed Edition: Standard  
     
    Microsoft Visual Basic 2008   91851-136-0251463-60735  
    Microsoft Visual Basic 2008  
     
    Microsoft Visual C# 2008   91851-136-0251463-60735  
    Microsoft Visual C# 2008  
     
    Microsoft Visual C++ 2008   91851-136-0251463-60735  
    Microsoft Visual C++ 2008  
     
    Microsoft Visual Web Developer 2008   91851-136-0251463-60735  
    Microsoft Visual Web Developer 2008  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB944899)   KB944899  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/944899.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB945282)   KB945282  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/945282.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB946040)   KB946040  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/946040.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB946308)   KB946308  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/946308.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB946344)   KB946344  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/946344.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB946581)   KB946581  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/946581.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB947173)   KB947173  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/947173.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB947540)   KB947540  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/947540.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB947789)   KB947789  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/947789.  
     
    Hotfix for Microsoft Visual Studio 2008 Standard Edition - ENU (KB948127)   KB948127  
    This hotfix is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/948127.  
     
    Microsoft Visual Studio 2008 Standard Edition - ENU Service Pack 1 (KB945140)   KB945140  
    This service pack is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this service pack will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/945140.  
     
    Microsoft Visual Studio 2008 Standard Edition - ENU Service Pack 1 (KB947888)   KB947888  
    This service pack is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this service pack will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/947888.  
     
    Microsoft Visual Studio 2008 Standard Edition - ENU Service Pack 1 (KB948484)   KB948484  
    This service pack is for Microsoft Visual Studio 2008 Standard Edition - ENU.  
    If you later install a more recent service pack, this service pack will be uninstalled automatically.  
    For more information, visit http://support.microsoft.com/kb/948484. 

    f

    • Proposed as answer by tbean Tuesday, February 10, 2009 4:58 PM
    Monday, September 15, 2008 7:53 AM
  •  

    Remove any attached master page to your current web form that you are working on. Make a vanilla master page and reference it to the web form you are working on. This helped my development time and stopped the lag between design and source views in VS2008.

    Tuesday, February 10, 2009 5:03 PM
  • This reinstall of the webdesignercore fixed it for me.  Now I can get back to work.  Thanks!
    Thursday, September 2, 2010 9:54 AM