MSDN Magazine February 2002
View Complete Post
The man most responsible for Visual Studio 2010 discusses what developers have to look forward to.
MSDN Magazine April 2010
Ruminations on ten years of Visual Studio.
MSDN Magazine June 2007
2005 was a truly exciting year for us here at MSDN Magazine. We launched a new magazine. We covered all sorts of amazing advances for the programmer, courtesy of Visual Studio 2005. We lost a couple of weeks, because of that dodgy falafel cart on 49th Street.
MSDN Magazine Visual Studio 2005 Guided Tour 2006
MSDN Magazine May 2002
Although it's been several months since the slammer virus hit SQL Server installations, we'd like to offer a public service announcement for anyone who hasn't patched their machine yet. PATCH YOUR MACHINE NOW! We found out the hard way that it can hit any machine that runs SQL Server and is attached to the network.
MSDN Magazine April 2003
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?
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?