ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Dot​Net​Comments

by juzzbott ALL

Visual Studio style XML comments in Sublime Text

Labels comments

Details

Installs

  • Total 2K
  • Win 1K
  • Mac 270
  • Linux 197
Jul 5 Jul 4 Jul 3 Jul 2 Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

DotNetComments

DotNetComments is a plugin for Sublime Text 3 that replicates the commenting functionality of Visual Studio.

To use the plugin, type '///' and the plugin with automatically determine the type of comment block to generate based on the next line of code. The plugin will ignore [Attributes] so that is able to correctly determine the comment type.

Once the comment block has been generated, the cursor is automatically shifted to the entry section for the <summary> so that typing is unimpeeded.

Supported comment types

The plugin can support the following comment types: * Properties and fields * Classes, interfaces and enumerations * Contstructors * Methods (both with and without return values) * Generic TypeParam methods ()

Examples

Property comment block:

/// <summary>
/// 
/// </summary>
private int _someValue { get; set; }

Generic method with return value:

/// <summary>
/// 
/// </summary>
/// <typeparam name="T"></typeparam>
/// <param name="objectId"></param>
/// <param name="count"></param>
/// <returns></returns>
public static T GetObject<T>(string objectId, int count)
{
}

Supported versions

So far, this has only been tested on Sublime Text 3, as it's designed to work along side plugins like OmniSharp. When I get a chance, I'll test this on Sublime Text 2.