Introducing the New Developer Experience, Part #2

UPDATE: We hear you. There’s a lot of excitement about this release and a lot of passion about colors, designs, styles and icons. Know that we are listening to all your comments here, across social media and we are working hard to make Visual Studio 11 a fast, powerful and feature-rich product. Keep the comments coming, both good and bad. We are reading them all.

Simplification: Streamlining common workflows

As we described in our previous blog post, in Visual Studio 11 we’ve focused on helping you spend more time focusing on your code through thoughtful reduction in UI complexity and by introducing search throughout the product. In this blog post we’re going to round out the story of how we’ve allowed you to spend more time adding value to your applications by describing how we’ve simplified common workflows.

Hubs

As we worked on ways to ensure developers can spend more time focusing on their code, we quickly identified the need for an improved approach to navigating code and related artifacts. Today’s IDEs surface code and artifact relationships through an array of largely independent tool windows. Within these environments developers end up having to re-establish context across multiple tool windows throughout their workday. The obligation to re-establish context across tool windows is a major source of workflow interruption and reduced developer productivity.

Switching costs are particularly pronounced for tool windows that operate over the same data. In such cases the developer not only has to spend time navigating and managing multiple tool windows, they also have to spend time ensuring that the context of each tool window is kept in sync. For example, Visual Studio 2010’s Solution Explorer and Class View both present different views and relationships over the same data (i.e., the code inside a VS solution), yet when the developer switches from one window to another, there is no easy way to keep the two in sync. If the developer is looking at the contents of a project in the Solution Explorer, the corresponding set of classes are not shown when the developer switches to the Class View.

In VS 11, we have created a relationship navigation model that places less focus on the tools, and more focus on the content that the tools provide access to. We have used this model to create new versions of both the Solution and Team Explorer. We call these new explorers, ‘hubs’.

With the Solution Explorer hub, core functionality and information from the Solution Explorer, Class View, Object Browser, Call Hierarchy, Navigate To, and Find References tool windows are now integrated into the one explorer. Thus developers can browse deep within the contents of a file without needing to switch between different tool windows. It’s worth noting that even though the information from these tool windows has been integrated into the Solution Explorer, each of the tool windows still exist. We don’t want to disrupt developers when they start using VS 11 by making them wonder where the tool windows they are used to have gone. When they start to interact with the new Solution Explorer they will become aware of the new functionality offered and will be able to adapt to the new Hub model.

Likewise, the Team Explorer has been similarly enhanced to combine views from multiple tool windows. The Team Explorer now houses multiple tool windows into ‘pages’ and provides a browser based navigation model between each page. With the new Team Explorer developers can find bugs, find pending changes, and view the differences between different versions of files all from the same tool window.

The new Solution Explorer hub in VS 11. In this example the developer has expanded the contents of the LinePaint.cs file and is browsing the class defined in the file.

Pivots

As noted above the new Solution Explorer hub integrates content and relationships from the Solution Explorer, Class View, Object Browser, Call Hierarchy, Navigate To, and Find References into a single tool (for more information on the new Solution Explorer, take a look at this blog post). Developers can easily switch the relationship or pivot that they wish to browse without needing to switch to another tool window.

The current list of relationships that are exposed as pivots within the Solution Explorer Hub is:

Contains

Base types

Derived types

Is used by

Calls

Is called by

The Solution Explorer Hub is designed to be extensible by third parties, allowing them to integrate new languages into Solution Explorer with support for browsing file contents (i.e., the ‘Contains’ relationship).

This powerful unification of relationships and views within a single browse-able information space allows the developer to browse the logical contents of a file, for example to find the class that is defined in the file. Then the developer can seamlessly follow relationships from that class such as ‘All derived types’ and ‘Base type’ which would previously only have been available from the Class View tool window in Visual Studio 2010.

By gaining access to multiple relationships from the one hub the developer doesn’t have to think about the tool window they need to use in order to browse the relationships of interest. Instead, they just access those relationships directly from the content inside the Solution and Team Explorer hubs.

Multi instancing

In VS 11 we allow developers to create multiple instances of the Solution Explorer, with each instance capable of displaying its own unique view on their content. When developers use the Solution Explorer to browse through their code, they can make permanent any view that they consider valuable by creating another instance of Solution Explorer. The newly created instance is a duplicate of the original (i.e., the content and view is the same), allowing the developer to continue browsing in the original instance of the Solution Explorer without worrying about losing the valuable information that they browsed to. This allows them to browse through the code, find something of interest, keep it around, and continue browsing.

Furthermore, each instance of a Solution Explorer can be positioned anywhere in the available screen real estate and can be rafted together with any document window and other tool windows. This provides developers with the freedom to position their content in a way that is optimized for their task. They can establish a rich working context, where the position of documents and tool windows on the available screen real estate serves as an indicator of the task specific purpose of those documents and tool windows. For example the developer could have an instance of the Solution Explorer that shows the list of derived types for a class. They could then raft this Solution Explorer with a document window that contains the definition of the class. Now they have a view on their content that is optimized for understanding the class and its derived classes.

The developer has created multiple instances of the Solution Explorer hub and has rafted code files to each instance.

Previewing content to reduce document overload

When we started designing VS 11, one of the core experiences we identified as contributing to lost developer productivity was the experience around collecting and managing relevant code files and related artefacts. While working on a task, developers often end up with large numbers of open documents in the IDE as a side effect of performing activities such as stepping through code in the debugger, triaging search results, or foraging through files in a solution.

For example, imagine a developer is trying to track down a bug that shows up whenever a call is made to some method. They place a breakpoint on that method then step into every method that it calls, and the methods that they call, until finally reaching the buggy code. It’s not uncommon in these situations to step through a number of different methods and different files until finally reaching the buggy code. The end result is that large numbers of files end up in the document/tab well, many of which were only relevant for a short period of time while the developer was stepping through the code. The developer in turn ends up spending valuable time and effort dismissing or working around these irrelevant documents.

We have observed developers adopting one of two strategies to address the problem. In one, developers prune their open document set as they work. Each time an irrelevant document is opened, the developer quickly closes it. In the other strategy, the developer allows documents to pile up to a point where the number of open documents is unmanageable. They then resort to closing all documents and reopening the relevant ones. In closing all documents they lose useful valuable context that has taken time and effort to build up.

As noted above the obligation to close or work around no longer relevant open documents is a major contributor to lost developer productivity. It disrupts developer flow and prevents them from realizing the kind of ‘fast and fluid’ development experience they desire.

Preview Tab

In VS 11, the preview tab significantly reduces the number of files that get opened into the document well. This avoids the need to manage these documents all together and allows the developer to maintain their flow and concentrate on their work.

The preview tab achieves this by previewing every document that the developer doesn’t explicitly open (to see a demo of the preview tab and the multi instance solution explorer, watch Scott Hanselman demo these features in this video – start watching from around 27:21). Single clicking in tool windows such as Solution Explorer, Find Results etc. allows the developer to look at the file without paying the cost of opening a full tab. So the developer can triage search results for example without having to open multiple files and then close the ones they don’t need after finding the one they do. Or they can step through code in the debugger, and not have to worry about cleaning up all the files that they stepped into, once the debug session is over.

Each time the developer takes an action that would cause a file to be opened as a side effect, that file is opened in the preview tab instead. There is only one preview tab per document well, so the content of the preview tab is refreshed on each new file that gets opened. In the above debugging scenario, when stepping through all of the intermediate files until eventually reaching the buggy code, the intermediate files are opened in the preview tab instead of opening up as separate, dedicated tabs (see Figure 14 ). The end result is that instead of multiple files being opened in the IDE, only one relevant file (the file containing the buggy code) is opened.

There are no constraints to what can be done with a file when it is previewed in the preview tab. For example, developers can read the content in the file, scroll through it and copy content from the file to paste elsewhere. If that file contains content that is deemed relevant to the current task, that file can be opened in a persistent, regular tab in the following ways:

Edit the content. As soon as any kind of edit is made to the file in the preview tab that file will be opened in a regular tab automatically. This allows developers to work with content they need to keep around without having to force them to explicitly indicate they want to keep the file around.

Click on the ‘Open’ button. The preview tab has a button in between the file name and the close button. Clicking on this button will open the file in a regular, persistent tab. A new regular tab will be created showing the content of the file and the preview tab will close.

Double click on the file. Double click continues to work as it always has and will open the file in a regular tab.

Drag the tab. As soon as the developer clicks and drags on the preview tab it is turned into a persistent tab that can be placed in any doc well.

In conjunction with hubs such as the Solution Explorer, the preview tab further streamlines common workflows, such as browsing code relationships. This streamlining effect is particularly pronounced when using the keyboard as a mechanism to preview content. We strongly encourage you to try this. With the keyboard, you can use “Ctrl + ;” to quickly jump into the Solution Explorer search field and then use the arrow keys to highlight the content that you wish to preview. You can invoke the keyboard shortcut to bring up the list of pivots by typing the context menu shortcut key on your keyboard then use the arrow keys to choose a pivot, resulting in a new list of content. You can continue using the arrow keys to browse and preview this new list. In this way, you can browse and preview long code relationships without ever taking your hands off the keyboard. To see some detailed screenshots and learn more about the preview tab, read this blog post.

The developer has single clicked on LinePaint.cs in the Solution Explorer and is previewing the contents of the file in the preview tab

History

Removing the burden of having to manage irrelevant open documents provides a much more fast and fluid experience for the developer. But to maintain the win-win nature of that experience, it’s important that the developer can just as easily return to files and artifacts that they have previewed in the past but which they did not open into a regular document tab.

Prior to the introduction of the preview tab the developer could switch between every currently open document using the window switcher (by pressing Ctrl-Tab the developer sees a list of every open document and tool window). If they had closed the file that they wanted to return to though, they couldn’t easily switch to it. They would need to navigate to and open that file from some tool window or other command within the product. At that point the developer’s focus has now shifted to operating the tool rather than concentrating on the task they were working on, as they try to figure out how to get back to the file.

In order to maintain the developer’s focus on their task we have significantly improved the history functionality in Visual Studio 11. Instead of just showing the navigation history through the set of currently open documents, the history now shows every navigation step taken by the developer, regardless of whether or not the files navigated into are currently open.

So if a developer steps through some code then later decides that they want to review that code, they can use the history UI to do so. The history shows the list of files the developer stepped through and allows the developer to open any of the files by clicking on them. Even if the file is no longer open, the fact that the developer previously navigated into it means that they can easily return to it through the history feature.

The developer uses the history feature to browse through the list of locations in their code that they have recently visited.

In Summary

The new approach to browsing relationships that we’ve introduced within Visual Studio 11, together with the new Preview Tab capability, enables you to explore your code and related artifacts far more comprehensively and smoothly than you could before while significantly streamlining and enhancing many common development experiences. You’ll be able to explore a broad set of relationships with far less need to switch between tool windows. You’ll be able to explore project and file contents, debug, search, check references, review search results etc. without seeing your workspace become crowded by fleetingly relevant or irrelevant content. In short, you’ll spend far less time getting and keeping yourself oriented to your tools and content and far more on adding value to the applications you’re working on.

Monty Hammontree – Director of User Experience, Microsoft Developer Tools Division Short Bio: Monty has been at Microsoft for ten years focusing primarily on developer tool experiences. He and his team provide product design and user research direction for the Visual Studio product family. He has 25 years of industry experience in product design and user research management.

Tags

Overall I like the preview pane, it's a great feature. The only annoyance is when you preview a file using different line endings and you get the question if you want to change them. Perhaps make the preview pane don't care about that stuff?

6 years ago

Anonymous

I approve of this blog post! Now get rid of the dead old gray look… 😛 Really, the Windows Phone, Windows Start Screen and Metro applications look nothing like this…

6 years ago

Anonymous

I really like the history feature. That would save me so much time.

6 years ago

Anonymous

These changes are pretty interesting, and can save some time without being intrusive. I like it. Yesterday's on the other hand… Is there going to be anything changed based on that feedback? The monochrome icons and caps lock text really are a huge negative on the environment.

These seem like great ideas, particularly the document previews and being able to open multiple solution explorers. I wonder if it'd be worth allowing the user to "pin" document tabs, so that you could then close all but the pinned ones later? Perhaps the need for those is largely gone with the excellent preview idea you've already implemented. Or if you could group and save particular documents/tabs as named groups for later. For example, I often have a few files open to do one piece of work, then I run into a bug and start fixing that in some other files, and everything gets jumbled together. Being able to save which documents I have open to a named group, then close them and work on other stuff, then later close everything and go back to my original set of documents, would be brilliant. Similarly, for files that need to be edited as a group. (I guess this can be done using macros to a degree, but that's a pain to set up and manage.) I hope that the new combined solution explorer copes sensibly with C++ code where the namespaces and/or classes may be declared and/or defined across multiple .h and .cpp files. I've found that VS2008, at least, gets confused in places due to .h files declaring classes whose definitions are spread across several .cpp files, for example. Nesting classes in a tree below files, as it sounds like you are doing in VS2012, makes me wonder how that will work with classes that are not entirely contained within one file or another. I hope that if you have multiple solution explorers then VS2012 will remember where they each were when a solution is re-loaded. That will make it easier to do work that involves changes to two projects at once (e.g. work on both a plugin DLL and the main EXE's plugin-API). In the 2nd screenshot with the panels floated as a separate window, I am disappointed to see that the weird, non-standard, non-glass, non-shadowed window borders that VS2010 introduced are still there. Surely WPF can put a standard window border around its owned windows, can it not? I find it not only ugly but at times confusing because the lack of shadow and standard borders means separate windows sometimes appear to be part of each other. But, after yesterday's revelations, this is now quite low-down on the must-fix cosmetics list, I suppose. There's some great functionality and ideas being added to VS, as well as the back-end language compiler improvements you've been making the last few years. It really is a shame that the UI it's all wrapped up in has gone in this direction, apparently to prove that WPF was suitable for real work, which I think seriously backfired and proved quite the opposite.

6 years ago

Anonymous

Kudos for inventing the History and Preview tab features. I have a similar concern as @LeoDavidson: do the pivots all work with Native C++ and C++/CLI code? (ex: Solution Navigator from the VS2010 pack will not show the contained classes in .h/.cpp files for example) If so, in a performant way (ie. faster than the VS2010 F12 symbol-lookup/breakroom-trip feature)? The oppressive gray really distracts me as you were demoing in the video – my eye keeps scanning the screen for what I'm supposed to be looking at – lost in a sea of gray.

6 years ago

Anonymous

Love the neutral gray pallette. It lets the "adminsitrative overhead" fade into background and let me focus on code. Great job.

6 years ago

Anonymous

The "pivot" concept of totally changing my view when I want a different type of data seems counter to the stated goal of minimizing context switches. Make these things part of the normal tree view so they can just be expanded in-place when needed.

6 years ago

Anonymous

I love the neutral gray pallette. Brings back fond memories of my naval days aboard a U.S. battleship. Well done, sir.

6 years ago

Pop.Catalin

@Brian Jimdar, Good for you, I like to do that too: focus on code, whenever I get the chance. Unfortunately quite often I have to navigate around solutions with dozens of projects and thousands of files, and the monochrome icons don't help with that,

6 years ago

Anonymous

1. Search is cool, but seems slow. It either waits too long to start searching or it takes too long to find stuff. We want something snappy; we don't want to wait on it. 2. From Scott's linked video: The Navigate To option is nice, but as soon as the up/down arrow keys are used the search box looses focus (in VS2010); it shouldn't as I may want to change the search query. 3. Multiple SE is a cool feature! 4. Please bring back colored icons in SE! 5. Please have a shortcut key or something to easy "permanently" open a file. I don't want to open it from SE AND have to aim for a tiny pixel area to make it stick (i.e. what was one click in 2010 would be two clicks in 2012). 6. For MVC please have a shortcut key (F7?) to allow easy navigation between view, model, and controller. Thanks.

Wooo, I was joking when I said "why not make it worse and let the office 15 team have a go" Groan… Its a crap pile; Windows 3.1 had more style, and I'm guessing thats what you were trying to emulate with this nasty SWING UI wannabe. I just hope, as do many people, that this is an "option" like the telly-tubby crack-den styling of Windows XP was optional.

6 years ago

Anonymous

Form visuals, this is Disaster Studio Grays over grays, no clear distinction between zones. Hard to fast search and focus on desired zones. Icons with Light Theme – NIGHTMARE Why do you removed icons from tabs ? Icons are fastest way to recognize related elements, so removing them decrease speed in recognizing these element. If you want to do something with icons, then make them flat and decrease shades. Do not remove colors from icons !!! Do not use all caps fonts, because big fonts takes more space. Use small fonts and colors to make them better visible. There is no need do drasctcally save space, used for command. With today high-res displays, there are lot of space for code. Putting command into small spaces make them less visible and recognizable. VS 2010 is best looking. Make themes very similar to VS 2010.

6 years ago

Anonymous

Drab and depressing theme. :::HATE:::::, :::HATE::::: the icons! There is absolutely no way they work better or anything like as well as colored icons. Whoever thought they did is sadly mistaken. Everyone uses both color and shape to recognize them and not just shape.

6 years ago

Anonymous

Looks like a typical cross platform java app, and that's not meant as a compliment. Just bringing back the VS 2010 icons would brighten it up, not sure if it would be enough but it would be a good start.

6 years ago

Anonymous

I do like the cleaner UI with less toolbar buttons. But I don't like the icons! The gray color makes it much harder to distinct them. The colored icons in VS2010 are way better.

6 years ago

Anonymous

The interface improvements look interesting but I'll have to try them myself to be sure. However, the two things I'm really interested in are performance and stability. Let me repeat that: PERFORMANCE AND STABILITY! VS2010 is sadly lacking in both areas. I'd be much more impressed with v11 if you had dumped WPF and gone native or at least back to Winforms.

From distance new theme looks more like it is called "depression" not "light" – just simple changing from dark grey to blue in icons would improve overall feel of VS 11

6 years ago

Anonymous

I believe the masses have spoken. An overwhelming majority HATE the new (lack of) color scheme. A simple vs 2010 theme will quiet everyone. I hope that Scott Gu is listening. He has become famous and beloved because he listens. I am sure many people worked very hard, earnestly and dilengently on this new theme but I do not like it. Give developers a choice. Please do not cram this down our throats. We deserve better.

Absolutely *LOVE* the new color scheme and icons. Every button should be a different color? Sure, next they'll be telling you that every button on your keyboard should be a different color so you can find them eaiser. ("Waaaa, the 'K' key on my keyboard used to be yellow, and now I can't find it. Waaaa.") It's called *Design* (capitol D), look into it. Visual Studio team: You are finally taking a risk and moving boldly into a modern future. People fear change. It's natural. A few negative comments as an initial reaction will not represent the ultimate response from your full user base. Trust me: absolutely none of the above users are going to leave Visual Studio because they didn't like the new Icon color. I love it. Ship it.

6 years ago

Anonymous

On this second post I am still skeptical concerning the gray and monochrome icons. While I already know I'll love history, preview panes, search (if it is instant!), I can clearly see that, for example on the history screenshots, icons, colors and UI candies are missing to guide the user eyes quickly in the list of history items :o/ (time tag like 30s ago, 10mn ago, yesterday are missing also in the history) Btw, unfortunatly I didn't see any answer to my questions on the last post, which obviously is central since most of VS users are using addins and extensions: –>How long do you let to VS addin/extension partners to adapt their UI to the new VS11 look? –>Will it works with the previous VS addin/extension colorful icons/UI ? (which if YES, will provoke a lot of UI incoherence, which if NO, will provoke a lot of friction)

6 years ago

Anonymous

These changes are all positive … the UI changes still need to be rolled back. You were headed in the right direction with VS 2010 and now this? @Brian_Jimdar … you can't be serious.

6 years ago

Anonymous

I hope you're taking Microsoft Connect feedback as seriously as all the comments here in public view. I predicted there that you would get this kind of reaction over the lack of color in VS11.

6 years ago

Anonymous

I'm not sure what you mean when you use the word "rafting" here — I've never seen that used before with respect to the VS IDE (or any software, for that matter). Is this the same thing as docking, or are you introducing something different? Can you "raft" a tool window to a specific document tab, like this post seems to suggest, and have it be hidden when you switch to a different editor tab? Or are you just docking it like any other tool window, and it'll just be in the way as soon as you switch to a different file, just like you'd expect?

6 years ago

Anonymous

I like the VS 2010 IDE. I like my iDE colorful. Is there a way to customize the VS11 Ui to show me the colors as in VS 2010?

6 years ago

tugberk_ugurlu_

I like the new look. I am sure that this makes the IDE faster as well. This is not a toy, this what we use for developing apps. It should be simple. good job!

I have an OOT request: Could you make this blog view defaulted to "Excerpt View" instead of "Full Post View", just like IE and B8 blogs? It took ages loading blogs.msdn.com/…/visualstudio, especially with those many and long posts, combined with slow internet connection. Thanks.

I just can't get over what you've done to Visual Studio. I'm so glad you are listening, the proof of the pudding will be in what you actually put out, MS do not in my opinion, have a history of listening to their users – more "here's what you're getting, and ::::YOU WILL LIKE IT:::: !". I hope this new theme is all encapsulated in a single theme class somewhere, somewhere you can revert the changes easily, and not scattered across the entire application. Still sad :sadface:, still hopeful you will see this for the error it is before release though. Fingers Crossed.

6 years ago

Anonymous

i want the winforms designer on one screen and on another the code. Will that be possible with VS11? There need to be better multi-screen support on VS!

6 years ago

Anonymous

I like the dark theme, but I really hope there's an option to turn off the unnecessary capitals in the dock tabs/titles. Why do the least important bits of text need to stand out the most?

6 years ago

Anonymous

Make a shortcurt to unpin all windows, and another shortcut to get all windows as before.

There are some good ideas, for example search everywhere is really a good thing, adding new features to the solution explorer is another good thing, but the UI please, please listen the developers comment in all blogs posts announcing the VS11 Beta and, at least, give us an option to have the UI less depressive, if not completely roll back your work to VS2010 look and feel! It would be nice if you guys open a poll on acceptance of new look so you can see how many of us really like or dislike. There is however a suggestion in uservoice site visualstudio.uservoice.com/…/2623017-add-some-color-to-visual-studio-11-beta for bring back colors. Apart from UI perspective, what about perf? Looking at the VS2010 uservoice visualstudio.uservoice.com/…/top, it seems that many of us voted for a better overall performance, so are there any improvements in VS11? @Brian_Jimdar … you can't be serious.

6 years ago

Anonymous

I LOVE the new interface. As a designer who has to use visual studio to get work done it is great that you guys are finally creating tools that we would enjoy using. Developers may not like the new look but they'll get over it. The muted pallette allows use to focus on the content and not the chrome. Great job!!!

6 years ago

Anonymous

I approve changes and new features but the downside of this is the gray palette. Please understand that is really hard to navigate to other parts of solutions, options and menus/toolbars without significant visual differences. Yes, you can disable toolbars and so forth but for all of us that DO use them it is a nightmare not having the visual colored cues.

Please stop listening to people about colors and icons. I'm starting to wonder whether all of this public comment really has that much value…it seems like most of it is just noise. Every time I read a blog post on the a new feature the bulk of comments seem to say something along the lines of, "Please always let us use whatever new features you've worked on, but don't change anythin, and why is this taking so long? Linux on the desktop. Ron Paul 2012." Maybe comments would be more useful after the product has been released and you want feedback.

6 years ago

Anonymous

@Brian_Jimdar is correct. People who "get" design know that you guys are going in the right direction. Using Visual Studio is going to be much like using Adobe CS suites as the content will be much more prominent now!

6 years ago

Anonymous

@Robert: when I look at Solution Explorer, that is where my focus is, that is where my content is. Of course I want colors there, the same way I want colors (syntax highlighting) when I am focused on code in text-editor. By the way, you can hide/auto-h

6 years ago

Anonymous

Apple is introducing HiQ displays with ridiculously high resolutions and you guys are getting rid of color in your toolbar icons. Somebody is right. Who would you bet on? Seriously, I live in Visual Studio all day long and it is my favorite piece of SW so I have the moral authority to say STOP! Those screen shots are horrible and depressing. At least give me the choice of legacy mode if you must go this route. Is this an early April Fool joke?

to start with let me say i'm not a programer.. i'm a UI/UX guy… its very recently I shifted from Dreamweaver to VS2010 to better integrate me with my programming colleagues workflow.. and kinda have started appreciating the "VS ways" of doing things… but in no ways is VS2010 a replacement for DW, yet.. lots of quirks and missing things in the HTML/CSS/JS world of VS.. when i read about the new things coming in VS 11 especially the HTML/CSS/JS improvements i was excited and got very interested… AND then you people dropped the bomb of these two post on all of us unsuspecting VS users… another small titbit about me… i'm a WinPhone 7 user for the last year or so and I LOVE IT.. i also like the Metro things happening on the Win8 front… so without much further ado here are my thoughts on VS 11 "user interface"… i like the dark "theme" a lot and that's how my VS2010 looks like except for the icons (obviously)… to me the icons in VS 11 are not as clearly defined/identifiable/understandable as some/all of your UX guys would like you to believe.. speaking of which.. a 76 user test group to see the impact of new icons..!! really..!! if VS2010 had maybe 760 total users in the whole world then that "76 user" test group would made sense.. even at a total 7600 user-base a "76 user" group does not make sense and i'm pretty sure the total number of VS users is in millions if not 10s of millions or more… another thing i'm pretty sure of – when this "control" group (assuming it was the only group) of tester were presented with the icons to identify them, they were presented either on a big projected screen or as placards… even if they were shown on normal screens i bet they were bigger than their real world 16×16 pixels size.. only that would explain the group not showing any noticeable negative impact… the XAML icon in the solution explorer…!! they stand out like sore spots against the "In VS 11 we have transitioned to glyph style iconography throughout the product" statement… heh..!! tells me to expect such sore spots "throughout the product" i guess.. about the colors… color for humans is the biggest form of differentiation/identification… imagine our stoplights all in grey… not red, yellow and green… just grey..!! would that have worked for us..? nope.. right..? but by your UX people definition they should, after all a circle is also a type of glyph… the CAPS thing… forgetting that its aesthetically and typographically "wrong", its also very distracting in that those headings attract more attention than necessary.. that makes it "anti-Metro" as its grabbing more attention than the content.. don't know about Win8 but in WP7.x nowhere in the UI are ALL CAPS employed but "all smalls" are.. and probably in VS 11s case that would work too..!! get rid of the leading and trailing colons too… colons instead of lines.. who came up with that idea..!! by the way, the "ALL CAPS = screaming" etiquette is not just true on the internet… it is said that a good UX/UI always generates mostly positive response form the target audience which in this case is your "EXTERNAL" developer, developer, developer (sorry couldn't myself there 😀 )… so i would have to say your UX team was totally out of sync with its target audience… or they were not allowed to be exposed to the target audience before this point.. and judging by latest trends inside MS it's probably too late to expect any changes between beta and final release… finally be clear and courageous enough to accept that these are not "mixed feedback" concerning the UI.. mixed would have been 50/50 positive/negative at worst… but these are more like 30/70 positive/negative…

6 years ago

Anonymous

Those gray screenshots look surprisingly good at 1:1 scale. If anything please let me tweak background colors (including VS Express!). What I miss is ability of VS to adapt itself to the type of content being edited. I keep all tool windows auto hidden. This suits me fine except for UI editing in Designer where I wish toolbox and properties stayed open. Today VS offers separate layout for debugging (maybe full screen too); this is too little. Can you extend it to have docking state remembered separately for cpp/cs files and UI designer? Another limitation: horizontal scroll bar visibility. I wish I could use it in XML files and nowhere else. Can it be enabled on per file type basis? How about changing tab step in a single file only (like in VC6)? Thanks

The productivity power tools in VS 2010 it seems has been a great testing ground for the new features in this upcoming version. One thing that I suspect is not going to be included because of the new look, but I find extremely useful, is the different tab colors per project. The grouping and clear visualization of what file I'm looking at is of great help. Also, the scrolling ability is pivotal for me. The old drop down menu of 2008 was very frustrating if I have just one too many files open and requires two clicks to navigate. I though the updated scroll bar with the map mode was very well done. It gives a good visualization as to when a reference is hidden in a collapsed section of code. I have not had a chance to try the new version but a few other things that I hope are included are: searchable add reference dialog, fix mixed tabs/spaces, moving lines up and down with Alt + arrow keys, and ctrl + click for go-to-definition. While I do think the new solution navigator/explorer is of good design, I found it a but bulkier than the old one. A possible suggestion is if the arrows to expand a class could be invisible by default but come into view on hover. It is also hopefully 99% of the time that a file only has one class so the double rows being listed are just one more expander to click to get through to the methods you are trying to find. While this belongs in the last post, I have to be yet another strong vote against the new UI look. I found the 2010 version very appealing and actually makes me enjoy starting it up in the morning. The new look and feel just reminds me of 2003 which is a nine year step backwards in my opinion. It is drab and boring, I can't tell half of the icons apart or what they do, and the titles look off-putting. While it is probably a lot of work, this may have introduced a great opportunity to provide full skin support (not just colors) to Visual Studio. I hope this wasn't TLDR, but thank you for the work you do!

6 years ago

Anonymous

When you are on stage and show VStudio's massive grey panes don't even think about saying "I'm excited to be here today". No one is going to believe you. GREY = DEPRESSION. Haven't you learned anything from Seattle's weather?????

6 years ago

Anonymous

Please give us an option to turn on colours, makes things much easier to quickly click

6 years ago

Anonymous

Great new features. I'm personally no so fussed about the themes, so long as this version performs and is stable – your content should be king here not the environment in which it is created, if you don't like something with VS theme then just make sure your app doesn't follow …

6 years ago

Anonymous

First at all: the productivity improvements like including productivity power toys, preview tab and history button are the right way! Simplify the toolbars by hiding some buttons is also a good step – as a developer i wanna have as much as possible place for content (code, designer, ..). Most of the buttons in VS2010 are waste because the functionality behind could be triggered with "common" shortcuts. So the UI should only offer buttons which a uncommon or meaningful in processes where mouse navigation is usual. The question is: should VS be a tool for fools or professionals – and professionals should know the environment perfect and this means also to know as much as possible the shortcuts to avoid mousing. Whether i like a gray or colored UI will be showed by using the new VS. In the last few years i simplified my environment also in terms of eye catcher. Every prominent artifact pulls the eyes to it – so its consequentially to avoid this: black desktop (thanks to Stardock Fences), dark theme in VS, dimming/minimizing inactive apps, .. So the gray UI could be the right one for me. But: why you use titles in tool windows and then these titles are capitalized?? Outgoing from context in the window it should be clear, what window it is – maybe by arranging and docking the title is shown. After docking there is no need more. And the capitalized title in the current font uses place and is an unintentional eye catcher – please reduce the font and abstain from capitalization. Thanks

6 years ago

Anonymous

I kinda see what you're trying to do with the gray. What you have here is still needlessly ugly, but I agree with the *goal* of reducing chrome and clutter, and letting my code, rather than the countless toolbars stand out. You just need to actually hire a designer to make something that isn't also absurdly ugly. But the ALL-UPPERCASE seems completely random and misplaced. The only reason I can imagine for it is to emulate Metro, but Metro guidelines would never do *anything* like that. So please, just kill it. Quickly. With fire. It doesn't look like Metro, it looks like DOS filenames. It looks amateurish. The functional improvements sound very nice, however. Long overdue, of course, but they're very welcome. But the UI changes? It's everything that Microsoft UI has historically been ridiculed for: dull, ugly, inconsistent and badly-designed, with text that makes your eyes bleed (only now, it's no longer because of font rendering, but because of ALL-UPPERCASE idiocy).

6 years ago

Anonymous

I posted a comment, which, while a bit harsh, was also insightful and not a little bit funny. But, it is missing in action. Hmmm…

6 years ago

Anonymous

Excited…!!! Please, release Beta for us asap.

6 years ago

Anonymous

Couple of comments. First, Solution Navigator, Most developers for most of their files only have a single class in it. The filename is also exactly the same as the class name. It's a complete waste of space for these files to display MyClass.cs |__MyClass It is literally another layer of complexity as well as wasting space. Please fix this. Secondly, the history bring up a list – Great! Except it has the same problem the find currently has – you don't use columns! It's looks terrible and comes across as one big blog of garbage. There's 2 columns – Filename and Line of code. Put the lines of code underneath each other!

6 years ago

Anonymous

posted on the previous blog: I don't understand how you can determine with any statistical confidence when using JUST 76 participants on the icon study. I prefer the VS 2010 color icons much more, and it certainly doesn't distract me one bit from the code. Whoever made the decision to go with all gray should seriously reconsider. Please give us the OPTION of choosing colored icons. This is project management at its worst. Holy smoke. That's right all gray = smoke.

When Microsoft say "we are listening to you", I'd be more likely to believe it if the major, ancient, well-known bugs in the MSDN commenting system were fixed. If you type a comment and click the Post button, one of two things will happen: 1. The page will reload, positioning you back at the top of the page. Your comment will not have been posted, but there will also be no error message. Or: 2. The page will reload, positioning you within the comments thread, with a green box confirming that your post was actually submitted. You only get the 2nd, successful case if you type/paste your comment and click Post within a very short time of (re-)loading the page. So the workaround is to write your post out, then put it in the clipboard, refresh the page, then paste the post and click the button. This is not at all obvious, and I have not seen anything like this on any other website. It seems that blogs.msdn has a *ridiculously* low session timeout, coupled with a lack of error handling / error messages when you try to post via an expired session. This bug has existed since the "/b/" URLs were introduced, and every large comment thread on MSDN — including this one and the previous one — has people complaining that the posts they typed up did not make it through. Microsoft cannot possibly be unaware of this problem, given the volume of complains and given that it causes problems on every single comment thread hosted on blogs.msdn. Crazy idea: If you are going to reinvent the wheel and build your own blogging platform, maybe take the time to fix the problems people keep reporting in it? Back on topic, crazy idea 2: Microsoft clearly have lots of teams who want to create custom UIs, like the much-criticised VS2012 one here. Microsoft also own both the Windows platform itself and the APIs, IDEs, frameworks and libraries used to build most of the UIs on top of the OS. So, why don't you make all your apps draw controls using the standard APIs and move the people working on per-app custom UIs into a team where they can create new visual styles (and improvements to the theme APIs and threadbare documentation) which can be used *by the entire platform* and *at the user's choice*? You could even expand the API to allow individual apps or even individual modes/parts of apps to use different visual styles, configured by the user. Then, users who want everything to be gray, or want it to be impossible to tell between a tab control and a static label, can apply a visual style which does those things. Users who don't can use another visual style. Users who want all well-written apps to look consistent can have that, and those who want some apps to look different can have that too. As it is, modern Windows doesn't even allow users to change the colors of standard buttons, which is ridiculous. The UI is long overdue an overhaul, and the time and effort making Office and Visual Studio look completely non-standard should instead go into providing more visual options for the entire desktop OS (Office and VS included). It's good that MS finally seem to be admitting that WPF was a disaster. Maybe once the WinRT/Metro diversion is over, and you get back to spending time improving the long-neglected native desktop APIs, you might take a look at this… I will now put this comment in my clipboard, refresh the page, paste it back, and click Post. 🙂

6 years ago

Anonymous

I think the new Solution Explorer is interesting, but without a simple and bare Solution Explorer without all the extra features you talk about here I think it will actually make matters worse for my normal usage of the Solution Explorer. Adding more and more to the Solution Explorer does not yield a better experience. I wish you would have stayed with the Solution Navigator (power tool) for the integrated, many tools in one solution and kept the simple and FAST solution explorer as it was. No doubt the solution explorer will be slower more cluttered than before. So please keep the distinction between solution explorer and solution navigator in tact and let solution explorer be as simple as possible.

6 years ago

Anonymous

The UI looks to be following down the route that Blend took. After having used Blend alongside VS for the past few years, I'm comfortable saying it doesn't grow on you or become more pleasing to use with time, it remains just as awkward to quickly scan for the tab or section you want on the UI as it is on day one. Switching to Silver & Monochrome may appease some in the Design camp, but it removes one of the key quick hints your brain uses to navigate around a complex UI. This isn't a step forwards for UI – If I'm forced to spend the next 3-4 years working on a washed out monochrome UI I'm not going to be impressed. Many of the other UI features people are raving about seem to be taken from a series of popular VS2010 extensions. It's nice that the UI will have some of them directly, but not particularly ground breaking I'm afraid.

6 years ago

Anonymous

I hate the ugly Color Scheme of VS10 but you showed me, that you can much more ugly. For me were the color changes between office 2007 an 2010 a breakthrough. I love office 2010, it is clear, simple and well-conceived. That’s light not yours. Fix it or let us fix that for ourselves.

6 years ago

Anonymous

Wow this looks terrible.

6 years ago

Anonymous

Looks like we're getting increased productivity out of VS11 and this is a step in the right direction regardless of what it looks like. Am wondering, I have Interfaces all over the place and I'm wondering if Go To Definition (F12) can take me to the method that is being used rather than the Interface?

6 years ago

Anonymous

It needs a splash of color! I like the metro-inspired look and feel but the overall impression from a distance is very dull and "battleship gray." It reminds me too much of Eclipse, ewwww. I would love to see some striking Bing imagery or some bold Win8 colors somewhere in there. It doesn't have to be gaudy; a little color goes a long way.

6 years ago

Anonymous

I would also just add that anything you can do to improve performance will make the whole experience better. Going from older versions to VS2010 was a great experience except that everything seemed to take longer. That was the main complaint my team had.

Are they going to add the 2007 style ribbon? It is nice ^^ 🙂 I looks great, but do something about the dead grey theme/color. That was all!

6 years ago

spongman

come on guys, black text on a white background, please (or visa versa). NOT hsl(0,0,11) on hsl(210,0,90), please. that's just not enough contrast for text that I'm going to be reading for about 1/4 of my life. if anything's going to hurt my ability to focus on the content, it's going to be me continuously cursing your names for causing me to squint in order to satisfy some need to try the latest UI fad on my work environment. no hire. seriously.

6 years ago

Anonymous

I also miss the colours, this new version looks dim, depressing and old. If any design changes are to be made, I think Visual Studio should conform a little more to the new Metro styling. Obviously it can't get there quite yet, but I think more steps should be taken in that direction. Above all though, please bring the color back, those pictures look like a color filter was applied to the code for the purpose of this presentation. I have never had trouble focusing on the code with previous versions of Visual Studio, and this look just makes me feel gloomy 🙁

6 years ago

Anonymous

I also miss the colours, this new version looks dim, depressing and old. If any design changes are to be made, I think Visual Studio should conform a little more to the new Metro styling. Obviously it can't get there quite yet, but I think more steps should be taken in that direction. Above all though, please bring the color back, those pictures look like a color filter was applied to the code for the purpose of this presentation. I have never had trouble focusing on the code with previous versions of Visual Studio, and this look just makes me feel gloomy 🙁

6 years ago

Anonymous

I am, however, a fan of the all caps fonts. It makes them stand out and clearly highlight different sections, which I felt I had a little trouble with in previous versions. The more I look at them and think about it, the more I like the all caps fonts for section headers, and I would even like to see them used a little more, as it fits the Metro style of simplicity.

The new features, such as enhanced Solution Explorer, preview tab, and Quick Launch, are great. But we've seen them before in previous blog posts and the developer preview. However, the new IDE theme is horrific IMO. The soulless icons are awful, the all-caps text is difficult to read, and the lack of icons on pane tabs will make it harder for me to identify them. The colon-lines look amateurish, and the uniform grey looks like 60s concrete block architecture. VS2010 (and VS11 dev preview) had a nice feel to them – if you're spending all day working in one application, you want something pleasant to look at. Here, I prefer the dark theme to the light one, but even that's too high-contrast to be uncomfortable for me. I appreciate that some others may like the new theme; but what I'd ask for at this stage is for you to just reinstate the VS2010 theme – icons, lines, colour and all. Leo – you're not wrong. I reported the timeout issue ages ago and had a little conversation with the blog team about it, but it doesn't seem to have been fixed. Like you, I've developed a habit of copying my posts to the clipboard before submitting 🙂 Even today, I signed in with the link at top-right, put my password in, only to find when the page came back that I wasn't actually signed in at all. Pressing it again worked, without requiring my password this time. But now the comments were chopped into pages, with no obvious way of showing them all at once. Looked in the settings, but didn't see anything that appeared to control that; pressed "back" in my browser only to be told the blog page had expired. Had to re-visit my shortcut to this blog and navigate back to the post. I think the Windows Live ID/MSDN infrastructure is probably the buggiest web service I've ever used – but as Microsoft-focussed developers, we're stuck with it. (As expected, I hit the timeout and scrolled down to notice my comment hadn't been posted…)

6 years ago

Anonymous

Do the 40 active developers used in testing this souless UI constitute even 0.00001 of real programmers? Hint: 10's of millions / 40… Bonus Question: How many of the 40 are actually "designers" and not really developers? Sorry designer guys, but your brains work differently. Having input from designers for a programmer's tool is like getting input from a chef for the design of a farmer's tractor.

6 years ago

Anonymous

Great blog – with lots of history /background. lots of improvement, but as Andrew mentioned time-outs are still frequent and there are np indications to them being addressed.

6 years ago

Anonymous

Great Blog – with lot of background / history. lot of improvement but as Andrew says time-outs are still an issue which seems there is no mention of addressing soon.

6 years ago

lmkz

I guess there will be no XP version? Why? Just so you can get users onto Win 7? Can't see any technical reason… We are stuck on XP due to our dinosaur-like corporate inertia. Disappointing. As for the UI, time will tell, will have to use it before passing judgement. It sure looks ugly. I liked the comment by #LeoDavidson about building all this UI stuff into the OS and letting it decide look and feel via themes, rather than every app reinventing the wheel.

@Patrick Smacchia to answer the following: –>How long do you let to VS addin/extension partners to adapt their UI to the new VS11 look? My company (Riverblade) develops three VS extensions (Visual Lint, Visual TICS and ResOrg), and the first we h

6 years ago

Anonymous

Great Blog – with lot of background / history. lot of improvement but as Andrew says time-outs are still an issue which seems there is no mention of addressing them soon.

6 years ago

Anonymous

This is a huge step backwards. Please… a) Bring back the color, especially for the icons. b) DON'T USE ALL CAPS FOR THE DOCKABLE PANE CAPTIONS! c) Bring back the icons for the dockable pane tabs

6 years ago

Anonymous

ok just downloaded and tried it. think I feel depressed after using it…please bring back to color icons, i m begging u…..

6 years ago

Anonymous

The following things are absolutely awful: – The monochrome icons: it's even worse than VS.NET 2002 or 2003 that were 16-bit icons. – The upper case text in toolwindows captions. – The :::::: in toolwindows captions: what's the need for this – The lack of gradients and borders At the very least you should give the option of using the VS 2010 look & feel, if not removing completely the new look & feel.

6 years ago

Anonymous

I am a person with visual disability I am an albino and this UI experience made me feel like VS team even never thought of people with visual disabilities. Using dark theme is a little bit easy to work with, but after working with this UI for about 1 hour I had a terrible headache and even can’t image how I would work in feature. Please keep colors from VS 2010

6 years ago

Anonymous

Man, I love .NET, and I love Visual Studio, but please, don't *** it up, don't mess it, the UI is really ugly, even the new logo in ugly. The old logo was just beautiful, why did you make that great experience of VS2010 in this ***? I'm sad, because I really love C# and Visual Studio was one of the greatest things C# had. Now I'm really sad and feeling lost.

@thenonhacker: if you're making everything white, you should add some borders and more contrast between all the windows/toolbars. Or add some LITTLE grays — it's all too WHITE now. (why are everybody making things too far?)

6 years ago

Dave A

I don't like the new look at all, a real backwards step. I skin VS2010 using the Expression dark skin. On other machines I use the stock skin. The thing is I can already in VS2010 choose a lokk that I like. If this VS2011 is a skin, even the default skin, then that is fine, so long as I can choose another.

The perf improvements and other features are great, really welcome editions. The UI styling is not.

After using this for a few weeks and honestly giving it a great try, I consider this a greatly unusable experience. I've grown used to expecting color to aid my selection of buttons, icons, and other elements.

I don't think the elements of Metro design are well applied. Although I expect more streamlined elements throughout the interface and more typography to drive design, I did not expect to have a monotone experience as though I'm staring at an old fashioned black screen with green text.

I understand the intent, where code is to be brought to the foreground; however, we developers have grown accustomed to the iconography of Visual Studio over 12+ years. You can improve the icons, but making them all black and gray is not an enhancement, in my opinion.

Please, in the next releases, add some color back to the icons.

6 years ago

Yoyo

Can we get a word from anyone at Microsoft regarding the huge number of negative comments other than "we're listening (but not doing anything)"?

6 years ago

Aaron Smith

Hey guys. If you want to see what a really properly done UI is, look at the new Photoshop CS6 beta that was released today. That's a proper experience right there.

6 years ago

anonymous

are your ui designers aware of the fact that "color and shape" gives much more information than "shape only".

apart from being bland and somewhat depressing, the new ui makes it a lot less efficient especially in projects where there's a lot of different element types.

sometimes, changing things which worked before just for the sake of changing it is really not an improvement. this is a work tool here, not some new toy for teenagers who wants a new style…

6 years ago

Batman!

Holy gray-is-everywhere Batman!

6 years ago

Beta 2

I hope you release a Beta 2 after the colors/vs 2010 theme is restored.

6 years ago

Dean

Please release another beta with the corrected colors/icons/theme **BEFORE** releasing the RC so you can get feedback on the colors/icons/theme.

6 years ago

Graham

Hi Guys & VS Dev Team,

Has the "Unshelve" Feature being left off on the TFS bits? I can't find the button anywhere!

Thanks… I hope it hasn't been forgotten! =) Or if so a patch can come out soon so I can restore my shelveset that I kinda need 😉

Another must-have piece of equipment is a cell phone to
enable easy response to your customers. This lets them know
how they have done and it helps them to improve their cleaning.
There are a couple of excellent e-courses available that
give a lot of really valuable information on how to structure your business,where and how
to get clients, how to calculate prices, what equipment and supplies are needed etc,
and in my opinion are well worth the $30 or $40 they cost.

These same apartment cleaning services Los Angeles use 100% biodegradable
and green products. Many mothers today work outside the home in addition to raising children, and
sometimes housework suffers as a result. You don’t want to be inhaling dust or preparing food
on dirty, contaminated surfaces.

You can choose your own timings and above all, you can choose how much work
you want to take up. When apartments get the unit “make ready” for the next tenant,
they usually employ a cleaning service to complete this.
You don’t want to be inhaling dust or preparing
food on dirty, contaminated surfaces.

You can choose your own timings and above all, you can choose
how much work you want to take up. Finally, I think parents and grandparents
need to make it clear to students that keeping the apartment clean is a personal health issue.
Equipment should also be serviced on a weekly basis to make them more efficient.

Before you start calling properties and getting estimates, you may need to find out what you need
cleaned. Finally, I think parents and grandparents need to make it clear to students that keeping
the apartment clean is a personal health issue. To begin with, you would
need an office, some people who will clean the apartments and
also some cleaning equipments.

Remember that people trust real address workplaces
more than online ventures because contact with the business is more
real. Finally, I think parents and grandparents need
to make it clear to students that keeping the apartment clean is a personal health issue.
These mops can be a bit pricey initially, but over time will add up to hundreds of dollars in savings on floor products, especially if
you have many types of flooring.

These same apartment cleaning services Los Angeles use 100% biodegradable and green products.
There is no limit on what you earn – Once you have made a good base
of clients, you will see that you can earn as much as you want.
You don’t want to be inhaling dust or preparing food on dirty, contaminated surfaces.

These are the right size for most cleaning jobs, very absorbent, lint free, and best of all reusable.

The places that are found in this lovely area are there
for the convenience of the customers. Most of the companies that offer apartment cleaning services are bonded and insured so that if any accident were to happen they will take full responsibility for the replacement.

Remember that people trust real address workplaces more than online ventures
because contact with the business is more real.
This lets them know how they have done and it helps them to improve their cleaning.
Most of the companies that offer apartment cleaning services are
bonded and insured so that if any accident were to happen they will
take full responsibility for the replacement.

If you have the tendency to horde things, you will have to learn let go.

There is no limit on what you earn – Once you have made a good base of clients, you will see that you
can earn as much as you want. You don’t want to be inhaling dust or preparing food
on dirty, contaminated surfaces.

These are the right size for most cleaning jobs, very absorbent, lint free,
and best of all reusable. Many mothers today work outside the
home in addition to raising children, and sometimes housework suffers as a result.
Equipment should also be serviced on a weekly
basis to make them more efficient.

If you have the tendency to horde things, you will have to learn let go.
This lets them know how they have done and it helps
them to improve their cleaning. You don’t want to be inhaling dust
or preparing food on dirty, contaminated surfaces.

These are the right size for most cleaning
jobs, very absorbent, lint free, and best of all
reusable. Now that you have a set of questions to work with, its time to start contacting companies and get a few
estimates. While you schedule your work, make sure that you make
allowance for cleaning different parts of the house on different days.

Before you start calling properties and getting
estimates, you may need to find out what you need cleaned.
You can also keep containers of various colors and sizes in different
rooms. Is there anything special that the cleaning service needs to know about.

You can choose your own timings and above all, you can choose how much work you want to take up.
Finally, I think parents and grandparents need to make it
clear to students that keeping the apartment clean is a personal health issue.
There are a couple of excellent e-courses available that give a lot
of really valuable information on how to structure your business,where and how to get clients, how to calculate prices, what
equipment and supplies are needed etc, and in my opinion are well worth
the $30 or $40 they cost.

Apply it to a soft cloth and use it to wipe down woodwork and
furniture. Finally, I think parents and grandparents need to make it clear to
students that keeping the apartment clean is a personal health
issue. Is there anything special that the cleaning service needs to know about.

These are the right size for most cleaning jobs, very absorbent, lint free, and best of all reusable.
The places that are found in this lovely area are there for the convenience of
the customers. You don’t want to be inhaling dust or preparing food on dirty, contaminated surfaces.

You can choose your own timings and above all,
you can choose how much work you want to take up.
It is an extremely versatile product that is inexpensive and helps cut back on the use
of expensive chemicals. While you schedule your work, make sure that you make allowance for
cleaning different parts of the house on different days.

Apply it to a soft cloth and use it to wipe down woodwork and furniture.
Will you need the cleaning service to do a thorough cleaning for you.
Of course, you don’t want to be doing something every minute of the day,
so take some time to relax too.

These same apartment cleaning services Los Angeles use 100%
biodegradable and green products. You can also keep containers of various colors and
sizes in different rooms. Most of the companies
that offer apartment cleaning services are bonded and insured
so that if any accident were to happen they will take full responsibility for the replacement.

These are the right size for most cleaning jobs, very absorbent, lint free, and best of all reusable.
This lets them know how they have done and it helps them to improve their cleaning.
Is there anything special that the cleaning service needs to know about.

You can choose your own timings and above all, you can choose how much work you want to
take up. You can also keep containers of various colors
and sizes in different rooms. These mops can be a bit pricey initially, but over time will add up to hundreds of dollars in savings on floor
products, especially if you have many types of flooring.

4) One Cleaning Supply at a Time – Instead of cleaning one room top to bottom then moving onto the next on cleaning day, pull
out one cleaning supply and use it everywhere you need to in your
home. Many mothers today work outside the home in addition to
raising children, and sometimes housework suffers as a result.
Equipment should also be serviced on a weekly basis to make them more efficient.

These are the right size for most cleaning jobs, very absorbent, lint free, and best of all reusable.
This lets them know how they have done and it helps
them to improve their cleaning. These mops can be a bit
pricey initially, but over time will add up to hundreds of dollars in savings on floor
products, especially if you have many types of flooring.

Apply it to a soft cloth and use it to wipe down woodwork and furniture.

This lets them know how they have done and it helps them to improve their cleaning.
Most of the companies that offer apartment cleaning services are bonded and insured so that if any accident were to happen they
will take full responsibility for the replacement.

Another must-have piece of equipment is a cell phone to enable
easy response to your customers. There is no limit on what you earn – Once you have made a good base of clients,
you will see that you can earn as much as you want.
Most of the companies that offer apartment cleaning services are bonded and insured so
that if any accident were to happen they will take full responsibility for the replacement.

If you have the tendency to horde things, you will have to
learn let go. Finally, I think parents and grandparents need to make it clear to students
that keeping the apartment clean is a personal health issue.
While you schedule your work, make sure that you make
allowance for cleaning different parts of the house on different days.

Another must-have piece of equipment is a cell phone to enable easy
response to your customers. Will you need the cleaning service to
do a thorough cleaning for you. There are a couple
of excellent e-courses available that give a lot of really valuable information on how to structure your business,
where and how to get clients, how to calculate prices, what equipment and supplies are needed etc, and in my opinion are well worth
the $30 or $40 they cost.

Before you start calling properties and getting estimates, you may need to find out what you need cleaned.
The places that are found in this lovely area are there for the convenience of
the customers. Regardless of whether you have a 3 bedroom
apartment home or a studio, your place will get dirty.

If you have the tendency to horde things, you
will have to learn let go. Will you need the cleaning service to
do a thorough cleaning for you. You don’t want to be inhaling dust or preparing food on dirty, contaminated surfaces.

These same apartment cleaning services Los Angeles use 100% biodegradable and green products.
When apartments get the unit “make ready” for
the next tenant, they usually employ a cleaning service to complete this.
Of course, you don’t want to be doing something every
minute of the day, so take some time to relax too.

If you have the tendency to horde things, you will have to learn let go.
When apartments get the unit “make ready” for the next tenant, they usually employ a cleaning service to
complete this. These mops can be a bit pricey initially, but over
time will add up to hundreds of dollars in savings on floor products,
especially if you have many types of flooring.

These same apartment cleaning services Los Angeles use
100% biodegradable and green products. Finally, I think parents and grandparents need to make it clear to students that keeping
the apartment clean is a personal health issue.
There are a couple of excellent e-courses available that give
a lot of really valuable information on how to structure your business,where
and how to get clients, how to calculate prices, what equipment and supplies are needed etc, and in my opinion are well worth the $30
or $40 they cost.

These same apartment cleaning services Los Angeles use 100%
biodegradable and green products. It is an extremely versatile product that is inexpensive and helps cut back on the use of expensive chemicals.
You don’t want to be inhaling dust or preparing food on dirty,
contaminated surfaces.