Quantcast
Channel: Node.js Tools for Visual Studio
Viewing all 4630 articles
Browse latest View live
↧

Closed Issue: Better "Files in your project exceed MAX_PATH" debugging message [1299]

August 18, 2014, 3:08 pm
$
0
0
When moving over to the Beta 2, from the alpha version, i kept getting an error when building saying "Files in your project exceed MAX_PATH, please move your project to a location with a shorter path."

However this message was not true, it turns our that this message can also appear if an included file in the project is missing.

If i log the "_NodeModulesContentProperty" variable i get the error message: "Could not copy the file <FileName> because it was not found." Which is a much more informative debug message.

↧
Search

Commented Unassigned: Max_path warning needs more triggers [1344]

August 18, 2014, 3:10 pm
$
0
0
Npm install outside ?

Build actions?

Copying things around?


Comments: npm install outside is tricky because that would require a full-fledged filesystem watcher, and it would also race against any VS-initiated operation. Copying things around is not particularly useful, because the main source of these troubles is node_modules, and you don't manually tinker with that outside of npm. Validating on build would be the catch-all in case this is missed in any other scenario.
↧
↧

Edited Unassigned: Max_path warning needs more triggers [1344]

August 18, 2014, 3:19 pm
$
0
0
Npm install outside ?

Build actions?

Copying things around?


↧

Edited Unassigned: Max_path warning needs more triggers [1344]

August 18, 2014, 3:58 pm
$
0
0
Npm install outside ?

Build actions?

Copying things around?


↧

Commented Issue: npm Package manager fails to retrieve published package list [1252]

August 18, 2014, 5:32 pm
$
0
0
Sometimes, when I right click npm and select "Manage npm Modules", the package manages says "Loading published package list", but it comes back empty. See screenshot here: ![Image](http://i.imgur.com/pThwb5H.png)

I am still able to install packages using the npm command, but they are not added to packages.json and I have to call npm init manually.
Comments: I have the same problem that Johngom. I had the VS 2013 update 2. Then, i updated to update 3 and the problem still ocurring. (Sorry for my english. I'm brazilian hihihihi) My packagecahce exists but my "Install Packages Windows" still empty everytime. I don't know what to do! Help me
↧
↧

New Post: Build server failing to build a Cloud Service with a Node.js project

August 19, 2014, 1:11 am
$
0
0
Hi guys,

Having a bit of an issue when building a solution including an Azure Cloud Service on our TeamCity build server.

The cloud service has two ASP.NET web roles and a Node.js role. It builds fine within VS locally, but when building on our build server we're getting:
error : WAT070 : The referenced assembly C:\TeamCity\buildAgent\work\a1a1a1a1a1a1a1a1\NodejsApp\NodejsApp.exe was not found. Please make sure to build the role project that produces this assembly before building this Windows Azure Cloud Service Project.
I'm not sure why it's expecting an .exe file to be emitted during the Node.js project build.

The project reference within the cloud service is as follows:
<ProjectReference Include="..\NodejsApp\NodejsApp.njsproj">
  <Name>NodejsApp</Name>
  <Project>{5b84f347-2866-40ee-9252-a1a1a1a1a1a1}</Project>
  <Private>True</Private>
  <RoleType>Web</RoleType>
  <RoleName>NodejsApp</RoleName>
  <UpdateDiagnosticsConnectionStringOnPublish>True</UpdateDiagnosticsConnectionStringOnPublish>
</ProjectReference>
The build server is running TeamCity 8.1.3, and has the following installed:
•Visual Studio Express for Web 2013 Update 3
•Windows Azure SDK 2.3
•Node.js 0.10.30
•Microsoft Azure SDK for Node.js 0.8.0
•Node.js Tools for Visual Studio 1.0 beta 2

How can I persuade our build server to build this properly rather than expect the Node.js project to emit an .exe file?

Many thanks,
G
↧

Commented Unassigned: the "Combine Javascript output into file" option does not work. [1354]

August 19, 2014, 1:53 am
$
0
0
The "Combine Javascript output into file" option does not work for me. It does not take the server.js file so I have the classes I defined in a subfolder, but not the initialisation code that is in server.js.

Is there a workaround ?




Comments: When writing `var http` one is writing JavaScript and not TypeScript. There is some [documentation on the github site](http://www.typescriptlang.org/Handbook#modules).
↧

New Post: Loading custom modules in the Interactive Window

August 19, 2014, 2:00 am
$
0
0
Hi,

The interactive window is a very nice feature. It's great that I'm able to test out NodeJS code on the fly.

I have a couple of questions:
  • Is it possible to associate the interactive window with a particular project in Visual Studio? This would permit loading custom modules defined in that project.
  • How do I load a module installed via npm? At present this works:
var x = require('fs');
but this doesn't
var x = require('htmlParser2')
Error: Cannot find module 'htmlParser2'
NB: I have installed htmlParser2 in one of the NTVS projects, but not all of them.
↧
Search

Edited Issue: Can't create worker role project - Azure Tools not installed [700]

August 19, 2014, 8:56 am
$
0
0
VS 2013, rolling debug build CL1190242

I do NOT have the Azure Tools installed.

Is there any way we can make it more obvious to the user as to what they need to do to fix this? They're probably not going to know they have to install the Azure Tools.

```
---------------------------
Microsoft Visual Studio
---------------------------
A problem was encountered creating the sub project 'Cloud'. The template specified cannot be found. Please check that the full path is correct.
---------------------------
OK
---------------------------

```

↧
↧

Edited Issue: Can't create worker role project - Azure Tools not installed [700]

August 19, 2014, 11:24 am
$
0
0
VS 2013, rolling debug build CL1190242

I do NOT have the Azure Tools installed.

Is there any way we can make it more obvious to the user as to what they need to do to fix this? They're probably not going to know they have to install the Azure Tools.

```
---------------------------
Microsoft Visual Studio
---------------------------
A problem was encountered creating the sub project 'Cloud'. The template specified cannot be found. Please check that the full path is correct.
---------------------------
OK
---------------------------

```

↧

Commented Issue: Copying node_packages to obj/Debug + looong path [1264]

August 19, 2014, 11:28 am
$
0
0
```
Error 16 Unable to copy file "c:\source\xxx-project-name\node_modules\grunt-contrib-cssmin\node_modules\maxmin\node_modules\gzip-size\node_modules\browserify-zlib\node_modules\pako\benchmark\implementations\inflate-pako-untyped\index.js" to "obj\Debug\.\node_modules\grunt-contrib-cssmin\node_modules\maxmin\node_modules\gzip-size\node_modules\browserify-zlib\node_modules\pako\benchmark\implementations\inflate-pako-untyped\index.js". The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Node.js

```
I understand the msbuild 248 limitation cannot be fixed. Why do the node_packages folder get copied though? Is there a way to disable?
Comments: We should defer this copy as late as possible, ideally only do it for the actual publish (or publish preview). In the meantime, the workaround is to override some targets in your .njsproj: ```xml <Target Name="CoreCompile"/> <Target Name="BuiltProjectOutputGroup"/> <Target Name="SourceProjectOutputGroup"/> ```
↧

Edited Issue: Copying node_packages to obj/Debug + looong path [1264]

August 19, 2014, 11:28 am
$
0
0
```
Error 16 Unable to copy file "c:\source\xxx-project-name\node_modules\grunt-contrib-cssmin\node_modules\maxmin\node_modules\gzip-size\node_modules\browserify-zlib\node_modules\pako\benchmark\implementations\inflate-pako-untyped\index.js" to "obj\Debug\.\node_modules\grunt-contrib-cssmin\node_modules\maxmin\node_modules\gzip-size\node_modules\browserify-zlib\node_modules\pako\benchmark\implementations\inflate-pako-untyped\index.js". The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Node.js

```
I understand the msbuild 248 limitation cannot be fixed. Why do the node_packages folder get copied though? Is there a way to disable?
↧

Commented Issue: No signature help when calling a lambda [1140]

August 19, 2014, 3:55 pm
$
0
0
Start typing this:
```
(function (x) { console.log(x); })(
```
I expect a signature help coming up for the function, showing parameter `x`, but there's nothing.
Comments: This is not actually a reverse expression parser problem - it handles lambdas just fine. The problem is that ExpressionEvaluator.EvaluateFunctionExpression returns an empty analysis set if the FunctionObject node it takes as a parameter is not ref-equals to what's saved in the node environment from the analysis: ```cs private static IAnalysisSet EvaluateFunctionExpression(ExpressionEvaluator ee, Node node) { var func = (FunctionExpression)node; EnvironmentRecord funcRec; if (ee.Scope.GlobalEnvironment.TryGetNodeEnvironment(func.Function, out funcRec)) { return ((FunctionEnvironmentRecord)funcRec).AnalysisValue.SelfSet; } Debug.Assert(ee._unit.ForEval, "Failed to find function record"); return AnalysisSet.Empty; } ``` In this particular case it will never be equal, because the function expression is freshly parsed.
↧
↧

Closed Issue: Crash when removing break point [1330]

August 19, 2014, 3:57 pm
$
0
0
I'm running on 1.0 beta 2 with VS 2012.

If I have a break point set, then remove when the code has been stopped by a previous break point I get a crash. So if I break on line 20, and have a break on line 25. Then when I stop at line 20, I remove the break on line 25 and continue - nodetools will crash.
Comments: https://nodejstools.codeplex.com/workitem/1321
↧

Commented Issue: VS crash (KeyNotFoundException) when removing a breakpoint when another one is on the same line [1321]

August 19, 2014, 3:57 pm
$
0
0
(from https://nodejstools.codeplex.com/discussions/554403)

While testing latest NTVS version my vS2013 regularly crashes. It happens just before breakpoint should be hit. In beta 1 I got this crash also, even more regularly, but there was other error logged. I’m using typescript project. Dump from my application events is:

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Collections.Generic.KeyNotFoundException
Stack:
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__5(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()


and

Faulting application name: devenv.exe, version: 12.0.30501.0, time stamp: 0x5361f453
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532943a3
Exception code: 0xe0434352
Fault offset: 0x00011d4d
Faulting process id: 0x1448
Faulting application start time: 0x01cfaa55e0418b61
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 0d3a9720-164a-11e4-8262-c4d9878cc84a
Faulting package full name:
Faulting package-relative application ID:

Same here, with the same log. It happens, when you remove a breakpoint before should be hit (set two breakpoints, remove second on debug).
Comments: I seem to be unable to reproduce this on the most recent dev build. Can you share the code snippet on which this happens for you?
↧
Search

Commented Feature: TypeScript: Build output message incorrect [693]

August 19, 2014, 4:08 pm
$
0
0
Hi,

I just upgraded to TypeScript 1.0RC, but the build output from the NodeJS project says:

```
1>------ Build started: Project: NodejsWebApp1, Configuration: Debug Any CPU ------
1> C:\Program Files (x86)\Microsoft SDKs\TypeScript\0.9\tsc.exe --noImplicitAny etc...
```

Notice where it says "TypeScript\0.9\tsc.exe".

I tested the actual compilation with a breaking change in 1.0RC and it appears that the compiler is actually version 1.0RC rather than the 0.9 as stated.

In any case I suggest that the entire line printing out the compiler and options should not be printed in the output window. This is because this line acts as a stop for the F8 key - which is inconvenient. I mean typically when a build fails I'd hit F8 to go to the first error. But F8 takes me to the line "C:\Program Files (x86)\Micr...".



Comments: I'll follow up with them, but I'd like to understand why it's not an issue for other projects types for them. Can you clarify what you mean by "an ordinary (non-NTVS) TypeScript project"? So far as I know, the only project templates that specifically enable TS are NTVS and Apache Cordova ones (at least out of the box).
↧

Closed Issue: NPM can't install dependency modules if the project name contains CHS chars [1182]

August 19, 2014, 4:16 pm
$
0
0
Config:

- Win8.1 CHS with the latest updates
- VS2013 ENU with Update 3 RC
- NTVS build 20707.01

Repro:

- Create a Node.js Basic Express project with the project name containing the following characters 捷径应用. (I use these chars for the solution name)

Issue:

- NPM failed to install the dependency modules because it thinks the solution/project name is invalid. But in our REPL window, we displayed the first two chars as garbage characters but the last two were fine. For example, this is how the project/solution name looked like in the REPL window (without the quotes). "?��?应用"

- In the NPM command line, it can't install the package either but it doesn't do the wrong encoding of the characters. So the project name was still displayed as 捷径应用.

As suggested in the bugbash, this is unfortunately an NPM issue, but we shouldn't encode the characters wrong.

Comments: https://nodejstools.codeplex.com/workitem/1184
↧
↧

Edited Issue: Completion does not understand interspersed multiline comments [1144]

August 19, 2014, 4:24 pm
$
0
0
```
"string"/*comments*/.
```
The completion at dot shows global variables rather than members of String. Removing the comment and retyping the dot will show the proper list.

This seems to be breaking Quick Info too, e.g. if you manually enter `length` after the dot and then hover over it, there's no Quick Info tip. But it does appear if comment is deleted.
↧

New Post: Shortcut for Copy + Execute in Node.js interactive window

August 19, 2014, 6:15 pm
$
0
0
Apologies if this already exists -

When I'm coding in F# I can highlight some code in the editor, press Ctrl + Enter and have it be copied and executed in the F# interactive window.

Is there a shortcut I can hit where the currently highlighted code will run in the Node.js interactive window? Can it be implemented?

Thanks!
↧

New Post: Shortcut for Copy + Execute in Node.js interactive window

August 19, 2014, 8:05 pm
$
0
0
We have this feature for PTVS but not for NTVS, unfortunately. Feel free to file a feature request for it. It should be a straightforward port from one codebase to another.
↧
Viewing all 4630 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>