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!
Yeah, we know a lot of people are just starting to use it, though we had over a million downloads of Beta2 so I think a good number of people have already used it (some rather extensively). Whether they realized certain things were missing or not is unknowable unless they filed bugs/contacted us in some way. We certainly do want feedback, and from this posting I can see there are a non-zero number of people that would like MDI mode back :) I can't promise that means MDI mode will come back, but we certainly have heard the request here (as I said it also helps your cause if you file Connect bugs or find existing ones and UpVote them).
The color issue sounds odd. By default these are controlled by settings in Fonts and Colors, and those settings may be language specific (I am not sure). The link I gave was for re-coloring the shell itself, not anything to do with the editor coloring (which is seperate and much more complex as it also involves language services). In 2008 numerics in my editor (in C#) are black. Did you change this in 2008 via Fonts and Colors? If so you can Export from 2008 and Import into 2010 and your settings should be honored. If not what language are you using? I can check if the language themselves decided to change the coloring of numbers to be black. In the mean time you can open Tools->Options and go to the Fonts and Colors page, the top combo should say Editor in it and then in the listbox below you want to find an entry called 'Number'. Once you do and have selected it you can change the foreground and background via the dialog and save it and it will be applied, for instance I just changed all numbers in my code to be displayed in red.
I am missing the MDI possibility, too. Trying to use floating windows, but if I open another window (e.g. with Go To Definition command), it opens tabbed, totally obscured by my floating windows - oops :-)
I’m sorry about my question about colours. Everything is fine. I just assumed, that converting of existing project would do it for me automatically. Though I have another question. In previous VS versions I was customizing menu items on a main top toolbar – I could go Tools->Customize and Customize dialog would pop-up. What’s important this dialog was modeless , so it allowed me to select controls, drag and drop the selection on this main top menu/toolbar, move them around, resize… Now this Customize dialog is modal. And I cannot figure how to modify this top menu/toolbar… I can do something with this menu items/command within this Customize dialog, but I cannot figure how to reflect this changes to the main top menu/toolbar..
Hey an actual question about my area :) Okay, yes the dialog is no longer quasi-modal as it was in 2008. That dialog in 2008 was implemented by MSO (office toolbar code written in very low-level, hand crafted Win32 code that was not usable with WPF in any way) that we borrowed from Office in ye olden days. To get that quasi-modal behavior required rather tight coupling between the main message loop in VS and that dialog in order to be kinda-sorta-modal. We didn't replicate that in 2010, and I highly doubt we will in Dev 11. That said we have had complaints about the lack of 'quick drag customize' and a number of other issues about the existing customization dialog, so I personally would love to do quite a number of things there in Dev11 if the powers that be let me :) As with MDI mode the takebacks here were due to lack of manpower (or my own incompetence/inability you could argue :)). As for your specific question:
You want to open Tools->Customize, go to the Commands tab and select the radio button that says Menu bar. The listbox will show all top level menu items (not just the visible ones like in 2008, another thing we have gotten feedback about :)). If you move/add/delete commands or menus here it will affect the top level menu. If you want to modify say the File menu then you want to drop the Combo next to the Menubar radio button and choose "File". If that isn't working or isn't clear let me know what specific modifications you are trying to make and I can probably point you in the right direction. Also you should be able to import modifications from 2008 into 2010 so if you have done lots of modification in 2008 you shouldn't need to redo it in 2010, just Export Settings on the General -> Menu and Command Bar Customizations in 2008 and then Import Settings on that .vssettings file in 2010.
Thank you Ryan for the great answers. I’m feeling better already about VS 2010, but please, let the people get comfortable with VS10, stop talking about VS11, at least just for now :).
Regarding customization of a top menu – it’s been so smart done, I mean default layout that I even didn’t realized, that I haven’t imported my favorite settings from my previous VS. Just a several my own macros were missing. But after I added my macros project and imported settings from VS 2005 everything is there. And this Import Settings function became smarter :). Before my macros were not imported automatically, I still had to drag and drop them ( or may be I’m wrong and they were), but what I know for sure, that images, which I assigned to this macros were not imported, a had to assign images I want manually. Now everything was imported OK, including macros images. Thanks for the great work… but slow down a little bit with VS 11, please :).
Glad you got it all working, sorry about the Dev11 talk, I am already thinking about all the things I want to fix / implement :)
The MDI source window feature is a make/break one for me.
I have been using the IDE since it was a just a compiler and editor. It has grown to contain tremendous functionality and everyone is to be congratulated for the effort.
However, i don't think this product or for that fact many MS product take visual context into account for the UI design.
In particular, i work in edit and debug mode with dozens of windows open and spacially laid out such that i can click from window to window visually and not textually. (btw, it would be nice to single click on a title bar w/o having it think it was a double click!)
All my aux windows are on the second monitor (output, solution explorer, breakpoints, etc) except for Autos, Locals, and a stack which are in the main monitor.
There is a huge difference between float and MDI: the MDI source windows are Below the bottom local/stack windows, not above as for float. This is huge because i now have to restrict my source window heights that let the locals/stack windows show through.
Additionally the previously mentioned problems are insurmountable if you like the MDI style. Every file you open is a tabbed doc, assuming you can see it.
This was a huge mistake imho and it neglected input from those who used spacial position and an almost-muscle memory to know where certain source windows are.
PLease please bring MDI back or at least provide some work around that walks and talks just like MDI.
This looks like a better release. Although non-Cleartype text aliasing somewhat differs from the "Standard" XP aliasing, I've worked around it by switching from Segoe UI Light to MS Sans Serif and also Tahoma as the environment font. Also replaces Consoleas with Courier New. Congrats to everyone in the WPF team for their work!
The MDI is gone. Not surprising as Microsoft seems to decide what we want in a UI not the other way around. I can't wait for the next release when they remove toolbars and menus in favor of ribbons. Then we can all forget about upgrading. I myself have been using this product since 1992 and this release will not be one I use again.
I cannot understand what happened, but when I started VS 2010 this morning Solution Explorer appeared at the right side of IDE. When I closed VS 2010 last time, it definitely was at the left side (where I want it to sit). Now I cannot dock it to my left. If I choose Dock option - Solution Explorer jumps to the right. If I drag it to the left – it “un-docks”. Double clicking doesn’t help…. I didn’t have problem with this in any previous VS.
So, please, what should I do to “dock” solution explorer at the left side of VS 2010 IDE. And preferably Output Window must be docked at the bottom and take the whole width of IDE, so Solution Explorer will be sitting on top of the Output Window. Sorry, but I used to this layout and feel uncomfortable with anything else. Or Microsoft didn't have enough resources to support this feature also :)
@rurulan: The Dock option in context menu on the toolwindow toolbar docks the window in the last place where it was docked, thus in the right side.
Have you tried dragging and dropping the toolwindow on one of the drop targets? When you begin dragging there should appear some guide drop targets floating on top of the IDE. For reference see pictures here:
Or are you saying you don't get the drop targets?
Make sure you don't have Control key pressed when you drag the window, that hides the drop guide targets.
You can also dock the window in the left side by importing a window profile that has it docked there. E.g. Tools/ImportsAndExportsSettings/Import, choose the VC++ profile and from the settings to import choose General/Window Layout.
[Visual Studio Shell Development]
Hello Alin Constantin
Thanks for the answer, but please, read my question. I’m not talking about the toolwindow. I have a problem with the “Solution Explorer” window. The link you’ve provided I’d seen already, but it also tells what to do with the toolwindow. Unfortunatelly in my case with the “Solution Explorer” window when I’m dragging it to this dimond only top area of the pane gets shaded. And indeed, Solution Explorer window could be docked to the top part of the pain. But I need to dock it to the left part of the pain.
So MDI option was removed in VS 2010 and option to dock “Solution Explorer” (as well as Class View and Resource View) was removed as well? Or the importing settings from previous VS versions is the only way to do so?
@rurulan: I think you are confused of what toolwindows are in Visual Studio... "Solution Explorer", as well as "Class View", "Resource View" are all toolwindows (as opposed to document windows like the editors that open when you open say a text file that can only be displayed tabbed in the document well/area).
No, nothing has been removed from the options of docking toolwindows. There should be docking guide drop targets in all parts of the IDE, not just on top. Select the drop target in the left.
If you still can't figure out how to dock the toolwindow in the left side and suspect there is a bug with the way VS displays the drop targets, please open a bug on Connect site (http://connect.microsoft.com/VisualStudio) and attach screenshots (e.g. press PrtScr during the drag operation to capture a screenshot, then paste in your favorite image editing program), or better, a video capture demonstrating the problem (you can use Community Clips Recorder from http://www.officelabs.com/projects/communityclips/Pages/Default.aspx )
P.S. FWIW, I was not talking about the importing settings from previous versions, I was talking about importing settings from the default VS2010 profiles.
I too was shocked when I first realized that the MDI interface was removed from the product. I'm trying to adjust by making all the document windows float. But it's rather annoying that when you open a document by double-clicking on the Solution Explorer, VS doesn't remember the "float condition" from the previous time the document is open and simply defaults to being docked. Being able to "tear the tab off" to make a window float again *somewhat* alleviates the annoyance, but not by much.
One other thing that would make living with this new UI much more bearable would be to allow the main VS window to display on top of the floating document windows. Right now the document windows always appear on top with respect to the main VS window.
Yet another developer who relies on MDI for editing amongst 6+ files at a time, knowing by memory where a particular one's edge/corner is on the screen. I can navigate among them faster that way. New looks are "cool", but power users rely on consistency and stability to maintain productivity too.
Perhaps an option to have them open floating as the default would suffice...