-
Notifications
You must be signed in to change notification settings - Fork 11
Change Log
This change log is for posterity only. Future logging will appear in the standard GitHub releases page. Issue links point back to the old JSLint.NET site on CodePlex.
This version adds support for Visual Studio 2015. Thanks Mads Kristensen!
Features:
- #46: Add support for Visual Studio 2015.
This version resolves intermittent MSBuild failures in certain build environments. Under the hood, the V8 JavaScript engine is now provided by ClearScript.
Bugs:
- #39: Intermittent MSBuild failures.
This version adds support for Node.js Tools projects and streamline.js "._js" files. It also fixes compatibility with C++ projects, in case they happen to include JavaScript files.
Bugs:
- #37: Prevent duplicate warnings when using both VSIX and NuGet.
- #41: Prevent project settings editor merging current configuration into base configuration.
- #42: Prevent project settings editor overwriting writability of predefined globals.
- #43: Correct default writable state for predefined globals.
Bugs:
- #38: MSBuild task support for linked settings file.
- #40: Explicitly typed imports / exports required in some Visual Studio environments.
Features:
- Upgraded JSLint to edition 2014-07-08 (disallows inefficient literal access).
Bugs:
- #26: Fixed regression of project assumption bug in Visual Studio.
Features:
- Upgraded JSLint to edition 2014-04-22 (allows leading semicolon).
Features:
- Upgraded JSLint to edition 2014-04-08.
Features:
- #34: Added support for streamline.js "._js" files.
Bugs:
- #35: Fixed folder scanning for Node.js Tools projects.
- #36: Fixed settings file for C++ projects.
Version 1.5 adds the ability to create JSLintNet.Debug.json and / or JSLintNet.Release.json files and have those settings merged with your core settings. By convention, this is based on the current build configuration in Visual Studio or MSBuild. In fact any custom build configuration names are supported, not only Debug and Release; just make a file to match.
This should make it easier to automatically switch between Warning or Error output or enable / disable JSLint options like the {{debug}} flag in different modes. See the Build Configuration heading on the [JSLint.NET Settings] page for more.
Internally, JSLint has been upgraded to edition 2014-02-06.
Features:
- Added minClientVersion attribute for NuGet 2.8.0. ^^Note: This patch version is only available via NuGet.^^
Features:
- #33: Support for JSLintNet.Debug.json and JSLintNet.Release.json.
- The OutputOverride property on the MSBuild task has been marked as obsolete.
- Upgraded JSLint to edition 2014-02-06.
This version adds support for 64-bit environments, including MSBuild x64. As a result, the packages are all a little larger to accommodate different CPU flavors, with the exception of JSLint.NET for Visual Studio which has had the benefit of some better compression and is actually slightly smaller.
Another addition in this release is the ability to launch the settings editor GUI from the console app. Just pass the full path to the .json file as the first argument, or drag the file onto JSLintNet.Console.exe from Windows explorer to bring it up.
Finally, JSLint.NET for MSBuild has been updated to be more configurable, and now includes the console app to make creating and editing settings easier.
Features:
- Upgraded JSLint to edition 2014-01-26.
- Marked JSLintNet.MSBuild NuGet package as a development only dependency.
Features:
- #23: Added support for 64bit environments.
- #15: Decoupled settings editor from Visual Studio.
- #30: Allowed console app to launch settings editor.
- #31: Allowed source files and directory to be overridden in MSBuild targets.
- #32: Included console app in JSLintNet.MSBuild NuGet package.
Version 1.3.0 adds support for websites in the Visual Studio extension and improves the MSBuild task for the JSLint.NET NuGet package which is now available.
This package adds JSLint.NET MSBuild targets to any project, which will automatically validate JavaScript "Content" files at build time locally and during CI. It understands [JSLintNet.json|JSLint.NET Settings] in the same way as the rest of the JSLint.NET tools.
Internally, JSLint has been upgraded to edition 2013-11-23.
Features:
- #29: Added configurable properties to JSLint.NET for MSBuild NuGet package.
Bugs:
- #28: Visual Studio extension not ignoring files.
Features:
- #27: Added support for website projects in Visual Studio extension.
- #14: Improved MSBuild task so it can be used as a NuGet package.
JSLint edition: 2013-11-23
Version 1.2.0 is primarily focused on improving the Visual Studio experience. Support for the brand spanking new Visual Studio 2013 has been added, there are now more ways to run JSLint from the context menu, and tooltips have been enabled for inline error markers. ,,Note: 1.2.1 and 1.2.2 are stability revisions and do not add new features,,
Get the latest bits at the Visual Studio Gallery, within the Visual Studio extension manager, or over on the releases page.
Bugs:
JSLint edition: 2013-11-21
Bugs:
- #21: Fixed incorrect text marker position error.
Features:
Bugs:
- #4: Fixed tooltips on error markers.
This version contains three significant changes (and lots of little updates). See the releases page for more information and downloads.
Features:
JSLint edition: 2013-09-22
The first stable version of JSLint.NET is now out! This version cleans up a few minor issues and adds some extra menu items to Visual Studio.
Also available from the Visual Studio Gallery or within the Visual Studio extension manager.
Features:
- #16: Ignore files and folders from Visual Studio menu.
Version 0.9.2 of the beta includes many tweaks and and bug fixes. A big thanks to ChrisNielsen for the bug reports, suggestions and pull requests. Please keep them coming.
This version also adds a settings screen for managing JSLint options and JSLint.NET specifics. For now this is available within Visual Studio from a project's context menu.
Features:
- #3: UI for JSLint.NET Settings in VS extension (right click on project).
Bugs:
- #12: MSBuild error path.
Many other small fixes and improvements.
Version 0.9.1 Beta includes:
- JSLint.NET Console: ** Console help available using the /? switch (or no arguments). See the [Console Options] page for more.
- JSLint.NET for Visual Studio: ** Support linked JSLintNet.json file. More about this file on the [JSLint.NET Settings] page. ** Hide un-implemented menu items. ** Prefix JSLint errors in the task list.
- JSLint.NET Core: ** Allow ignoring of individual files in JSLintNet.json.
This is a beta release of JSLint.NET and associated tools. Each part is working well, but with minimal bells and whistles.
- JSLint.NET for Visual Studio 2012 ** Supports processing files from the context menu, on save and on build. ** Warnings can be cleared from the error list context menu. ** There are currently no screens for this Visual Studio extension, but it can be configured easily by creating a JSLintNet.json file in the root of a project. Read more about this file on the [JSLint.NET Settings] page.
- JSLint.NET Core ** This is the core assembly for use in other projects. ** Includes an MSBuild task that also supports a [JSLintNet.json|JSLint.NET Settings] file.
- JSLint.NET Console Application ** Allows a folder to be processed from the Windows command line. ** Supports [JSLintNet.json|JSLint.NET Settings] file. ** The first argument must be the the directory to be processed. More information on the [Console Options] page.