Quantcast
Channel: JSLint.NET
Viewing all 537 articles
Browse latest View live
↧

New Post: Separating syntax errors from JSLint suggestions

December 12, 2014, 1:54 am
$
0
0
So I did. I tried to add a syntax error, so I put
\
In the code. I did get a lot of warnings and a warning titled "Invalid character". But is it possible to have that single warning as an error?
↧
Search

New Post: Intermittent Noesis.Javascript.JavascriptException in Windows Server 2012 x64

December 14, 2014, 12:23 pm
$
0
0
Thanks for the thorough report. It helps a lot.

This is related to this discussion:
https://jslintnet.codeplex.com/discussions/544991

And this issue:
https://jslintnet.codeplex.com/workitem/39

There seems to be something unique about the MSBuild execution context that causes intermittent issues on certain environments. I have considered switching to other JavaScript engines to avoid the issue, but unfortunately they all have a noticeable negative performance trade-off.

I believe the next best step is for us to make a custom build of the latest Noesis JavaScript.NET source and see if that improves things.
↧
↧

Source code checked in, #efadb114ce03a683632c085e61347ee4b3404265

December 15, 2014, 2:20 am
↧

New Post: Intermittent Noesis.Javascript.JavascriptException in Windows Server 2012 x64

December 16, 2014, 2:41 am
$
0
0
I'm also experimenting with switching from Noesis.JavaScript to ClearScript (Microsoft's V8 wrapper). So far it doesn't exhibit any intermittent failures, but I'll queue up a bunch more builds to be sure.

If all goes well, this change will be released as 1.7.
↧

Commented Issue: Error on Visual Studio Online hosted build controller [39]

December 18, 2014, 1:19 am
$
0
0
In certain environments, such as a Visual Studio Online hosted build controller, the MSBuild task can fail with the following error:

"C:\a\src\XXX\ProjectX\ProjectX.csproj" (default target) (8) ->
(JSLintNet target) ->
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: The "JSLintTask" task failed unexpectedly. [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: Noesis.Javascript.JavascriptException [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Noesis.Javascript.CompileScript(Local<v8::Script>* , Char* source_code, Char* resource_name) [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Noesis.Javascript.JavascriptContext.Run(String iSourceCode) [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at JSLintNet.JSLintFactory.CreateContext() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at JSLintNet.JSLintTask.Execute() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext() [C:\a\src\XXX\ProjectX\ProjectX.csproj]

Experiment with different locations for the x86 and amd64 versions of the msvcp100.dll and msvcr100.dll libraries so they can be found by JSLint.NET.
Comments: I have been able to eliminate the intermittent errors by switching from JavaScript.NET to [ClearScript V8](https://clearscript.codeplex.com/). A new release will be available soon.
↧
↧

Created Release: JSLint.NET 1.7.0 (Dec 18, 2014)

December 18, 2014, 1:49 am
↧

Updated Wiki: Home

December 18, 2014, 1:50 am
$
0
0

JSLint.NET

JSLint.NET is a wrapper for Douglas Crockford's JSLint, the JavaScript code quality tool. It can validate JavaScript anywhere .NET runs.

Get JSLint.NET

JSLint.NET for MSBuild

Wires up targets to any Visual Studio project for development and CI time JavaScript validation.Check it out on NuGet and run this command from the package manager console to install:

PM> Install-Package JSLintNet.MSBuild

JSLint.NET for Visual Studio

Provides a richer IDE experience for Visual Studio 2012 and 2013, with underlined warnings and the ability to validate automatically on save and build. Download it from the Extensions and Tools dialog within Visual Studio or from the Visual Studio Gallery.

Other Editions

All flavors of JSLint.NET can be downloaded from the CodePlex releases page.

1.7.0 Released

This version resolves intermittent MSBuild failures in certain build environments. Under the hood, the V8 JavaScript engine is now provided byClearScript.

Older Releases

See past release information on the Change Log page.

 

↧

Updated Wiki: Change Log

December 18, 2014, 1:52 am
$
0
0

Change Log

1.7

This version resolves intermittent MSBuild failures in certain build environments. Under the hood, the V8 JavaScript engine is now provided by ClearScript.
1.7.0
Bugs:
  • #39: Intermittent MSBuild failures.

1.6

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.
1.6.5
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.
1.6.4
Bugs:
  • #38: MSBuild task support for linked settings file.
  • #40: Explicitly typed imports / exports required in some Visual Studio environments.
1.6.3
Features:
  • Upgraded JSLint to edition 2014-07-08 (disallows inefficient literal access).
Bugs:
  • #26: Fixed regression of project assumption bug in Visual Studio.
1.6.2
Features:
  • Upgraded JSLint to edition 2014-04-22 (allows leading semicolon).
1.6.1
Features:
  • Upgraded JSLint to edition 2014-04-08.
1.6.0
Features: Bugs:
  • #35: Fixed folder scanning for Node.js Tools projects.
  • #36: Fixed settings file for C++ projects.

1.5

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.
1.5.1
Features:
  • Added minClientVersion attribute for NuGet 2.8.0.
Note: This patch version is only available via NuGet.
1.5.0
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.

1.4

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.
1.4.1
Features:
  • Upgraded JSLint to edition 2014-01-26.
  • Marked JSLintNet.MSBuild NuGet package as a development only dependency.
1.4.0
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.

1.3

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 in the same way as the rest of the JSLint.NET tools.

Internally, JSLint has been upgraded to edition 2013-11-23.
1.3.1
Features:
  • #29: Added configurable properties to JSLint.NET for MSBuild NuGet package.
Bugs:
  • #28: Visual Studio extension not ignoring files.
1.3.0
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

1.2

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.
1.2.2
Bugs:
  • #25: Fixed tag migration.
  • #26: Fixed project assumption bug.

JSLint edition: 2013-11-21
1.2.1
Bugs:
  • #21: Fixed incorrect text marker position error.
1.2.0
Features:
  • #19: Run from project and folder context menu.
  • #20: Visual Studio 2013 support.
Bug:
  • #4: Fixed tooltips on error markers.

1.1

This version contains three significant changes (and lots of little updates). See the releases page for more information and downloads.
1.1.0
Features:
  • #11: Ability to upgrade JSLint version.
  • #17: Configurable limits.
  • #18: Removed "es5" option.

JSLint edition: 2013-09-22

1.0

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.
1.0.0
Features:
  • #16: Ignore files and folders from Visual Studio menu.

0.9

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.
0.9.2
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.
0.9.1
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.
0.9.0
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 file.
  • JSLint.NET Console Application
    • Allows a folder to be processed from the Windows command line.
    • Supports JSLintNet.json file.
    • The first argument must be the the directory to be processed. More information on the Console Options page.
↧
Search

Source code checked in, #0bc42ccece8455233731c86a013ea2f607129210

December 18, 2014, 1:16 am
↧
↧

Source code checked in, #0c3f7b0b0ce056342ed34bdec92885bc9669d04d

December 18, 2014, 1:27 am
↧

Released: JSLint.NET 1.7.0 (Dec 18, 2014)

December 18, 2014, 1:49 am
↧

Edited Issue: Error on Visual Studio Online hosted build controller [39]

December 18, 2014, 1:53 am
$
0
0
In certain environments, such as a Visual Studio Online hosted build controller, the MSBuild task can fail with the following error:

"C:\a\src\XXX\ProjectX\ProjectX.csproj" (default target) (8) ->
(JSLintNet target) ->
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: The "JSLintTask" task failed unexpectedly. [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: Noesis.Javascript.JavascriptException [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Noesis.Javascript.CompileScript(Local<v8::Script>* , Char* source_code, Char* resource_name) [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Noesis.Javascript.JavascriptContext.Run(String iSourceCode) [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at JSLintNet.JSLintFactory.CreateContext() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at JSLintNet.JSLintTask.Execute() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext() [C:\a\src\XXX\ProjectX\ProjectX.csproj]

Experiment with different locations for the x86 and amd64 versions of the msvcp100.dll and msvcr100.dll libraries so they can be found by JSLint.NET.
↧

Commented Issue: Error on Visual Studio Online hosted build controller [39]

December 18, 2014, 1:53 am
$
0
0
In certain environments, such as a Visual Studio Online hosted build controller, the MSBuild task can fail with the following error:

"C:\a\src\XXX\ProjectX\ProjectX.csproj" (default target) (8) ->
(JSLintNet target) ->
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: The "JSLintTask" task failed unexpectedly. [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: Noesis.Javascript.JavascriptException [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Noesis.Javascript.CompileScript(Local<v8::Script>* , Char* source_code, Char* resource_name) [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Noesis.Javascript.JavascriptContext.Run(String iSourceCode) [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at JSLintNet.JSLintFactory.CreateContext() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at JSLintNet.JSLintTask.Execute() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [C:\a\src\XXX\ProjectX\ProjectX.csproj]
C:\a\src\XXX\packages\JSLintNet.MSBuild.1.6.2\build\JSLintNet.MSBuild.targets(20,5): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext() [C:\a\src\XXX\ProjectX\ProjectX.csproj]

Experiment with different locations for the x86 and amd64 versions of the msvcp100.dll and msvcr100.dll libraries so they can be found by JSLint.NET.
Comments: Fixed in 0bc42ccece84
↧
↧

Source code checked in, #45271811414433120a0f51ba01efebc5683bd85c

December 18, 2014, 1:57 am
$
0
0
Removed redundant dynamic assembly resolver.
↧

New Post: Intermittent Noesis.Javascript.JavascriptException in Windows Server 2012 x64

December 19, 2014, 12:34 am
↧
Search

New Post: Problems using MSBuild target in TFS build (Visual Studio Online hosted build controller)

December 19, 2014, 12:35 am
↧

New Post: Intermittent Noesis.Javascript.JavascriptException in Windows Server 2012 x64

December 29, 2014, 11:19 am
$
0
0
That's great news! As a workaround, I am running the JSLint executable as one of the AfterBuild tasks in my project.

Thanks Qube for your hard work in making JSLint easily accessible for .NET developers! I look forward to your next version.
↧
↧

New Post: Intermittent Noesis.Javascript.JavascriptException in Windows Server 2012 x64

December 30, 2014, 12:22 pm
$
0
0
You're welcome. JSLint.NET for MSBuild 1.7 is up on NuGet, so please upgrade and let me know how you go.
↧

New Post: Intermittent Noesis.Javascript.JavascriptException in Windows Server 2012 x64

January 13, 2015, 8:37 am
$
0
0
The new version works perfectly now. I have been running version 1.7 for more than a week now, and the intermittent errors are gone. Seems like the switch from Noesis did the trick.

A minor issue is that the option to run JSLint on save does not seem to work anyone. Using VS 2013 Ultimate.
↧

New Post: Intermittent Noesis.Javascript.JavascriptException in Windows Server 2012 x64

January 16, 2015, 3:18 pm
$
0
0
prokaryx wrote:
A minor issue is that the option to run JSLint on save does not seem to work anyone. Using VS 2013 Ultimate.
Well that's odd. The "run on save" setting is only available with the Visual Studio extension - see the settings table. Have both the NuGet and VSIX been upgraded?
↧
Viewing all 537 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>