Skip to content

Releases: editorconfig/editorconfig-core-net

0.15.0

24 Nov 10:23
295f0af
Compare
Choose a tag to compare

0.14.0

02 Jun 12:44
b3e00ba
Compare
Choose a tag to compare

0.13.0

02 Jun 12:18
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.12.2...0.13.0

0.12.2: quite wildcard nupkg reference so the nuget tooling does the wildcard…

14 Jul 16:22
Compare
Choose a tag to compare

0.12.1...0.12.2

New Features

  • #6 Remake glob matcher (minimatcher) to significantly improve performance
  • #9 [netstandard] Migrated EditorConfig.Core project to support multiple … (issue: #2)
  • #10 Change ParseFile to an overload to Parse and make it public
  • #11 Update build to make it easier to release

View the full list of issues and PRs

0.12.1

13 Feb 15:07
Compare
Choose a tag to compare

Added proper aspnetcore50 and net45 builds.

First release

02 Dec 12:32
Compare
Choose a tag to compare

This is the first release of the .net port of editorconfig core:

The .NET port was necessary in order for crossplatform .NET code to take advantage of editorconfig files without having to link against different c libraries for different platforms.

command line

https://chocolatey.org/packages/editorconfig.core (still pending approval of 0.12.0)

The chocolatey package now uses the .net port of the cli tooling.

library

http://www.nuget.org/packages/editorconfig/

Provides strongly typed access to your editorconfig configuration for files. See the README for more information.

The nuget package is intended for when you want to embed support for reading editorconfig files i.e: editor extensions (visual studio/xamarin/others).

future work

  • moving the visual studio extension to the .NET library, this will make it easier to compile without requiring CMAKE.
  • Looking to add support for editorconfig inside http://github.com/omnisharp so that refactorings take .editorconfig files into account and to use .editorconfig domain properties to configure omnisharp itself