Your official information source from the .NET Web Development and Tools group at Microsoft.
Some customers discovered that sometimes switch to Design view was very slow. We analyzed submitted reports and tracked the issue down to a code that was discovering available AJAX Extenders and which contols they were applicable to. In order to avoid unnecessary delays we moved discovery of AJAX extenders to a background thread. This made switch to Design view significantly faster since designer is now available immediately while extenders are still being enumerated. Here is a screenshot, look at the status bar that shows "Discovering AJAX extender controls..." and displays a small progress indicator:
If you select a control before applicable extenders are discovered, the control will not display its smart task menu and/or will not have "Add Extender..." menu item.
Unfortunately, if control is selected, due to architectural limitations we cannot update its smart task availability. Therefore you may have to unselect and reselect the control in order to let it update its smart task menu.
PingBack from http://www.basketballs-sports.info/basketball-chat/?p=1707
Second picture shows 'Ready' in status bar. Slight ambiguity.
It correct, second picture shows what happens when control was selected while discovery process was running, hence no smart tasks menu.
My Design View tab freezes when I switch do DV.
Will SP1 solve this??
I recorded a movie of my problem:
This blog states SP1 is RTM now and all MSDN downloads list the SP as Beta? Can someone clarify this please?
The improvements mentioned in this blog are in SP1 RTM, which is not publicly available yet, but will be out in the very near future. Hope this clarifies.
Omar Khan | Visual Web Developer
Visual Studio 2008 SP1 and Visual Web Developer 2008 SP1 are now available for download . This blog post
We just announced the release of Service Pack 1 for VS 2008 and .NET FX 3.5 . A major push for this release
I just installed the SP1 for VS2008 and .NET 3.5 and now my VS freezes when I try to switch a page to "Design View" from "Source View". This happens for even a new project with a new aspx page that doesn't have any thing in it.
I have installed Visual Studio 2008 Pro + SP1 + .Net3.5 SP1 using VB layout as default.
Opening a brand new web application project and switching to Design view freezes the whole package immediately - no dump, no errors, no event log entries - nothing. The only way I can get out of the freeze is to kill the devenv.exe process which interestingly is only running at 2 - 3% utilisation rather than the more common 100% utilisation during a freeze.
This is insane. SP1 was said to address these issues but the problems I am having got worse. I can hardly get anything done. Switching back and forth is extremely slow. Another issue is when I make a change in source view and save, it takes forever as well.
I'm sorry to hear that you are running into the problem described. In our general testing we did not find problems with switch to design view. We would like to investigate the issue you are having, and hopefully resolve it for you.
Please send email to vwdperf-at-microsoft-dot-com, and we should be able to help. Thanks again for bringing this problem to our attention.
James D: can you obtain a debug dup from the frozen VS? In you are on Vista, go to Processes tab in the Task Manager, right click on devenv.exe and select Create Dump. Please zip it and e-mail to mikhaila-at-microsoft-dot-com. Thanks.
Today, I installed the SP1 for VS 2008. And now my designer won’t event load the page. Now switching to designer mode from html won't work.
Follwoing are my environment settings:
VS 2008 + SP1
SQL Server 2005
Thanks Mikhail, from micosoft, for solving the issue
To solve the switching problem in designer follow these steps.
1) uninstall Microsoft Visual Studio Web Authoring Component.
2) reinstall the Microsoft Visual Studio Web Authoring Component from DVD (look into WCU folder where you can find WebDesignerCore.exe).
I has the same issue, but after reinstalling the Microsoft Visual Studio Web Authoring Component solved my problem.