The official source of product insight from the Visual Studio Engineering Team
As Soma announced on his blog this morning, Visual Studio 2010 and .NET Framework 4 have just launched! The Visual Studio team has been working on this release for more than two years and we’re extremely proud to announce the availability of the final RTM build!
MSDN Subscribers can download Visual Studio 2010 later today from MSDN, and non-MSDN subscribers can go here to get a copy of Visual Studio 2010. For those that want to take a test-drive, a 90-day trial version of all Visual Studio 2010 products can be downloaded here. Also, for the hobbyist developer, the free Visual Studio 2010 Express products are now available as well.
As always, we’re excited to hear your thoughts on this release. Please make sure to send your feedback via Connect or post comments to this blog.
Download and enjoy!
I have been using Visual Studio since it was invented for Visual C++ 1.0. The version that shipped way back in the late 1980's with a T-Shirt bearing the Visual C++ logo.
The MDI interface is what made the visual studio experience infinitely better to code, than any other editor of the day, and to the present. The tab-style is worthless. Once a person opens upon about 3 files with long names, the Tabs not only are worthless, but hinder/clutter the display and consume veritcal display space which one has nothing they can do about. But at least VS-2008 and previos when the tab-style was introduced, let one go to MDI. When dealing with many files opened at a time, the MDI style works best. It puts the current file into the title bar, by default, consume no vertical space (where the tab bar would otherwise be), and using the Window-Windows (which I always made a short cut to of Ctrl-Q from the original default of VS), I got the list of windows in a popup dialog, which showed me the full list.
Please put the MDI back ASAP. It is really going to cost valuable development time to deal with. I may very well have to keep VS-2008 around, just to have the MDI.
I would reccommend who ever didn't think of putting the MDI in, be fired also.
TOTALLY agree with the poster above named, " Put the MDI back in ASAP. ". (Great name, BTW.)
Long file names, and the tabs are worthless. Lots of files open, and the tabs are worthless. And, I don't appreciate those worthless things taking up pixels on my 30" display -- I use my display for "real" stuff, like code.
I use DevStudio because the MDI permitted me to quickly navigate among many files, each with different space needs. It was superior to twenty console windows running a text editor, sized and placed where I needed them. Without MDI, I'm going back to my consoles (seriously). I need each file to have its own "remembered" placement and sizing constraints, because they have different styles of code, and I don't have time (nor interest) in continually fiddling with pixel placement every time I re-open a file.
I commonly work on 6-12 files at a time, and it is not abnormal for me to have 30+ files open at a time, each with "remembered" placement and size constraints. The idea that "all files must hide everything else in the stack, and all files have the same display requirements" is incredibly stupid to people that actually have to write code on non-trivial projects.
I'd like to point out that the documentation for VS2010 still implies that MDI windows are available:
I too am sorry to see them missing. I used them extensively, and for reasons that have been previously mentioned: they allowed me to switch between C source files by "physical place on the screen."
It's true that we MDI fans should have caught this earlier in the Beta process. But I should remind you that Visual Studio 2010 Beta 1 completely failed to support building C/C++ programs, so that was an instant roadblock for us C programmers. Let me make this helpful suggestion in the future: do not let Betas go out with vital features broken, because it's impossible for users to give any feedback at all. We have to wait for the next release cycle, wasting time that could have been spent tracking down trickier issues for you.
Just like everyone else here, I want to lament the lack of MDI. I see some people at work, working the way Ryan describes, that is, having only one source window open, and switching back-and-forth. Maybe Microsoft needs to hire a psychologist. He/She would tell them, that some people can hold things like code in short-term memory, like Ryan I guess, or some of my colleagues at work, and some don't. I can't - I am still a capable programmer, but I have to have multiple windows side by side, rearranged the way I want, because once I close one, I don't remember what was that line of code that I saw there. That is the way my brain works, and I wrote lots of good code in my life. That is why I can't see moving to Visual Studio 2010 and am staying with 2008.
I would like to add my vote for the return of a native float window default, but with the ability to set a default size for new floating windows. When I drag off the tab, the window size defaults to the size of the working area, which for me, makes the window too big for my taste, and thus requires the extra step of a manual resize.
I program in VC++ and enjoy the ability of having multiple documents open simultaneously so I can make use of information from various headers.
I have a three side-by-side-by-side monitor configuration. Up until this moment, I would have VS2010 opened to cover two monitors. The third monitor is the application testing area.
When opening a new document, it is auto-tabbed. I can drag it off the tab, but it defaults to being two monitors wide and as tall as one monitor (the size of the VS2010 workarea). So then I have to resize it. This is the painful part when trying to get a bunch of windows going.
Instead of dragging off a tab, I have in the past done Window->Float. This defaults to a smaller window which I can then drag. Right click on the tab and choose float does the same thing. Each way seems to require too many clicks after a while.
What I have now done is resize the VS2010 work area to the size of the default window I want. I can then open the document and drag it to where I want it at close to my final desired size.
The downside to this is that my tool bars aren't exactly where I want them. If I could float, and 'keep on top' the tool bars, I think that would solve this problem. The other drawback is that I had VS2010 across two monitors to hide all the other stuff I have open. Well, ok, this I can live with.
@Anonymous: Dragging a window tab is the same as Window/Float. In the past you could not have used this to float documents - floating documents are a feature introduced in VS2010. Nothing was removed in what you refer to "native float window default". I suspect you're thinking about floating toolwindows - toolwindows have a default floating size that can be statically specified when the toolwindow is declared (in registry), and they still use this in VS2010.
Floating documents don't have this feature - they use by default the same size the document had when it was tabbed in the document well area.
It should not be hard to add in VS11 a differenly-specified default size for floating toolwindows (e.g. via new Tools/Options values) - please open a suggestion bug on connect.microsoft.com/VisualStudio so other user can vote on its importance.
@Ryan: You keep saying there was no feedback about MDI in the beta. The first result I get when searching for "Visual Studio 2010 MDI" is a lngthy discussion on "where the hell is my MDI" from the Beta 1 release.
what are the limitations of using " evaluation purpose only" visual studio 2010 premium edition, does it limit me from using VS 2010 nomally. plz rply