I tried to create new .njsproj on a path that contains space and it will fail with "Directory not found" error.
↧
Edited Unassigned: can't create new projects if folder path contains space [1326]
↧
Edited Issue: Installing new version of NTVS changes jade coloring [1159]
After installing a new version of the tool set the jade syntax highlighting resets to a color set that isn't compatible with Dark Mode theme in Visual Studio.
Jade keywords are dark red and html tags are very dark blue which is very hard to read.
Jade keywords are dark red and html tags are very dark blue which is very hard to read.
↧
↧
Edited Issue: Adding web role to cloud service doesn't add node.js specifics to service config file [861]
Let's say you want a solution that has a web role and one or more worker roles, all of them as part of the same cloud service.
I proceeded by using the Worker role new project template. Then I added an Azure web project to my solution. Then I went to the cloud project added my web project from my solution as a web role.
When I went to publish, I got a 500 error, due to the missing node.js specific configuration for the web role in ServiceDefinition.csdef (IISNODE, setup_web.cmd, etc.).
I proceeded by using the Worker role new project template. Then I added an Azure web project to my solution. Then I went to the cloud project added my web project from my solution as a web role.
When I went to publish, I got a 500 error, due to the missing node.js specific configuration for the web role in ServiceDefinition.csdef (IISNODE, setup_web.cmd, etc.).
↧
Edited Issue: Installing new version of NTVS changes jade coloring [1159]
After installing a new version of the tool set the jade syntax highlighting resets to a color set that isn't compatible with Dark Mode theme in Visual Studio.
Jade keywords are dark red and html tags are very dark blue which is very hard to read.
Jade keywords are dark red and html tags are very dark blue which is very hard to read.
↧
Commented Unassigned: can't create new projects if folder path contains space [1326]
I tried to create new .njsproj on a path that contains space and it will fail with "Directory not found" error.
Comments: Hi Chris, thanks for following up! I can still repro on my VS2012. Repro steps below: 1. create new NodeJs project from existing NodeJs code (ProjName: NodeJsApp1, Path: C:\Users\cxu\Documents\Visual Studio 2012\Projects) 2. set folder containing Js file to C:\src\Predixion v1\Asterix\99.Test\PXTest\NodeJs 3. select one js file as the default start 4. accept default save folder: C:\Users\cxu\Documents\Visual Studio 2012\Projects\NodejsApp1.njsproj and click Finish. Error: --------------------------- Node.js Tools for Visual Studio --------------------------- An unexpected error (DirectoryNotFoundException) occurred while creating your project. --------------------------- OK --------------------------- I'll try the latest dev build to see if it also repros.
Comments: Hi Chris, thanks for following up! I can still repro on my VS2012. Repro steps below: 1. create new NodeJs project from existing NodeJs code (ProjName: NodeJsApp1, Path: C:\Users\cxu\Documents\Visual Studio 2012\Projects) 2. set folder containing Js file to C:\src\Predixion v1\Asterix\99.Test\PXTest\NodeJs 3. select one js file as the default start 4. accept default save folder: C:\Users\cxu\Documents\Visual Studio 2012\Projects\NodejsApp1.njsproj and click Finish. Error: --------------------------- Node.js Tools for Visual Studio --------------------------- An unexpected error (DirectoryNotFoundException) occurred while creating your project. --------------------------- OK --------------------------- I'll try the latest dev build to see if it also repros.
↧
↧
Edited Unassigned: Could not attach Azure remote debugger [1355]
Currently getting the following error when attempting to attach the debugger to my Azure website:
"Error retrieving websocket debug proxy information from web.config"
"Error retrieving websocket debug proxy information from web.config"
↧
Edited Issue: Could not attach Azure remote debugger [1355]
Currently getting the following error when attempting to attach the debugger to my Azure website:
"Error retrieving websocket debug proxy information from web.config"
"Error retrieving websocket debug proxy information from web.config"
↧
Commented Issue: Could not attach Azure remote debugger [1355]
Currently getting the following error when attempting to attach the debugger to my Azure website:
"Error retrieving websocket debug proxy information from web.config"
Comments: Can you check whether the website is published in Debug configuration? (note that this is distinct from your current active solution configuration)
"Error retrieving websocket debug proxy information from web.config"
Comments: Can you check whether the website is published in Debug configuration? (note that this is distinct from your current active solution configuration)
↧
Commented Issue: Could not attach Azure remote debugger [1355]
Currently getting the following error when attempting to attach the debugger to my Azure website:
"Error retrieving websocket debug proxy information from web.config"
Comments: Ah, yep that fixed it. Thanks.
"Error retrieving websocket debug proxy information from web.config"
Comments: Ah, yep that fixed it. Thanks.
↧
↧
Commented Unassigned: the "Combine Javascript output into file" option does not work. [1354]
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: In fact it works until there is a import http = require('http'); line in the main file. I tried command line with tsc.exe it give the same result... so it's not a NTVS problem. (if someone can point me to an explanation of the problem I'll be gratefull)
Is there a workaround ?
Comments: In fact it works until there is a import http = require('http'); line in the main file. I tried command line with tsc.exe it give the same result... so it's not a NTVS problem. (if someone can point me to an explanation of the problem I'll be gratefull)
↧
Commented Unassigned: the "Combine Javascript output into file" option does not work. [1354]
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: I would expect that this is because Node.js module system wants to have modules in separate files, so the "combine in one file" TS mode doesn't make much sense. Can you tell more about your scenario - i.e. why do you want to use this option? Perhaps there's a better way to achieve this with Node.
Is there a workaround ?
Comments: I would expect that this is because Node.js module system wants to have modules in separate files, so the "combine in one file" TS mode doesn't make much sense. Can you tell more about your scenario - i.e. why do you want to use this option? Perhaps there's a better way to achieve this with Node.
↧
Commented Unassigned: the "Combine Javascript output into file" option does not work. [1354]
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: @pminaev is right. "Combine Javascript output into file" will not currently work for external modules.
Is there a workaround ?
Comments: @pminaev is right. "Combine Javascript output into file" will not currently work for external modules.
↧
Commented Unassigned: the "Combine Javascript output into file" option does not work. [1354]
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: I want to instanciate my classes with the syntax "var instance=new MyClass();" wich is much more convenient in my own opinion. To do this, I usually combine all files in one. Bur with Nodejs, as soon as there is a "import http = require('http');" line, the code of server.ts is not combined. Everything works great if I combine files manually.
Is there a workaround ?
Comments: I want to instanciate my classes with the syntax "var instance=new MyClass();" wich is much more convenient in my own opinion. To do this, I usually combine all files in one. Bur with Nodejs, as soon as there is a "import http = require('http');" line, the code of server.ts is not combined. Everything works great if I combine files manually.
↧
↧
Commented Unassigned: the "Combine Javascript output into file" option does not work. [1354]
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: I just replaced import http = require('http'); by var http = require('http'); and it works as expected. Thank you for your attention. I do not create modules in my project.
Is there a workaround ?
Comments: I just replaced import http = require('http'); by var http = require('http'); and it works as expected. Thank you for your attention. I do not create modules in my project.
↧
Commented Unassigned: the "Combine Javascript output into file" option does not work. [1354]
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: Maybe import should be replaced by var in the template project ? Why using import there if var works ?
Is there a workaround ?
Comments: Maybe import should be replaced by var in the template project ? Why using import there if var works ?
↧
Created Issue: .gitignore ignores some .nodejs submodules [1356]
Repro: http://blog.jongallant.com/2014/08/nodejs-visual-studio-azure.html#.U_IqM_9OVaS
Looks like this is an issue with the .gitignore file that’s added in new project when you check “add to source control” on new project creation. There’s one line (“[Dd]ebug/”) that prevents `debug` (one of the submodules) from being added to the git repo – workaround - comment out or remove the unnecessary lines in .gitignore, then git add.
Looks like this is an issue with the .gitignore file that’s added in new project when you check “add to source control” on new project creation. There’s one line (“[Dd]ebug/”) that prevents `debug` (one of the submodules) from being added to the git repo – workaround - comment out or remove the unnecessary lines in .gitignore, then git add.
↧
Edited Issue: .gitignore ignores some node.js submodules [1356]
Repro: http://blog.jongallant.com/2014/08/nodejs-visual-studio-azure.html#.U_IqM_9OVaS
Looks like this is an issue with the .gitignore file that’s added in new project when you check “add to source control” on new project creation. There’s one line (“[Dd]ebug/”) that prevents `debug` (one of the submodules) from being added to the git repo – workaround - comment out or remove the unnecessary lines in .gitignore, then git add.
Looks like this is an issue with the .gitignore file that’s added in new project when you check “add to source control” on new project creation. There’s one line (“[Dd]ebug/”) that prevents `debug` (one of the submodules) from being added to the git repo – workaround - comment out or remove the unnecessary lines in .gitignore, then git add.
↧
↧
Commented Issue: Kraken app causes VS2013 to crash on app launch [569]
I have a created an empty kraken.js app by following the getting started instructions, this app I can run my issuing the "npm start" command
I then create a node project in vs 2013 using the "from existing node,js code" template and add my newly created kraken app folder
The code is imported ok but whne I try and run the app (index.js is set as start up) the debug cmd window is launched but then vs crashes leaving the node process running
Vs briefly shows the q.js file before crashing and restarting
the cmd window reports error 10054 after starting the debug listener
the full output of the cmd window is
debugger listening on port 5858
Error 10054
Multipart body parsing will be disabled by default in future versions. To enable
, use `middleware:multipart` configuration.
connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0
Listening on 18128
I have the following versions installed
node 0.10.22
npm 1.3.14
ntvs 1.0.11119.03
How do I debug this issue - is there some logging in vs I can turn on to find out whats causing it crash vs 2013?
Comments: I have had the same error while using the nodejs tools with VS. I thought it was Kraken.js, so I got rid of it and things went well until today I run into 10054 error again. Nodejs is pissing me off these days, not only is it not a mature framework, the tooling around it is minimal at most. Although MS is trying to do a good job at providing tooling for it, I am afraid the nature of the framework is not suitable for large scaling application or tooling. When can I go back to the established ASP.NET and the like with the ease of tooling from VS.
I then create a node project in vs 2013 using the "from existing node,js code" template and add my newly created kraken app folder
The code is imported ok but whne I try and run the app (index.js is set as start up) the debug cmd window is launched but then vs crashes leaving the node process running
Vs briefly shows the q.js file before crashing and restarting
the cmd window reports error 10054 after starting the debug listener
the full output of the cmd window is
debugger listening on port 5858
Error 10054
Multipart body parsing will be disabled by default in future versions. To enable
, use `middleware:multipart` configuration.
connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0
Listening on 18128
I have the following versions installed
node 0.10.22
npm 1.3.14
ntvs 1.0.11119.03
How do I debug this issue - is there some logging in vs I can turn on to find out whats causing it crash vs 2013?
Comments: I have had the same error while using the nodejs tools with VS. I thought it was Kraken.js, so I got rid of it and things went well until today I run into 10054 error again. Nodejs is pissing me off these days, not only is it not a mature framework, the tooling around it is minimal at most. Although MS is trying to do a good job at providing tooling for it, I am afraid the nature of the framework is not suitable for large scaling application or tooling. When can I go back to the established ASP.NET and the like with the ease of tooling from VS.
↧
Commented Issue: Crash when removing break point [1330]
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: Can you share a code snippet that reproduces this problem?
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: Can you share a code snippet that reproduces this problem?
↧
Commented Issue: Better "Files in your project exceed MAX_PATH" debugging message [1299]
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.
Comments: I can't seem to be able to repro this on our current bits. If a file is missing from a project, MSBuild emits a "could not copy the file" error message in the Output Window, and that is then picked up by the Error List. There's no spurious MAX_PATH error there. I can't think of any way it can be triggered, because the MAX_PATH warning is basically conditional on `NodeModulesContentProperty` containing an asterisk - and that error message text does not include any. Please reactivate if you still hit this on the most recent dev build, and provide more information about the project on which it happens.
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.
Comments: I can't seem to be able to repro this on our current bits. If a file is missing from a project, MSBuild emits a "could not copy the file" error message in the Output Window, and that is then picked up by the Error List. There's no spurious MAX_PATH error there. I can't think of any way it can be triggered, because the MAX_PATH warning is basically conditional on `NodeModulesContentProperty` containing an asterisk - and that error message text does not include any. Please reactivate if you still hit this on the most recent dev build, and provide more information about the project on which it happens.
↧