Blog - Title

Visual Studio 2013 Current Status

  • The Ultimate Visual Studio Tips and Tricks Blog

    .NET Framework 4.5 Poster from the Community

    • 0 Comments

    image

     

    I’ve had a lot of people asking about our famous .NET poster and if there is a version for 4.5 yet.  The answer, to my knowledge, is “no”.  However there IS a really good poster created by Jouni Heikniemi that you can find here:

    http://www.heikniemi.net/hardcoded/2011/10/whats-new-in-net-framework-4-5-poster/

     

    Grab it and see if you like it as much as I do Smile

  • The Ultimate Visual Studio Tips and Tricks Blog

    IntelliTrace Debugging Deep Dive Session is Available for Download

    • 0 Comments

    image

     

    Folks, apologies for going dark for a few weeks but I have been heads down in the creation of some new IntelliTrace content.  I’ve put together a set of labs and slide decks that you can use to train yourself and/or train others on how to use this to full advantage.  You can find the entire package here:

    http://sdrv.ms/UPUEE3

     

    The contents are built on top of Brian Keller’s amazing work with his virtual machine and labs that can be found here:

    http://blogs.msdn.com/b/briankel/archive/2011/09/16/visual-studio-11-application-lifecycle-management-virtual-machine-and-hands-on-labs-demo-scripts.aspx

     

    Here is a quick look at the contents:

    Presentation Materials

    · Slide Deck for presenting at an event

    · Titles and Abstracts for informing others about the event

    · Demo Quick Snippets for use when presenting to cut down on the demonstration time if needed

    You can (and should) modify the materials to suit your needs. For example, to put on the one hour version of this session you would need to cut out several slides from the original deck. Feel free to modify as needed for your organization.

     

     

    IntelliTrace Labs

    · Lab Manual for demonstration or instructor-led lab sessions

    · Any supplemental material required to complete the labs including project files

     

    Contents of the Lab Manual

    Introduction

    Lab 1: IntelliTrace Events

    Lab 2: IntelliTrace with Call Information

    Lab 3: Creating Log Files

    Lab 4: IntelliTrace CAB

    Lab 5: Collection Plans

    Lab 6: IntelliTrace Everywhere with ASP.NET

    Lab 7: Debugging with IntelliTrace Files

    Lab 8: IntelliTrace Everywhere with Other .NET Applications

    Lab 9: IntelliTrace Everywhere with Microsoft Test Manager

    Lab 10: Configuring Symbols

    Lab 11: Using Symbols

    Conclusion

     

     

    Toolbox

    · Collection Plans folder with sample collection plans for use with Visual Studio or IntelliTrace Everywhere as indicated by the folder name

    · IntelliTrace Everywhere Best Practices document that has a summary of the best practices mentioned in the labs and slide deck

    · IntelliTrace configuration tool obtained from
    http://intellitracecpconfig.codeplex.com/
    Included in these materials with permission from the tool’s author, Vlatko Ivanovski

  • The Ultimate Visual Studio Tips and Tricks Blog

    TFS 2010: What Service Packs and Hotfixes Should I Install?

    • 0 Comments

    Grant Holliday wrote a great blog post a while back that I have been meaning to surface to my readers for some time.  If you haven’t seen it yet, you can find it here:

    http://blogs.msdn.com/b/granth/archive/2012/01/03/tfs-2010-what-service-packs-and-hotfixes-should-i-install.aspx

     

    Here is the opening paragraph from the post that lays out what Gran is trying to do:

    ===

    Team Foundation Server 2010 was released in April 2010. Since then, there have been a number of important Service Packs, Cumulative Updates and hotfixes that have been made available based upon internal usage at Microsoft and customer feedback via the support organisation. This blog post is an attempt at bringing together all the updates that are currently available.

    ===

     

    He is keeping it updated consistently and you should definitely read this post if you use TFS 2010.

  • The Ultimate Visual Studio Tips and Tricks Blog

    Microsoft Positioned as Leader in Application Lifecycle Management Space

    • 0 Comments

    Gartner doesn’t allow us to show the famed Magic Quadrant in posts like this but, if you are into these kinds of things, definitely check out how much butt we kicked in this article from them:

    http://www.gartner.com/technology/reprints.do?id=1-1ASCXON&ct=120606&st=sb

  • The Ultimate Visual Studio Tips and Tricks Blog

    Why Smart People Are Stupid

    • 0 Comments

     

    Jonah Lehrer the author of “How We Decide” has written an article for the New Yorker showing how people take mental shortcuts to arrive at wrong answers.  Most surprisingly was the finding that more intelligent people make this mistake more often than others.  You can read the entire article here:

    http://www.newyorker.com/online/blogs/frontal-cortex/2012/06/daniel-kahneman-bias-studies.html#ixzz1xgvsJzj5

    Also, if you haven’t read “How We Decide” and are interested in a nice high-level look at the cognitive decision-making process then you should absolutely read this book:

    http://www.amazon.com/How-We-Decide-Jonah-Lehrer/dp/0547247990

  • The Ultimate Visual Studio Tips and Tricks Blog

    On Vacation Until 8/6

    • 0 Comments

     

     

    Folks,

    I'll be on vacation until Aug 6th so there will be no posts until the week after I get back.  We will resume our regularly scheduled posts at that point :)

     

    Z

  • The Ultimate Visual Studio Tips and Tricks Blog

    Visual Studio 11 Developer Preview: Code Clone Detection (aka Code Clone Analysis)

    • 0 Comments

    [NOTE: This post has been depricated, you can find the updated post here:

    http://blogs.msdn.com/b/zainnab/archive/2012/06/28/visual-studio-2012-new-features-code-clone-analysis.aspx]

     

     

    Versions: Visual Studio 11 Developer Preview

     

    Make sure to get your copy of the new book from Sara and me:

    Coding Faster: Getting More Productive with Microsoft Visual Studio

     

     

    <Disclaimer>

    Note: As always with pre-release software, some of the features may not make it into the final version or may change significantly before RTM. Also, although I will only show features that are publicly available, I may be using a slightly older or newer version of the build than you are so there may be slight differences in the feature set I show and the feature set you currently have.

    </Disclaimer>

     

     

    In my travels across the country, with my fellow Evangelist, Clint Edmonson, talking about Visual Studio we often come across great stories to tell. One of our favorite true stories is of a customer that had a web application running very slow. We ran code metrics against it and, sure enough, the Page_Load event had 9,000 lines of code in it. Naturally we were curious so we opened it up to see that it was basically the same if statement copied over and over. Apparently they needed to find out who was coming into the website in order to show customized content and the solution they came up with was this massive set of statements.

     

    For better or worse we have all had code that gets copied throughout our solutions. Until now there was no tool to tell us there were copies and, instead, we had to rely on other metrics such as lines of code to hopefully reveal any code smells. Now, however, we have the new Code Clone Detection (aka Code Clone Analysis) feature.

     

    According to the documentation:

    Code clones are separate fragments of code that are very similar. They are a common phenomenon in an application that has been under development for some time. Clones make it hard to change your application because you have to find and update more than one fragment. Visual Studio can help you find code clones so that you can refactor them.”

    http://msdn.microsoft.com/en-us/library/hh205279%28v=vs.110%29.aspx

     

     

    Specific Clones

    You can find clones of specific code by selecting the segment you are interested in:

    image

     

    Then Right-click on the selection and choose Find Matching Clones in Solution from the context menu:

    image

     

    Visual Studio will search for code clones and produce the result in the new Code Clone Search Results window:

    image

     

    The original line of code is put in a group on its own and then all the matches are put into a different group. You can expand the groups to see the specific locations of the matches:

    image

     

     

     

    Solution Clones

    Besides looking for specific clones you can also just look for code clones for the entire solution. This will search the entire solution for duplicate code and display the results. To use this feature go to Analyze | Analyze Solution for Code Clones:

    image

     

    This creates a result set for the entire solution:

    image

     

    By default it groups and sorts the results by the strength of the match. Exact matches come first then those matches that may be close but not exact come next. As you can see the other terms used are Strong, Medium, and Weak in this example.

     

     

     

    Reviewing Matches

    Once you have the result set, there are a couple of ways you can compare them against each other.

     

    Comparison Tools

    Although I don’t show it here, if you have a comparison tool configured you can Right-click on any two items and select Compare from the shortcut menu. You would know if you have this feature available by going to Tools | Options | Source Control | Team Foundation Server and click on Configure User Tools.

     

     

    Manual Comparison

    If you don’t have a comparison tool you can do manual comparisons between two entries in the list. If the clones are in different files then you can just double-click each one and file tabs will be available for you to look at for comparison:

    image

     

     

    When it comes to comparisons in the same file I’ve only found one good way to accomplish this so far. Granted, I have just started playing with this feature so there might be something coming or something I missed that makes this easier. Here is a series of steps to compare two items in the same file.

     

    First, find the first entry you want to look at and double-click on it to open a file tab and highlight the code segment:

    image

     

    Now make a copy of the current code window by going to Window | New Window:

    image

     

    Next, go to the second entry you are interested in and double-click it. The result should be one code segment on each tab so you can compare the two:

    image

     

    You can do this for as many entries in the list as you like. Just repeat these steps for each entry you want to compare.

     

     

     

    What Is Found

    You are probably curious as to what is found by this tool. The heuristics for finding clones will find duplicates even if the following changes have happened:

    · Renamed identifiers.

    · Insert and delete statements added.

    · Rearranged statements.

     

     

     

    What Is Not Found

    There are some rules for what is not found as well. I have taken this list from the documentation pretty much verbatim.

    · Type declarations are not compared. For example, if you have two classes with very similar sets of field declarations, they will not be reported as clones. Only statements in methods and property definitions are compared.

    · Analyze Solution for Code Clones will not find clones that are less than 10 statements long. However, you can apply Find matching clones in solution to shorter fragments.

    · Fragments with more than 40% changed tokens.

    · If a project contains a .codeclonesettings file, code elements that are defined in that project will not be searched if they are named in the Exclusions section of the .codeclonesettings file.

    · Some kinds of generated code are excluded:

    · *.designer.cs, *.designer.vb

    · InitializeComponent methods

    · However, this does not automatically apply to all generated code. For example, if you use text templates, you might want to exclude the generated files by naming them in a .codeclonesettings file.

     

     

     

    Code Clone Settings and Exclusions

    A settings file is available to configure this feature at the project level. I tried to use it at the solution level but it didn’t work so this is definitely a per-project activity. Currently we have only announced the ability to do exclusions in the file but there will most likely be other elements that are added later on. The file is just XML with a .CODECLONESETTINGS extension. The only requirement for use is that the file exists in the top level directory of the project.

     

    The base elements consist of a CodeCloneSettings element with an Exclusions child:

    image

     

    Within the Exclusions element you can have the following children:

    <File>

    This element is used to indicate files that should be excluded from analysis. Path names can be absolute or relative and you can use wildcards as well. So, for example, to ignore all the C# text template files that have been put in their own directory (called MyTextTemplates) you might have the following:

    image

     

     

    <Namespace>, <Type>, and <FunctionName>

    You can also exclude namespaces, types, and functions. Just like files these items can use absolute names or names with wildcards in them. Here is an example of what it might look like:

    image

     

    Example Scenario

    In the Tailspin Toys sample that I have there is some generated code in the TailSpin.SimpleSqlRepository project that is the bulk of the duplications:

    image

     

    Code clone analysis doesn’t automatically know to ignore text templates so I have created an XML file called TailSpinRepository.codeclonesettings and inserted an entry like this:

    image

     

    Now if I run clone analysis here is the result:

    image

     

    As you can see the results are significantly less than the first time the analysis ran. It’s common to create several exclusions in different projects to weed out noise in the analysis results.

     

     

     

    Finally

    Code Clone Detection is a great new tool to add to your arsenal for improving code quality. Combined with Code Analysis and Code Metrics, this will help quickly find potential issues.

  • The Ultimate Visual Studio Tips and Tricks Blog

    Surround with a Code Snippet (C# Only)

    • 0 Comments

    Keyboard:  CTRL + K, CTRL + S
    Menu:  Edit | IntelliSense | Surround With
    Command:  Edit.SurroundWith
    Versions:  2008,2010
    Published:  4/21/2010
    Code:  vstipEdit0052

     

     

    This is one that even people who know about snippets tend to forget.  You can actually put a snippet AROUND existing code.  Assuming you have some code selected:

    clip_image002

     

    Just press CTRL + K, CTRL + S:

    clip_image004

     

    Then type the statement you want to surround the code with.  In this case, I’ll use an “if” statement:

    clip_image006

     

    Hit your TAB key once and you get your result:

    clip_image008

     

    Now you can put in your condition and any additional logic you want.  Pretty cool stuff!

  • The Ultimate Visual Studio Tips and Tricks Blog

    Chaotic Moon’s Board of Awesomeness: Kinect Is Your Friend

    • 0 Comments

    xbox-kinect-skateboard[1]

     

    What's red, goes 32MPH, and is controlled by a wave of your hand? 

     

    It's the Chaotic Moon Labs "Board of Awesomeness"!!

     

    My good friend, Phil Wheat, works over there and he has been working on this most excellent device.  If you've been following CES, you've probably seen their Kinect controlled, powered longboard all over the place but some things you might not know about it is that it's all programmed in C# on Visual Studio 2010

     

    The board is made up of a number of hardware components, but the main parts are the Kinect Beta 2 SDK and a Phidgets analog out board.  Visual Studio was the key to tying these systems together and making the project take weeks, not months to put together.  Even more awesome, is that with the Visual Studio debugger and refactoring tools, as tests showed improvements that could be made - changes could be made in the field, on the fly and tested without having to go back into the lab to rework the code.

     

  • The Ultimate Visual Studio Tips and Tricks Blog

    Visual Studio 11 Beta arrives on February 29, 2012

    • 0 Comments

     

    In case you haven’t heard, Visual Studio 11 Beta will be available on the 29th.  I’ll post more information once it pops but wanted to get everyone pointed to a few resources to tide you over Smile

    The Road to Visual Studio 11 Beta and .NET Framework 4.5 Beta

    Blog

    Sneak Preview of Visual Studio 11 and .NET Framework 4.5 Beta

     Blog

    Coming Soon: Team Foundation Server Express

     Blog

    Introducing the New Developer Experience – Part 1

     Blog

    Link to learn more about Visual Studio 11 Beta

    Visual Studio 11 Home Page

    Link to learn more about Visual Studio 11 Beta

    What's New in Visual Studio 11

    Link to learn more about Visual Studio 11 Beta Go Live

    Visual Studio 11 Beta Go Live

Page 131 of 135 (1,345 items) «129130131132133»