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

Created Unassigned: waitforattach in RemoteDebug.js starts node too early [1368]

August 26, 2014, 1:38 pm
$
0
0
Repro steps:
1. On remote target run the command: "Node.exe RemoteDebug.js -waitforattach <js file>"
2. In VS, open Attach to Process dialog
3. After setting the Node.js transport, enter the appropriate qualifier
4. Press Refresh button

Result:
Node starts running

Expected Result:
Node starts running when I press Attach button
↧
Search

Created Unassigned: Feature Request: Deploy and start Node on remote target from Visual Studio [1369]

August 26, 2014, 1:44 pm
$
0
0
Currently, debugging Node remotely requires the exe to be started on the target device and then from VS you use Attach to Process.
It would be great if I could create a Node project and have the ability to:
1. Deploy Node and project JS files to target device.
2. Start Node on target machine and attach debugger automatically.

Basically have behavior that is similar to debugging locally with just pressing "Start"
↧
↧

Commented Unassigned: waitforattach in RemoteDebug.js starts node too early [1368]

August 26, 2014, 2:48 pm
$
0
0
Repro steps:
1. On remote target run the command: "Node.exe RemoteDebug.js -waitforattach <js file>"
2. In VS, open Attach to Process dialog
3. After setting the Node.js transport, enter the appropriate qualifier
4. Press Refresh button

Result:
Node starts running

Expected Result:
Node starts running when I press Attach button
Comments: This is an unfortunate side effect of the Attach to Process dialog actually doing the attach when populating the process list, to make sure that the machine has Node running on that port. It immediately detaches after receiving the initial V8 response, but it still counts as an attach, so the proxy spins up the actual process. To fix this, we'll need to make the proxy smarter. Right now it's just a dumb pipe that copies packets over from an externally visible socket to the one that Node actually binds to. It would have to peek at the packets, and somehow figure out that the attach is really just a ping, and respond to that ping itself without spinning up Node. We can probably add a custom X-NTVS-... request header to that request as a marker, but first need to make sure that V8 itself won't balk at it (we still want attach to work without the proxy, just with node.exe --debug).
↧

Commented Unassigned: Feature Request: Deploy and start Node on remote target from Visual Studio [1369]

August 26, 2014, 2:55 pm
$
0
0
Currently, debugging Node remotely requires the exe to be started on the target device and then from VS you use Attach to Process.
It would be great if I could create a Node project and have the ability to:
1. Deploy Node and project JS files to target device.
2. Start Node on target machine and attach debugger automatically.

Basically have behavior that is similar to debugging locally with just pressing "Start"
Comments: This needs to be more specific, since deployment methods can vary a lot depending on what the device supports. Today, we support deployment to Azure web sites and cloud services. Web sites in particular use the standard VS publish functionality that is also used for web projects in other languages, and that has a number of publish targets - Web Deploy, obviously, but also FTP or generic filesystem copy. I'm not sure if that is extensible on UI level, but the publish pipeline on MSBuild level definitely is (it's just a target, and it builds up a list of files before handing it over). Similarly, for starting node on the target device, that device needs to expose some protocol that enables such a thing, and reports completion so that VS knows to attach.
↧

Commented Unassigned: waitforattach in RemoteDebug.js starts node too early [1368]

August 26, 2014, 4:38 pm
$
0
0
Repro steps:
1. On remote target run the command: "Node.exe RemoteDebug.js -waitforattach <js file>"
2. In VS, open Attach to Process dialog
3. After setting the Node.js transport, enter the appropriate qualifier
4. Press Refresh button

Result:
Node starts running

Expected Result:
Node starts running when I press Attach button
Comments: By the way, in the meantime, there is an undocumented (not anymore, I guess!) hack that unit test runner uses to spin up debugging. When entering the machine qualifier in Attach to Process, append `#ping=0` at the end of the `tcp://` URL. This will prevent it from pinging the server, and just display one fake node.exe process; the connection will only be established once, when you click "Attach".
↧
↧

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

August 27, 2014, 3:27 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: @pminaev this is *exactly* what I needed :)
↧

Created Unassigned: Build Action / Publish options missing from linked files [1370]

August 27, 2014, 3:29 am
$
0
0
These options are not available for linked files from the Properties pane.
↧

Edited Unassigned: Build Action / Publish options missing from linked files [1370]

August 27, 2014, 3:29 am
$
0
0
These options are not available for linked files from the Properties pane for linked files.

This is an issue for me as I have common code I share across projects and I need to publish the file with my builds.
↧
Search

Commented Unassigned: Build Action / Publish options missing from linked files [1370]

August 27, 2014, 6:15 am
$
0
0
These options are not available for linked files from the Properties pane for linked files.

This is an issue for me as I have common code I share across projects and I need to publish the file with my builds.
Comments: Actually, more digging into this suggests that this is more of a VS limitation than a NodeJS tools one. However, that being said, it would be a nice enhancement :)
↧
↧

Commented Unassigned: Build Action / Publish options missing from linked files [1370]

August 27, 2014, 8:44 am
$
0
0
These options are not available for linked files from the Properties pane for linked files.

This is an issue for me as I have common code I share across projects and I need to publish the file with my builds.
Comments: I am working around this at the moment by adding a new target into the njsproj file ``` <!-- Copy linked files --> <Target Name="CopyLinkedFiles" AfterTargets="Build"> <Copy SourceFiles="@(Content)" DestinationFiles="@(Content->'$(IntermediateOutputPath)%(Link)')" SkipUnchangedFiles="true" OverwriteReadOnlyFiles="true" Condition="%(Content.Link) != ''" /> </Target> ```
↧

Reviewed: Latest dev build (Aug 27, 2014)

August 27, 2014, 8:59 am
$
0
0
Rated 2 Stars (out of 5) - With VS2013 update 3 I'm now able to use this release to load my solution, successfully debug, and don't experience any crashes when performing this simple workflow. However performance in terms of CPU usage and memory usage is still bad (and I guess if left unchecked will lead to a crash with >2GB in use). Turning off full intellisense helps but still not great. Can I help by providing you with more information?
↧

Commented Unassigned: Feature Request: Deploy and start Node on remote target from Visual Studio [1369]

August 27, 2014, 11:25 am
$
0
0
Currently, debugging Node remotely requires the exe to be started on the target device and then from VS you use Attach to Process.
It would be great if I could create a Node project and have the ability to:
1. Deploy Node and project JS files to target device.
2. Start Node on target machine and attach debugger automatically.

Basically have behavior that is similar to debugging locally with just pressing "Start"
Comments: Will add more info...
↧

Created Issue: Publish Setting on Item not respected [1371]

August 27, 2014, 11:31 am
$
0
0
The publish setting on a project item is not respected. All items in a project are published regardless of a users settings on this. We should listen to this setting so users can choose to exclude files from publish.
↧
↧

Edited Issue: Breakpoints inside functions don't work when attaching [1365]

August 27, 2014, 1:49 pm
$
0
0
```js
setInterval(function () {
console.log('Hello');
}, 5000);
```

Set a breakpoint on `console.log`. Run the script with `RemoteProxy.js`, and attach to it from a local VS instance (will probably need to use the machine name rather than localhost for this). The breakpoint is marked as unbound in VS, and is not hit, despite script repeatedly printing out "Hello".

↧

Commented Unassigned: cannot debug project anymore [1340]

August 27, 2014, 4:28 pm
$
0
0
I can no longer debug one of my projects. The build output window shows the following. I'm not exactly sure what has changed, but it used to debug fine. I didn't change the path, so I can't imagine how there are any illegal characters in it. Please let me know if there is any more information I can give.

```

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Node.js Tools\Microsoft.NodejsTools.targets(137,5): error MSB4018: The "AssignTargetPath" task failed unexpectedly.
System.ArgumentException: Illegal characters in path.
at System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional)
at System.Security.Permissions.FileIOPermission.CheckIllegalCharacters(String[] str)
at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath)
at System.IO.Path.GetFullPath(String path)
at Microsoft.Build.Tasks.AssignTargetPath.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
Done building project "api-server.njsproj" -- FAILED.

Build FAILED.

```
Comments: It sounds like this is also the MAX_PATH issue that is floating around. I believe the problem started when I added gulp to devDependencies. I've moved my code to a really short folder name off of C:\ and it seems to be working again.
↧
Search

Commented Issue: KeyNotFoundException crashes VS [1343]

August 27, 2014, 4:54 pm
$
0
0
Hi,

I have the same problem, but not the same error.
VS2013 also crash on my computer (only with nodejs projects) but the error in my case 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()


Emilien
Comments: Pretty sure this is a dupe of https://nodejstools.codeplex.com/workitem/1321 (the stacks can vary due to all the async goo). Please reactivate if you still see it happening for you in the next dev build that we'll put out.
↧

Closed Issue: KeyNotFoundException crashes VS [1343]

August 27, 2014, 4:55 pm
$
0
0
Hi,

I have the same problem, but not the same error.
VS2013 also crash on my computer (only with nodejs projects) but the error in my case 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()


Emilien
Comments: https://nodejstools.codeplex.com/workitem/1321
↧
↧

Reviewed: 1.0 Beta 2 (八月 28, 2014)

August 28, 2014, 12:55 am
$
0
0
Rated 5 Stars (out of 5) - Hello, may I know if you are interested to find Sponsor for your product? And we want to be your sponsor. Please mail me cxienancy@gmail.com for detailed information. Thank you very much.
↧

Created Unassigned: Publish to azure not working [1372]

August 28, 2014, 1:09 am
$
0
0
When I get to the Preview section of the publish and hit `Start Preview` I get the following error

![Image](http://i57.tinypic.com/nb3epd.png)

If I continue it then just sticks on

![Image](http://i61.tinypic.com/11c3vac.png)

If I skip the preview part and just go straight to publish, it tells me that the publish was successul and the Web Publish Activity console stays like

![Image](http://i58.tinypic.com/t0nrx5.png)

Any idea's what's going on here?
↧

Edited Unassigned: Publish to Azure not working [1372]

August 28, 2014, 1:09 am
$
0
0
When I get to the Preview section of the publish and hit `Start Preview` I get the following error

![Image](http://i57.tinypic.com/nb3epd.png)

If I continue it then just sticks on

![Image](http://i61.tinypic.com/11c3vac.png)

If I skip the preview part and just go straight to publish, it tells me that the publish was successul and the Web Publish Activity console stays like

![Image](http://i58.tinypic.com/t0nrx5.png)

Any idea's what's going on here?
↧
Viewing all 4630 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>