View Complete Post
Visual Studio 2010 includes new resource contention profiling features that help detect concurrency contention among threads. We walk through a profiling investigation to demonstrate how you can pinpoint and fix resource contention problems in your code.
MSDN Magazine June 2010
The man most responsible for Visual Studio 2010 discusses what developers have to look forward to.
MSDN Magazine April 2010
Understanding performance bottlenecks in multithreaded apps used to require significant instrumentation and analysis by expert developers. The Concurrency Visualizer in Visual Studio 2010 significantly reduces the burden of parallel performance analysis.
MSDN Magazine March 2010
I am having a weird problem with VS 2010. I am using the premium edition.
It seems that none of the asp controls <asp:..> tag are recognized by the editor. I keep getting a green underline under each control name. To check this, I have created a brand new web site targeting .NET framework 4.0 and even in the auto-generated pages, none of the asp controls is recognized. I am also unable to see the properties of any control if I click inside the tag (at an attribute). All I get is the ID of the button and the tag <HTML ELEMENT>! Furthermore, when I drop an ASP control from the toolbox, the attribute "ID" is not generated. Only when I switch to the design view that I can get to see the properties of the control and the ID is set automatically. The message for the green underline says: Element 'Button' is not a known element. This can occur if there is a compilation error in the Web Site, or the web.config file is missing.
Does anyone know what is going on?
IMPORTANT NOTE: the Beta and Release Candidate builds of Visual Studio 2010 are now obsolete, since Visual Studio 2010 has now released to manufacturing.
NOTE: The Release Candidate and RTM builds of Visual Studio 2010 does not need this configuration change
This post is to let you know about a configuration change (registry switch) which you can use to improve the startup performance of the WPF and Silverlight Designer in Visual Studio 2010 Beta 2.
1. Since this was a late-breaking change, you may experience some instability or increased Virtual Memory usage in some Visual Studio scenarios when using it. If you see such instabilities, please try removing the configuration change, and let us
know about the problem you saw (you can do this by replying to this posting or by raising a bug on Connect).
2. You should only make this configuration change if you are a regular user of the WPF and Silverlight Designer, and are experiencing poor performance with it.
3. This configu
I am using Visual Studio 2010. I was debugging a web application and an exception happened and VS 2010 froze. I ended the VS 2010 in the task manager and when I went back to developing, I found on every form for every ASP.net control I get:
Error Creating Control -
Error HRESULT E_FAIL has been returned from a call to a COM component.
Also I am unable to edit the form or add anything from the toolbox.
Any help on this matter will be appreciated.
I added a visual web part item to my solution. I'm looking to drag some controls on to the design surface from the toolbox but they're not there. For example, linqdatasource control and datapager control. I tried to create them in
the markup up but all I get is 'cannot render control' or 'unknown server tag.'
At the top of my .ascx file I have:
<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %>
<%@ Assembly Name="Microsoft.Web.CommandUI, Version=220.127.116.11, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="SharePoi
After I imported a VS 2008 web project to VS 2010, I can't view aspx pages that have master pages in design mode. The page design mode displays "error creating control - contentplacehoder1 object reference not set to an instance of an object." The project builds and runs fine though. I have only one master page that all other aspx pages reference and I don't have any nested master pages. Can anybody help me with this? Thanks in advance.
when I work with the Visual Studio 2010 Ultimate Edition WPF XAML editor Visual Studio constantly freezes for more than one minute.
Impossible to work with this. This affect only occurs when the WPF editor is opened. The problem starts as soon as I start to edit the XAML code in the text editor.
What can I do?
I was unhappy with VS 2010 performance on my machine:
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
System Type X86-based PC
Processor x86 Family 6 Model 37 Stepping 5 GenuineIntel ~2393 Mhz
Total Physical Memory 4,096.00 MB
Graphics: Intel HD graphics, internal 128mb
Basically the UI kept hanging when closing tabs on the workspace or under general
navigation of UI.
I eventually found this fix:
which suggested turning off hardware rendering and it worked a treat.
General UI responsiveness was massively improved.
I see that this was recognised and VS comes with SW rendering as standard now for SP1 on XP.
However the upgrade to SP1 seems to have brought this problem back even though hardware rendering is disabled!
Has anyone else noticed this behaviour?
Is there any suggestions?
Here is my info from VS:
is it possible to convert whole visual studio 2008 web site project to visual studio 2010 web site project
my current project references
i have a very annoying iis problem
iis server stops working until app pool is recycled
i am hoping that new visual studio (net framework 4.0) may solve this very annoying unsolveable problem