Letters from Readers
Looking to .NET 4 and Visual Studio 2010
Readers sound off on the next generation of these key development technologies.
In April we explored Visual Studio 2010, and in June we took an in-depth look at .NET Framework 4. Here's what readers had to say about our coverage of the next generation of these strategic dev technologies.
I'm curious about how the developers of .NET Framework manage to keep from reintroducing historical bugs or problematic features from past versions, when I'm certain that the development teams have changed over the years.
Allan (via the Web)
Bronx, New York
I love all the candy that should be coming with Visual Studio 2010, but what I'd like to know is if I'll still be stuck using Visual Studio 2005 and Visual Studio 2008 to build and maintain SQL 2005 (or SQL 2008) reports and SSIS [SQL Server Integration Services] projects. I was very upset to find out that Visual Studio 2008 doesn't allow me to maintain SQL 2005 reports and SSIS projects.
An Office user doesn't need an older version of Word to open and maintain an older-version document, and this shouldn't happen for developers either!
I'm curious to know: Has Microsoft implemented multiple controls selection in WebForm (to set common properties, moving, resizing, etc.)? The company dropped this feature in Visual Studio 2008 with the lame excuse that it's created from scratch on FrontPage Designer.
Shame on you, team of 1,000 people with unlimited resources, for giving this excuse. I've never worked in Dreamweaver, but after missing this basic feature in Visual Studio 2008 Designer, I feel that not having a grip on Dreamweaver is hurting me-simply because Visual Studio 2008 is poorly designed.
Adil (via the Web)
Visual Studio Magazine wants to hear from you! Send us your thoughts about recent stories, technology updates or whatever's on your mind. E-mail us at firstname.lastname@example.org and be sure to include your first and last name, city and state. Please note that letters may be edited for form, fit and style. They express the views of the individual authors, and do not necessarily reflect the views of the VSM editors or 1105 Media Inc.
This story was written or compiled based on feedback from the readers of Visual Studio Magazine.