VS2013 using nodejs tools

Mar 5, 2014 at 1:46 PM
Running JSLint from the solution explorer is not picking up .js files in sub folders.

If I expand the folders and right-click on the sub-folder to run JSLint it will run on the files at that level, but not any files further down the folder tree.

This may of course be something to do with the way that nodejs tools organise the project file.
Coordinator
Mar 8, 2014 at 9:29 PM
Edited Mar 8, 2014 at 9:38 PM
Would you mind putting together a basic repro project for me to test? Some installation steps / pre-reqs would help too.

Feel free to attach a zip to the other issue you raised. We can probably kill two birds with one stone here.
Mar 10, 2014 at 8:45 AM
No problem - I'll get onto it today.
Mar 10, 2014 at 2:04 PM
Below is a highly trimmed down version of my project file (there are thousands of file in the original).
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    ...
  </PropertyGroup>
  <PropertyGroup Condition="'$(Configuration)' == 'Release'" />
  <ItemGroup>
    <Content Include="package.json" />
    <Content Include="README.md" />
    <Compile Include="apatch.js" />
    <Compile Include="Gruntfile.js" />
    <Compile Include="index.js" />
    <Compile Include="nodelocal.js" />
    <Content Include="node_modules\ez-streams\examples\echo._js" />
    <Content Include="node_modules\ez-streams\examples\oracleMongoPipe._js" />
    <Content Include="node_modules\ez-streams\lib\reader._js" />
    <Content Include="node_modules\ez-streams\lib\writer._js" />
    <Compile Include="node_modules\ez-streams\lib\index.js" />
  </ItemGroup>
  <ItemGroup>
    <Folder Include="node_modules" />
    <Folder Include="node_modules\ez-streams" />
    <Folder Include="node_modules\ez-streams\examples" />
    <Folder Include="node_modules\ez-streams\lib" />
  </ItemGroup>
  <Import Project="$(MSBuildToolsPath)\Microsoft.Common.targets" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" />
  <Import Project="$(VSToolsPath)\Node.js Tools\Microsoft.NodejsTools.targets" />
  <ProjectExtensions>
    <VisualStudio>
      <FlavorProperties GUID="{349c5851-65df-11da-9384-00065b846f21}">
        <WebProjectProperties>
         ...
        </WebProjectProperties>
      </FlavorProperties>
      <FlavorProperties GUID="{349c5851-65df-11da-9384-00065b846f21}" User="">
        <WebProjectProperties>
        ...
        </WebProjectProperties>
      </FlavorProperties>
    </VisualStudio>
  </ProjectExtensions>
</Project>
Coordinator
Apr 11, 2014 at 3:21 AM
This has been fixed as part of issue 35.