Visual StudioVisual Studio tools

Code Lens

Code lens is a simple way to know what happens with the code. Here you could find an image with the number of references of a method or class.

Code lens

If you can't see the code lens please see this question: Missing CodeLens references count in VS 2015 Community edition

Snippets

Intoduction

Since Visual Studio 2005 can you make Intellisense Code Snippets. This allow you to generate some code just by typing one keyword and press two times the tab key.

Using the code

The XML code you need for make an Intellisense Code Snippet stands below:

<?xml version="1.0" encoding="utf-8"?>

<CodeSnippets xmlns="http://schemas.microsoft.com/VisualStudio/CodeSnippet">
  <CodeSnippet Format="1.0.0"> <!-- format attribute is required -->

    <Header> <!-- 1 -->
      <Title></Title>
      <Author></Author>
      <Shortcut></Shortcut>
      <Description></Description>
      <Keywords>
        <Keyword>abc<Keyword>
        <Keyword>def<Keyword>
      </keywords>
    </Header>

    <Snippet> <!-- 2 -->

      <Imports> <!-- 2.1 -->
        <Import>
          <Namespace>System</Namespace>
        </Import>
      </Imports>

      <Declarations> <!-- 2.2 -->
        <Literal Editable="true/false"> <!-- 2.2.1 -->
          <ID>example</ID>
          <Type>System.String</Type>
          <ToolTip>A tip you can show</ToolTip>
          <Default>default value</Default>
          <Function></Function> <!-- 2.2.2 -->
        </Literal>

        <Object> <!-- 2.2.1 -->
          <ID>example</ID>
          <Type>System.String</Type>
          <ToolTip>A tip you can show</ToolTip>
          <Default>default value</Default>
          <Function></Function> <!-- 2.2.2 -->
        </Object>
      </Declarations>

      <References> <!-- 2.3 -->
        <Reference>
          <Assembly>System.Data.dll</Assembly>
        </Reference>
      </References>

      <Code Language=""> <!-- 2.4 -->
        <![CDATA[
            <!-- your code here if you use literals use dollar chars  -->
        ]]>
      </Code>

    </Snippet>

  </CodeSnippet>
</CodeSnippets>

In the snippet tag, you have two required tags named Header and Snippet. You can find more information in next headings. The number near the name are correspondents with the numbers in the code above.

There can be zero or more CodeSnippet elements added into the CodeSnippets element.

1. Header

In the Header-tag, you can place some specific information about the snippet and what he does. The important tags you can use inside this tag are:

ElementDescription
TitleThe title of the snippet. This attribute is required.
AuthorThe author of the snippet.
ShortcutIs the shortcut, you can use for generating the code. Note that this can only contain letters and numbers and must begin with a letter.
Note: Remember also to give the snippet a good and unique name and shortcut. Otherwise, it will give problems when you import the snippet into Visual Studio.
DescriptionGives more information about the snippet if you need that.
HelpUrlA url for a help page on the internet.
KeywordsGroups one or more keyword elements.
SnippetTypes

Groups SnippetType elements. This element contain a text value and must be one of the following values. Snippet types are merged with a forward slash.


  • SurroundsWith: Allows the code snippet to be placed around a selected piece of code.
  • Expansion: Allows the code snippet to be inserted at the cursor.
  • Refactoring: Specifies that the code snippet is used during Visual C# refactoring. Refactoring cannot be used in custom code snippets.
Source list: msdn.microsoft.com

Source table (but edits): msdn.microsoft.com

2. Snippet

In the snippet tag, you can use three different tags. This can be:

  • Imports
  • Declarations
  • Code (required)
  • References

These are explained below.

2.1 Imports

Imports contain the needed namespaces you need for the code. Use the import-tag inside this tag and here you can place the needed namespaces each with the Namespace-tag.

2.2 Declarations

Declarations can be used for declaring some literals or objects into your code in the Code-tag. The children are literals and objects.

2.2.1 Literals and objects

Literals and objects define the literals and objects of the code snippet that you can edit. Functionality are literals and objects are the same, but it has an additional type constraint.

The Literal and object-tag can contain next children:

  • ID: The ID of the literal (required)
  • Type: The type of that object including namespace and class (required by objects)
  • ToolTip: Gives a tip
  • Default: A default value of that object (required)
  • Functions

In the snippets, there are some predefined literals. They are listed below:

LiteralDetails
$end$Marks the location to place the cursor after the code snippet is inserted.
$selected$Represents text selected in the document that is to be inserted into the snippet when it is invoked. Example, If you have:
A $selected$ is an object that I like.
and the word was car selected when you invoked the template, you would get:
A car is an object that I like.
2.2.2 Functions

Functions in the Literal- or Object-tag means that you can use a function for generating code depending on another element. There are three functions that I know:

FunctionDescriptionLanguage
GenerateSwitchCases (EnumerationLiteral)Generates a switch statement and a set of case statements for the members of the enumeration specified by the EnumerationLiteral parameter. The EnumerationLiteral parameter must be either a reference to an enumeration literal or an enumeration type.Visual C# and Visual J#1
ClassName()Returns the name of the class that contains the inserted snippet.Visual C# and Visual J#1
SimpleTypeName(TypeName)Reduces the TypeName parameter to its simplest form in the context in which the snippet was invoked.Visual C#

1 only available in Visual Studio 2005.

Source table: msdn.microsoft.com

Attributes for the Literal and Object Elements

The Literal and Object tags can have some optional attributes.

AttributeDescriptionType
EditableSpecifies whether or not you can edit the literal after the code snippet is inserted. The default value of this attribute is true.Boolean

Source table: msdn.microsoft.com

2.3 References

Groups reference elements that contains information about assembly references for the code snippet. This can contain next elements:

  • Assembly: Contains the name of the assembly by the code snippet (required)
  • Url: Contains a website that gives more information about the assembly

2.4 Code

Code is the code you will generate between <![CDATA[ and ]]>. Place the ID of your literal between dollar chars and Visual Studio will ask you for change these default value if the declarations are filled in. Here, you've an example for C# and VB for the shortcut propfull.

<!-- ... Other code ... -->
<Declarations>
  <Literal>
    <Id>variablename</Id>
    <Default>_myproperty</Default>
  </Literal>

  <Literal>
    <Id>propertytype</Id>
    <Default>int</Default>
  </Literal>

  <Literal>
    <Id>propertyname</Id>
    <Default>myproperty</Default>
  </Literal>
</Declarations>

<Code Language="CSharp">
  <![CDATA[
    private $propertyvalue$ $variablename$;

    public $propertyvalue$ $propertyname$
    {
        get { return $variablename$; }
        set { $Variablename$ = Value; }
    }
  ]]>
</Code>

<!-- ... Other code ... -->

<Declarations>
  <Literal>
    <Id>variablename</Id>
    <Default>_myproperty</Default>
  </Literal>

  <Literal>
    <Id>propertytype</Id>
    <Default>int</Default>
  </Literal>

  <Literal>
    <Id>propertyname</Id>
    <Default>myproperty</Default>
  </Literal> 
</Declarations>

<Code Language="VB">
  <![CDATA[
    Private $variablename$ As $propertyvalue$ 
    
    Public Property $propertyname$ As $propertyvalue$
        Get
            Return $variablename$ 
        End Get

        Set (ByVal value As $propertyvalue$)
            $variablename$ = value
        End Set
    End Property
  ]]>
</Code>

<!-- ... Other code ... -->

In the required Language attribute, you can define your language where you are making the snippet. You can find the languages you can use in the next table.

LanguageKeywordAvailable in next versions
Visual C#CSharp2005, 2010, 2012 and later
Visual BasicVB2005, 2010, 2012 and later
XMLXML2005, 2010, 2012 and later
Visual J#VJSharp2005, 2012 and later
C++CPP2012 and later
JavaScriptJavaScript2012 and later
JScriptJScript2012 and later
SQLSQL2012 and later
HTMLHTML2012 and later
CSSCSS2012 and later
XAMLXAML2012 and later

Other optional attributes are:

AttributeDescription
DelimiterSpecifies the delimiter used to describe literals and objects in the code. By default, the delimiter is $.
KindSpecifies the kind of code that the snippet contains and, therefore, the location at which a code snippet must be inserted for the code snippet to compile.

The valid values for the kind variable are:

ValueDescription
method bodySpecifies that the code snippet is a method body, and therefore, must be inserted inside a method declaration.
method declSpecifies that the code snippet is a method, and therefore, must be inserted inside a class or module.
type declSpecifies that the code snippet is a type, and therefore, must be inserted inside a class, module, or namespace.
fileSpecifies that the snippet is a full code file. These code snippets can be inserted alone into a code file, or inside a namespace.
anySpecifies that the snippet can be inserted anywhere. This tag is used for code snippets that are context-independent, such as comments.

Source tables: msdn.microsoft.com

Import Snippet into Visual Studio

  1. Save the XML code and give it the extension .snippet.

  2. You can add the new made snippet into Visual Studio by pressing Control + K, Control + B or go to "Tools""Code Snippets Manager...". This open next window:

    The Code Snippet manager window

  3. Choose the language into the combo box for which language you've made the snippet. click on "Import..." and choose the file you've made.

    The Import Code Snippet window

  4. Click on "Finish". If the file name already has been used, Visual Studio go ask to override the existing file. You've three options:

    • Overwrite: Overwrites the file. You can use this option if you will edit an old snippet.
    • Rename: Goes to rename the file to an unique name.
    • Skip: Cancels the import. Renames the file to a unique name.

You could also add a new location with all the snippets you've made by clicking on the "Add..." button on the first window and select the folder in the "select folder window". The advantage is now when a new valid snippet is added in that folder, you can use this directly in Visual Studio.

Note: Test after importing your snippet for errors, so you don't have any problems when you use the snippet. You can always remove or overwrite the snippet if there is an error.

Point of intrest

You can also see the documentation on MSDN for more information.

Override merge/compare tools

Got to Tools | Options | Source Control | Visual Studio Team Foundation Server

click on the Configure User Tools:

enter image description here

You can add separate overrides for 'Compare' and 'Merge' operations. Click on Add and select the operation you want to override. You'd need to type the path to the tool you use, and the exact arguments your tool expects. For example to use BeyondCompare, add the following Arguments " %1 %2 /title1=%6 /title2=%7":

enter image description here

To Merge with BeyondCompare use the Arguments "%1 %2 %3 %4 /title1=%6 /title2=%7 /title3=%8 /title4=%9"

In a 2006 blog post MS employee James Manning surveyed the arguments as expected by various tools: WinDiff, DiffDoc, WinMerge, Beyond Compare, KDiff3, Araxis, Compare It!, SourceGear DiffMerge, TortoiseMerge and Visual SlickEdit. The post is a good starting point, but be sure to check the up to date documentation of your tool.

It is highly recommended not to use for merge tools that are incapable of 3-way merges (e.g., WinMerge 2.x).

Entity Framework

Entity Framework (EF) is an object-relational mapper that enables .NET developers to work with relational data using domain-specific objects. It eliminates the need for most of the data-access code that developers usually need to write.

Entity Framework allows you to create a model by writing code or using boxes and lines in the EF Designer. Both of these approaches can be used to target an existing database or create a new database.

Source and more information: Entity Framework documentation