Downloads of v 0.12.0:


Last Update:

01 Dec 2014

Package Maintainer(s):

Software Author(s):

  • EditorConfig Team


development editor IDE coding-style

EditorConfig Core

This is not the latest version of EditorConfig Core available.

0.12.0 | Updated: 01 Dec 2014



Downloads of v 0.12.0:



Software Author(s):

  • EditorConfig Team

EditorConfig Core 0.12.0

This is not the latest version of EditorConfig Core available.

All Checks are Unknown

2 Test of Unknown Status

Validation Testing Unknown

Verification Testing Unknown

To install EditorConfig Core, run the following command from the command line or from PowerShell:


To upgrade EditorConfig Core, run the following command from the command line or from PowerShell:


To uninstall EditorConfig Core, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade editorconfig.core -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade editorconfig.core -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure editorconfig.core installed
    name: editorconfig.core
    state: present
    version: 0.12.0
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'editorconfig.core' do
  action    :install
  version  '0.12.0'
  source   'STEP 3 URL'

See docs at

    Name: editorconfig.core,
    Version: 0.12.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller editorconfig.core
   Name     = 'editorconfig.core'
   Ensure   = 'Present'
   Version  = '0.12.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'editorconfig.core':
  provider => 'chocolatey',
  ensure   => '0.12.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install editorconfig.core version="0.12.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 07 Dec 2014.


EditorConfig helps developers define and maintain consistent coding styles between different editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readibly and they work nicely with version control systems. This package installs the editorconfig command line tooling written in .NET.

<?xml version="1.0" encoding="utf-8"?>
		<add key="version" value=""/>
		<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
<?xml version="1.0"?>
        <member name="T:Minimatch.Options">
            <summary>Contains options that control how Minimatch matches strings.</summary>
        <member name="P:Minimatch.Options.NoComment">
            <summary>Suppresses the behavior of treating # at the start of a pattern as a comment.</summary>
        <member name="P:Minimatch.Options.NoNegate">
            <summary>Suppresses the behavior of treating a leading ! character as negation.</summary>
        <member name="P:Minimatch.Options.NoBrace">
            <summary>Do not expand {a,b} and {1.3} brace sets.</summary>
        <member name="P:Minimatch.Options.NoGlobStar">
            <summary>Disable ** matching against multiple folder names.</summary>
        <member name="P:Minimatch.Options.NoCase">
            <summary>Ignores case differences when matching.</summary>
        <member name="P:Minimatch.Options.NoExt">
            <summary>Disable "extglob" style patterns like <c>+(a|b)</c>.</summary>
        <member name="P:Minimatch.Options.Dot">
            <summary>Allow patterns to match filenames starting with a period, even if the pattern does not explicitly have a period in that spot.
            Note that by default, <c>a/**/b</c>  will not match <c>a/.d/b</c>, unless dot is set.</summary>
        <member name="P:Minimatch.Options.NoNull">
            <summary>When a match is not found by Match(), return a list containing the pattern itself. If not set, an empty list is returned if there are no matches.</summary>
        <member name="P:Minimatch.Options.FlipNegate">
            <summary>Returns from negate expressions the same as if they were not negated. (ie, true on a hit, false on a miss).</summary>
        <member name="P:Minimatch.Options.MatchBase">
            <summary>If set, then patterns without slashes will be matched against the basename of the path if it contains slashes. For example, <c>a?b</c> would match the path <c>/xyz/123/acb</c>, but not <c>/xyz/acb/123</c>.</summary>
        <member name="P:Minimatch.Options.AllowWindowsPaths">
            <summary>If true, backslahes in patterns and paths will be treated as forward slashes.  This disables escape characters.</summary>
        <member name="P:Minimatch.Options.IgnoreCase">
            <summary>Ignores case differences when matching.  This is the same as NoCase.</summary>
        <member name="T:Minimatch.Minimatcher">
            <summary>Parses a single glob pattern and tests strings against it.</summary>
        <member name="M:Minimatch.Minimatcher.CreateFilter(System.String,Minimatch.Options)">
            <summary>Creates a filter function that tests input against a pattern.</summary>
        <member name="M:Minimatch.Minimatcher.Check(System.String,System.String,Minimatch.Options)">
            <summary>Tests a single input against a pattern.</summary>
            <remarks>This function reparses this input on each invocation.  For performance, avoid this function and reuse a Minimatcher instance instead.</remarks>
        <member name="M:Minimatch.Minimatcher.Filter(System.Collections.Generic.IEnumerable{System.String},System.String,Minimatch.Options)">
            <summary>Filters a list of inputs against a single pattern.</summary>
            <remarks>This function reparses this input on each invocation.  For performance, avoid this function and reuse a Minimatcher instance instead.</remarks>
        <member name="M:Minimatch.Minimatcher.CreateRegex(System.String,Minimatch.Options)">
            <summary>Compiles a pattern into a single regular expression.</summary>
        <member name="M:Minimatch.Minimatcher.#ctor(System.String,Minimatch.Options)">
            <summary>Creates a new Minimatcher instance, parsing the pattern into a regex.</summary>
        <member name="M:Minimatch.Minimatcher.IsMatch(System.String)">
            <summary>Checks whether a given string matches this pattern.</summary>
        <member name="M:Minimatch.Minimatcher.Filter(System.Collections.Generic.IEnumerable{System.String})">
            <summary>Filters a list of inputs against this pattern.</summary>
        <member name="M:Minimatch.Minimatcher.BraceExpand(System.String,Minimatch.Options)">
            <summary>Expands all brace ranges in a pattern, returning a sequence containing every possible combination.</summary>

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
EditorConfig Core 0.12.0 484 Monday, December 1, 2014 Approved
EditorConfig Core 591 Monday, May 20, 2013 Approved
EditorConfig Core 373 Thursday, March 14, 2013 Approved
EditorConfig Core 443 Sunday, July 1, 2012 Approved

This package has no dependencies.

Discussion for the EditorConfig Core Package

Ground Rules:

  • This discussion is only about EditorConfig Core and the EditorConfig Core package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or EditorConfig Core, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus