Blog - Title

Visual Studio 2013 Current Status

  • The Ultimate Visual Studio Tips and Tricks Blog

    Using the WPF Tree Visualizer

    • 13 Comments

    Versions:  2010
    Published:  1/29/2010
    Code:  vstipDebug0004

     

    For those not familiar with WPF Trees, check out this article:  http://msdn.microsoft.com/en-us/library/ms753391(VS.100).aspx

     

    Now.  For those that ARE familiar with them have we got something for you:  WPF Tree Visualizer.  Yes, it started out as a CodePlex project and ended up in the product itself as a visualizer.  But how do you use it? 

     

    1. Enter debug mode using any method you prefer.
    2. Once you are there take a look at either a DataTip, the Watch window, the Autos window, or the Locals window.  For this example, I will use the Autos window.
    3. Choose any control in the Autos window and then click on the magnifying glass way over to the right of the control name.
      image
    4. You will see a drop down list.  Choose the WPF Tree Visualizer to get this dialog:
       image
    5. This thing has a lot of different parts so let's take a look at each one.  First, the Visual Tree shows you the hierarchy of the controls:
      image
    6. Clicking on any particular node of the tree will show you the Rendering view just below:
      image
    7. Also, the selected control will have its properties displayed in the large area to the right:
      image

    8. In, both, the Visual Tree and the Properties area you can search/filter the results by typing into the "Search" or "Filter" textboxes respectively:
      image

    9. WARNING:  Watch out for the results as they may not be what you expect.  See the extra items in the list that don't have the word "context" in them?  How did they get there?  Well, if I scroll to the right and look at other properties you can see how it happened:
      image 

      Currently, there is no way that I am aware of to change this behavior.
  • The Ultimate Visual Studio Tips and Tricks Blog

    Announcing the Tips and Tricks SWAG Fest Beginning April 12th

    • 13 Comments

    ThinkGeek

     

    So, someone thought it would be a good idea to give me some money for SWAG to give to my readers.  Naturally, I loved the idea!  So I went and bought a whole bunch of $100 ThinkGeek gift certificates.  The problem is how to give them away?  After much thought (about 10 minutes, at least), I figured the best way was to give them away whenever I felt like it. 

     

    Okay so there you have it.  Beginning April 12th (Visual Studio 2010 Launch Day) I will be giving away ThinkGeek gift certificates.  I’ll be picking people who show love for the Visual Studio Tips and Tricks blog.  There are some basic ways you can do this:

     

    1. Leave some cool comments on the tip(s) you like the most
    2. Tweet about the Tips blog using the #vstips hashtag
    3. Show some blog love by cross posting to your blog if you have one

    Feel free to get creative and let me know about it.  That’s pretty much it.  Very simple really.  Look for the fun to begin on Launch Day.

  • The Ultimate Visual Studio Tips and Tricks Blog

    Select the Current Word

    • 13 Comments

    Keyboard:  CTRL + W
    Command:  Edit.SelectCurrentWord
    Versions:  2008,2010
    Published:  4/5/2010
    Code:  vstipEdit0039

     

    Download the seriously cool Tip of the Day Extension to get the daily tips delivered to your Start Page!

     

    You can easily select the current word in Visual Studio by simply putting your cursor in the word to select:

    image

     

    Then press CTRL + W and it will automatically select the current word:

    image

  • The Ultimate Visual Studio Tips and Tricks Blog

    Split Your Windows

    • 13 Comments

    Menu:  Window -> Split
    Command:  Windows.Split
    Versions:  2008,2010
    Published:  3/5/2010
    Code:  vstipEnv0004

     

    Did you know you can split your windows?  This feature has been available in a lot of Microsoft products for some time.  You can simply go to Window -> Split on the Menu Bar or you can use this mouse technique:

     

    1. Go the upper right-hand corner of a document window and look for the splitter control:
      image
    2. Click and hold on it and drag it down to begin the split process:
      image
    3. You can now see different places in your code to, for example, call a method while looking at the definition:
      image 
  • The Ultimate Visual Studio Tips and Tricks Blog

    Coding Faster: Give Me Your Thoughts

    • 13 Comments

    Folks,

    Just an update on the book.  It appears that it may be over 300 pages as originally planned so I am seeing if that is an issue with the publisher.  Would you have a problem if the book was larger? 

     

    Also, I've gotten another draft of the book as we move along and, just as I have always done, I would like to get your thoughts.  I've attached the PDF for your review.  Let me know your thoughts.  Bear in mind is it a rough draft and some things will change.  For example, "Free Your Document Windows" will become something like "Multi-Monitor Support" as I review the titles. 

     

    Also, I will most likely be trimming out the more trivial tips.  The tricky part is that one person's "trivial" is another person's "cool" so I'm erring on the side of too much information rather than not enough.

     

    Z

  • The Ultimate Visual Studio Tips and Tricks Blog

    Visual Studio vNext IDE Enhancements

    • 13 Comments

    ===

    Quick Housekeeping Note:  I’ve deprecated the old Visual Studio Tips extension and have tried to get it removed from the gallery so it isn’t available anymore but have had little success.  I am currently not planning to replace the tool with a new version but am open to suggestions as to a viable alternative.  For now I suggest you use your favorite RSS feeder or visit the blog directly.  Now on with the post…

    ===

     

    With the BUILD conference (http://www.buildwindows.com/) just around the corner and lots of announcements coming I thought now would be a good time to pause the usual posts and talk about the next version of Visual Studio (vNext) and how you can prepare for some of the goodness to come.  This is a high-level look at what is coming and I will be blogging in much more detail on the features throughout the vNext cycle.  With that said, I’ve intentionally left out any images of the IDE for this post in favor of brief feature descriptions.  Additionally, I will be blogging and tweeting directly from the BUILD conference while I am there to keep you up to date on the latest revelations that are coming out.  To get a sneak preview of some of the features make sure to see the following video:

     

    Microsoft Visual Studio IDE Futures

    http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DEV326

     

    vNow

    Visual Studio 2010 introduced a great new extensibility model that made custom additions very easy to make.  You can find these extensions at the Visual Studio Gallery (http://visualstudiogallery.msdn.microsoft.com/)  and, if you haven’t explored some of these great additions, I suggest you browse through the gallery to see the items there.  When asked which extension I suggest everyone download the number one answer I give is always been the Productivity Power Tools (http://visualstudiogallery.msdn.microsoft.com/d0d33361-18e2-46c0-8ff2-4adea1e34fef?SRC=Home).  Download it now.  Seriously.  Now. 

     

    We have (and will going forward) use extensions to field test new features that will be included in future versions of Visual Studio and it is a safe bet that some of the Power Tools will find their way into the vNext.  If you watched the video mentioned above you will hear Weston Hutchins mention this as well.  What better way to see what people want than to let them vote by actually downloading and using a feature?  Granted it’s a little harder to focus on individual features when a lot are packed together but, even then, we get plenty of feedback on what people like and don’t like.

     

    vNext

    Once we get beyond VS2010 then we can start looking at the new features that have been publicly revealed so far.  Here is a list of things you can expect in the next version:

     

    Project Round-Tripping

    One of the bigger pains in prior versions of Visual Studio is moving a project between versions.  It was an all-or-nothing proposition typically due to schema changes to the proj files.  If you opened a VS2008 project in VS2010 and converted it to the new project format then that project could no longer be opened in the prior version.  For those that have experienced this you know this wasn’t entirely true and you could do a little proj file hacking to go back but it wasn’t fun or intuitive to do so.  Visual Studio vNext will solve that issue.  You will now have the ability to open a project in the new version of Visual Studio and still go back to prior versions.  The net effect is you can have different teams on different versions of Visual Studio but still able to share projects with each other!

     

    Search the IDE

    With the dizzying array of menu items, toolbar buttons, options, files, etc… it is often difficult to remember where a particular item exists.  VS vNext adds the ability to quickly search the IDE for these things.  A good analogy would be to compare it to the ability to search programs and files when you click on the start button in Windows.  I don’t know about you but I don’t look for files anymore for the most part, I just hit my Windows key then type in what I am looking for then select what I want.  Imagine that level of functionality inside the Visual Studio IDE and you have an idea of what this new feature does.

     

    Solution Explorer Enhancements

    Multiple Instances of Solution Explorer

    vNext supports creating new instances of Solution Explorer so you can have focused areas (one project in one instance and another project in a second instance) for working on multiple monitors.  Additionally these instances can be nested inside windows that have been pulled outside the IDE for use on other monitors.

     

    Navigation

    In the Productivity Power Tools we introduced the Solution Navigator with some cool new features that have found their way into the new IDE.  The ability to drill down into the classes then members from Solution Explorer now exists.  You can right-click, say, a method in Solution Explorer and see some new terminology:  Calls, Is Called By, and Is Used By.  Calls represents the call hierarchy for the method; Is Called By represents a list of methods that call the current method; and Is Used By represents all the specific file, line, and column positions where the method is mentioned.

     

    Search

    Much like the new search for the IDE, we now have a new search for just the items in Solution Explorer.  You can quickly type in a file, class, reference, etc… and see a filtered list in Solution Explorer of the items you are looking for.

     

    Collapse All

    A long-awaited feature that will collapse everything in Solution Explorer so you can expand items “fresh” as you navigate though the various hierarchies. 

     

    Tab Well Enhancements

    Pin Tabs

    Another feature introduced in the Productivity Power Tools, this feature will let you keep interesting tabs surfaced on the left of the tab well while non-pinned tabs get pushed out of the visible area based on usage.

     

    Floating Tab Wells

    You can now rip off documents from the IDE and have multiple tabs grouped together in one or more floating tab wells.  This is great for multi-monitor situations where you want groups of related files on separate monitors.

     

    Search Toolbox

    There is now a dedicated search box for the Toolbox window so you can quickly filter items to find the controls you want.

     

    Add Reference Dialog

    The most notable change to the Add Reference dialog is speed.  It is way, waaaaay faster to add a reference with the new dialog than ever before.  Also, a search box has been added to allow quick filtering of assemblies.

     

    Streamlined Quick Find / Replace

    The Quick Find / Replace has been cleaned up and streamlined to make using the experience easier overall.

     

    Error List Window Enhancements

    Search Errors

    As with many other tool windows, the Error List window now sports a search box you can use to filter the list of errors, warnings, and information messages.

     

    Scope Filter

    The Error List window also now supports a scope filter that lets you show only those items in Open Documents, the Current Project, or the Current Document.

     

    Preview Tab

    Probably one of the coolest new changes is the Preview Tab.  Essentially it allows you to look at a preview of a file and decide if you want that file to be opened up in the tab well.  I’ll show much more on this feature later but wanted to mention it here to round out the list of items I will be covering in the short-term.

     

    Finally

    There are a lot of very cool changes coming in Visual Studio vNext.  This post is meant to make you aware of the coming changes at a high-level to prepare you for a deeper discussion of each of these features in future posts.

  • The Ultimate Visual Studio Tips and Tricks Blog

    Visual Studio vNext Performance Enhancements

    • 13 Comments

    Continuing on our odyssey of exploring the features in vNext, I thought we would look at some of the performance enhancements that have been publicly announced.  Naturally, at this time, I can’t go very deep into the inner-workings of the improvements but will endeavor to list them out and explain somewhat based on information currently available.  Also, be aware that this is a very early look at these features so there will be many improvements made as the product gets closer to RTM.  I’m actually running two versions of vNext currently; the one that will be made available to the public as a pre-release at some point and the one we build internally so I have a pretty good handle on what you will see and what is coming out.  I can say that there are some great things that are being done with the product you will definitely enjoy.  With that said let’s take a look at some of the things we have revealed so far…

     

    Microsoft Visual Studio IDE Futures

    First off, if you haven’t seen it yet, most everything I mention comes from the great TechEd session done by Weston Hutchins that can be found here:

    http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DEV326

     

     

    Performance: The Four Pillars

    For vNext we are focused on four areas of investment to improve the product:

    1. Overall Responsiveness
    2. Long Running Operations
    3. Memory Utilization
    4. Better Feedback

     

    Overall Responsiveness

    As I review the areas of improvement expect a great deal of overlap as many of the improvements fall into multiple categories.  With that said, this area is pretty self-explanatory:  We want vNext to enable users to quickly go about their work without waiting on the IDE.  These improvements manifest themselves in a variety of ways but all have the singular goal of making the product more responsive.  Below are some of the areas that address this goal that we have made public so far.

     

    Faster, Stronger, Better Add Reference Dialog

    One of the IDE enhancements revealed so far is Add Reference dialog box.  First and foremost it has been supercharged to load almost instantaneously.  How?  We index the assemblies beforehand to have a ready-made list on demand.  We haven’t gone into detail yet on what exactly is being done but expect that revelation in due course.  Also, as with most of the IDE, we have added the ability to search/filter the list so you don’t spend a billion years looking for the assembly you want.

     

    Out-of-Process Operations

    We have moved some activities out-of-process to give control back to the IDE quickly.  See Memory Utilization.

     

    Parallel Operations

    vNext will take advantage of multi-core systems much better than VS2010 which will result in more overall responsiveness.  See Long Running Operations.

     

     

    Long Running Operations

    Building and debugging are examples of a long-running operations that we are addressing.  For example, Visual Studio 2010, while a great improvement over previous versions, really doesn’t take full advantage of multi-processor machines.  Our goal is to speed things up so you can get your work done faster with less time spent waiting.

     

    Background Builds

    Build operations have now been moved to background threads so you can actually do other things in Visual Studio while a build is happening.

     

    Parallel Project Builds

    Another great new feature is the ability to build projects in parallel.  vNext comes with an option to have parallel project builds based on the number of cores your system has.  In fact, the default value is automatically set to the max cores on your system.  You can reduce this value if you want.

     

     

    Memory Utilization

    Responsiveness also includes the overall efficiency of Visual Studio.  We are working on reducing the memory utilization overall based on usage. 

     

    Virtual Memory Utilization

    vNext uses much less virtual memory internally.  Much of this is due to running builds out-of-process (see below) as well as other enhancements we have made that haven’t been released yet.

     

    Out-Of-Process Builds (C++, C#)

    C++ has had this feature for a while and we are now brining it to C# and, in a future release sometime after vNext, VB as well.  We now perform builds outside the Visual Studio process.  Instead of loading numerous referenced assemblies inside the VS process they are now loaded into an external process then discarded when we are done.  This results in significantly less memory usage inside Visual Studio which results in a more responsive, stable product.

     

     

    Better Feedback

    This one is really simple.  How do we get the best information possible when there are issues with the product so we can continuously improve it for you?  Solving for this question is never easy but we have devised ways of obtaining performance data from your actual use of the product to help strengthen our knowledge of areas that need to be addressed.

     

    PerfWatson, PerfWatson, PerWatson

    The number one tool you can download TODAY to give us feedback on VS2010 and vNext is PerfWatson.  You can get it from the Visual Studio Gallery here:

    http://visualstudiogallery.msdn.microsoft.com/fa85b17d-3df2-49b1-bee6-71527ffef441

    This tool allows us to get up-to-date, immediate information on the issues that are impacting performance.  This tool is currently built into the pre-release version of vNext and, I suspect, we will include it in the RTM version as well with an option for you to turn it off if you don’t want it.

     

    Visual Studio Feedback on Connect

    If you haven’t gone to http://connect.microsoft.com/VisualStudio/ yet then you need to.  This is one of the main ways we have been getting directed feedback from you for some time now.  It’s a great way to get to see what others are saying and to communicate directly with the VS team.

  • The Ultimate Visual Studio Tips and Tricks Blog

    Visual Studio 2013: TODO Comments and Custom Tokens in the Task List

    • 13 Comments

    NOTE: This is an older feature I’ve updated the information for VS2013

     

    Ever been writing some code and you want to leave a reminder to yourself to do something on a particular line or area?  Did you know about the "to do" comment feature or custom tokens?  They seriously rock if you have never used them and, because they go in source code, everyone can have access to the information when you check-in the code!

     

     

    TODO Comments

    So here's how TODO comments work: 

     

    VB

    In VB you just put any comment in that begins with the letters "todo" (case doesn't matter):

    5-16-2012 12-13-33 PM

     

     

    C# and C++

    In C# and C++, it's pretty much the same thing (again, case doesn't matter):

    5-16-2012 12-17-39 PM

     

     

    In C++ you have to explicitly turn this feature on.  Go to Tools | Options | Text Editor | C/C++ | View and change Enumerate Comment Tasks to True:

    5-16-2012 12-19-14 PM

     

     

    Regardless which language you use the result is an entry in your Task List:

    5-16-2012 12-22-52 PM

    Note: You can Double Click any entry to automatically have the editor go to the respective line in your source.

     

     

    If you don’t see the entries, make sure you have set the task list to see comments:

    5-16-2012 12-24-46 PM

     

     

     

    Custom Tokens

    We actually have several tokens you can use in addition to TODO. To see all the existing tokens go to Tools | Options | Environment | Task List:

    5-16-2012 12-28-08 PM

     

     

    HACK and UNDONE

    You are welcome to use HACK and UNDONE as well. The MSDN documentation is horrifically bad when it comes to describing these tokens and I don’t agree with the description of use necessarily. Here is what it says:

    “Items labeled TODO, HACK, and UNDONE in the Task List window indicate code problems that do not keep the project from compiling, but that do cause run-time errors. You should correct these errors before running the project.”

    http://msdn.microsoft.com/en-us/library/aa652344(v=VS.71).aspx

     

    Also, be aware that the number of entries that appear in the Task List changes depending on the type of project you are working on. With VB and C# projects, the Task List displays all of the comments in the project whether the file is open or not. With C++ projects, the Task List displays only the comments that are found in the files currently opened for edit.

     

     

    Creating Custom Tokens

    Feel free to create your own tokens for your use. Creating your own tokens is very simple, just pick a name for your token and type it in the Name textbox:

    5-16-2012 1-07-32 PM

    Note: UnresolvedMergeConflict looks like an error but isn’t it is an actual token that will make a high priority item in the Task List.

     

     

    Next choose a priority level:

    5-16-2012 1-09-02 PM

     

     

    Then click the Add button to make it an active token:

    5-16-2012 1-10-32 PM

     

     

    You will see it in your list:

    5-16-2012 1-11-42 PM

     

     

    Now you can use the token in your comments:

    5-16-2012 1-14-01 PM

     

     

    Sharing Custom Tokens

    Be aware that any tokens you create ARE NOT SHARED with other developers so you may want to come up with a standard set of tokens for everyone to use if you intend to leverage this feature company-wide then export them (http://blogs.msdn.com/b/zainnab/archive/2010/07/14/exporting-your-environment-settings-vstipenv0021.aspx) and have folks import them (http://blogs.msdn.com/b/zainnab/archive/2010/07/15/importing-or-changing-your-environment-settings-vstipenv0022.aspx).

     

     

     

    Finally

    Tokens are a pretty nice feature to keep track of places in your code you need to revisit. I don’t suggest them over, say, tasks in Team Foundation Server but they are a great short-term reminder for things that need to get attention. If you decide you would like to create Task List items programmatically you can do that as well. Here is a link to some guidance to get you started:

    http://msdn.microsoft.com/en-US/library/envdte.tasklist.defaultcommenttoken(v=vs.80).aspx

  • The Ultimate Visual Studio Tips and Tricks Blog

    Keyboard Shortcuts for the Book

    • 12 Comments

     

    Folks,

     

    We just had a meeting the other day and are getting closer to the final draft for the book.  The piece I am most concerned about is how best to convey keyboard shortcut information so it is easy for you to use.  Here is the table structure we were originally thinking:

    image

     

    Notice the actions are on the left and keyboard settings are along the top.  During the discussion I thought it would be more logical to put the keyboard settings along the left and the actions across the top.  My thinking is that when you use the table you will start with your setting and then want to move right along actions you can take.  What do YOU think?  Do you like it the way it is or with the settings and actions switched?

  • The Ultimate Visual Studio Tips and Tricks Blog

    The Immediate Window: Working with Members

    • 12 Comments

    Keyboard:  CTRL + ALT + I
    Menu:  Debug -> Windows -> Immediate
    Command:  Debug.Immediate
    Versions:  2008,2010
    Published:  9/28/2010
    Code:  vstipTool0095

     

    When using with the Immediate Window, you can work with class and object members directly:

     

    Debug

    You can use any method or property as long as it is in context.  So, for example, when you are in debug mode, you can call any method that is in scope:

    image

     

     

    Design

    A less-known feature is you can work with properties and methods while in design mode.  If you have static methods on a class, for example, you can just execute them right away:

    image

     

     

    For object members, obviously, you need to create an instance of the object before working with the members:

    image

     

    WARNING:  When working with members at design-time a build will occur.  This could have unintended consequences so make sure you have experimented with this feature a bit before you use it.

Page 4 of 135 (1,345 items) «23456»