What blogs should the Visual Studio Core team read?

I want to put together a list of recommended blog reading for my team. Ideally, I’m looking for blogs that talk about features we own, for good and for bad.

Here’s a quick breakout of what the VS Core team owns:

  • MS Build

  • Creating Projects and Solutions; Adding new or existing items

  • Editor and Code navigation (Object Browser, Find in Files, etc)

  • Tool Windows used by all languages (except for debugging tool windows – another team owns those), ie Task List, Error List, Toolbox, etc.

  • Tools – Import Export Settings; Tools – Options; Window management

  • Help system Extensibility – Add-ins, Macros, DTE, VSIP, etc.

Just send me a pointer to your blog, and I’ll add it to the list of recommended reading.


Comments (6)

  1. Travis Owens says:

    Imho anybody on the VS teams who isn’t checking out the competition (ex: KDevelop) is doing themselves, Microsoft and the developement community a huge disservice.

    The worst blogs to read are the ones who rant that VS is the best thing since sliced bread (which it arguable is 🙂 but praise won’t inspire new features or improvements. The best blogs are the ones critical of VS, pointing out faults.

    Obviously a good starting point would be:




    I know none of these IDEs are up to par with VS, it’s still a good idea to keep tabs on these projects. Obviously these guys are stealing the ideas of VS, it would be a shame if the VS team isn’t inspired by the ideas they impliment. Remember these IDEs are approaching developement from a clean slate, they don’t have to worry about mimicing older versions of their application, and can easily come up and impliment better ideas.

  2. InesK says:

    If you plan on reading blogs about the Eclipse IDE/Platform, I recommend:


    You will find it more useful than eclipse.org.


  3. Jason R says:

    Does your team own the Output Window?

    Reaosn I ask is, seems to me that this is the one window which is seriously due for an update.. I mean, it’s basically the same as old Turbo C IDE in DOS.

    It’s sort of half way there with the task list, but it’d be really nice to not even have to see the output window ever again.

  4. saraford says:

    Jason, yep, my team owns the Output Window. Can you give me some examples of how this tool window needs an update or how you would like to see it improve? Or better yet, you can go to http://lab.msdn.microsoft.com/productfeedback/ and file a request. Let me know what i can do.



  5. James Avery says:

    Check out the feed for Visual Studio Hacks –


Skip to main content