I've just started playing around with your addin. I've found 3 issues so far:
1) Whenever I load my solution with a .njsproj, this message appears in the output window:
Show output from: JavaScript Language Service
07:06:34.0279: Referenced file '~/Scripts/_references.js' not found.
2) If I add a block comment ('/*') to the top of one of my .js files in my project, your addon immediately crashes with:
An exception has been encountered. This may be caused by an extension. My log file has this information - <entry>
<record>686</record>
<time>2014/06/08 18:18:49.376</time>
<type>Error</type>
<source>Editor or Editor Extension</source>
<description>Microsoft.Ajax.Utilities.ScannerException: Syntax error
 at Microsoft.Ajax.Utilities.JSScanner.SkipMultilineComment()
 at Microsoft.Ajax.Utilities.JSScanner.ScanNextToken(Boolean scanForRegularExpressionLiterals)
 at Microsoft.NodejsTools.NodejsProjectionBuffer.UpdateLeadingText(ITextSnapshot current)
 at Microsoft.NodejsTools.NodejsProjectionBuffer.DiskBufferChanged(Object sender, TextContentChangedEventArgs e)
 at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.RaiseEvent[TArgs](Object sender, EventHandler`1 eventHandlers, TArgs args)</description>
</entry>
3) Whenever I press F5 to run the project, Visual Studio always says "This project is out of date" and asks if I want to build it. This is a project created from 'existing node project'. When I create a new express project for comparison, it doesn't do this.
Thankyou
Tom
Comments: The "build" part comes from the fact that the projects are MSBuild makefiles. For a regular Node app, the build doesn't actually do anything (though you can change that by adding more targets to your .njsproj, which may be convenient if you want some custom steps to happen before your app is launched form VS). It does actually get used when you publish, because publishing is also an MSBuild target. This is also what "obj" is about. Basically, you can just consider "obj" to be a VS artifact. Regarding the message, it has a checkbox to disable showing it in the future (unfortunately, it is not a default VS setting...).
1) Whenever I load my solution with a .njsproj, this message appears in the output window:
Show output from: JavaScript Language Service
07:06:34.0279: Referenced file '~/Scripts/_references.js' not found.
2) If I add a block comment ('/*') to the top of one of my .js files in my project, your addon immediately crashes with:
An exception has been encountered. This may be caused by an extension. My log file has this information - <entry>
<record>686</record>
<time>2014/06/08 18:18:49.376</time>
<type>Error</type>
<source>Editor or Editor Extension</source>
<description>Microsoft.Ajax.Utilities.ScannerException: Syntax error
 at Microsoft.Ajax.Utilities.JSScanner.SkipMultilineComment()
 at Microsoft.Ajax.Utilities.JSScanner.ScanNextToken(Boolean scanForRegularExpressionLiterals)
 at Microsoft.NodejsTools.NodejsProjectionBuffer.UpdateLeadingText(ITextSnapshot current)
 at Microsoft.NodejsTools.NodejsProjectionBuffer.DiskBufferChanged(Object sender, TextContentChangedEventArgs e)
 at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.RaiseEvent[TArgs](Object sender, EventHandler`1 eventHandlers, TArgs args)</description>
</entry>
3) Whenever I press F5 to run the project, Visual Studio always says "This project is out of date" and asks if I want to build it. This is a project created from 'existing node project'. When I create a new express project for comparison, it doesn't do this.
Thankyou
Tom
Comments: The "build" part comes from the fact that the projects are MSBuild makefiles. For a regular Node app, the build doesn't actually do anything (though you can change that by adding more targets to your .njsproj, which may be convenient if you want some custom steps to happen before your app is launched form VS). It does actually get used when you publish, because publishing is also an MSBuild target. This is also what "obj" is about. Basically, you can just consider "obj" to be a VS artifact. Regarding the message, it has a checkbox to disable showing it in the future (unfortunately, it is not a default VS setting...).