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

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

August 22, 2014, 3:32 pm
$
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: Why do we want to combine Javascript output into one file for typeScript development ? The answer is very simple to me: avoid all .js and .js.map files to polluate the njsproj ! As soon as I discovered this option provided by tsc, my project was clean, easy to organize even in Windows Explorer and share. This feature is necessary for me and works with all other TypeScript projects in Visual Studio, so why not for NodejsTools ? But this is just my opinion and I hope you will take in consideration.
↧
Search

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

August 22, 2014, 5:15 pm
$
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: Can you clarify "avoid all .js and .js.map files to polluate the njsproj"? The normal workflow for these is to _not_ have them in your .njsproj file. You can still get to them with "Show All Files", and if you write mixed JS/TS code, the analyzer will still pick them up; and web site publish will package them up regardless, too. But otherwise, the expectation is to treat them purely as build artifacts, just like "obj" and "bin" folders.
↧
↧

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

August 23, 2014, 1:12 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: "avoid all .js and .js.map files to polluate the Nodejs project folders" for clarification and I never mentioned .njsproj file. Sorry for my bad explaination. I always turn "Show All Files" on in all my projects to keep control over hidden files which is probably my problem. In my point of view, example1.js and example1.js.map files attached to example1.ts (...) for a njsproj project could be considered as example1.dll and example1.pdb files attached to example1.cs (...) for a csproj project. I know that's a very bad example. If you want to share quickly from one njsproj project to another one, 20 classes from 20 .ts files, that's easier to combine js and get 1 .js .js.map .d.ts file instead of searching those 20 .js .js.map .ts files. "This feature is necessary for me and works with all other TypeScript projects in Visual Studio, so why not for NodejsTools ?"
↧

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

August 23, 2014, 1:21 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: @pminaev Can you please explain or point me to a documentation that explain the workflow to : - have classes in separates .ts files - instanciate classes with the syntax "var instance=new MyClass();" (with references) an not "import http=require('http'); server=new http.server(...." - allow to use modules for third party libraries
↧

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

August 23, 2014, 1:28 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: I meant allow to use __external__ modules (for nodejs).
↧
↧

Edited Issue: VS crash (KeyNotFoundException) when removing a breakpoint [1321]

August 25, 2014, 4:49 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).
↧

Commented Unassigned: can't create new projects if folder path contains space [1326]

August 25, 2014, 4:50 pm
$
0
0
I tried to create new .njsproj on a path that contains space and it will fail with "Directory not found" error.
Comments: I tried with your exact repro on the following configuration and cannot seem to reproduce this. Windows 8.1 64bit, Visual Studio 2012 with Update 4, Node.js Tools for Visual Studio 1.0 Beta 2 Were you able to reproduce this?
↧

New Post: Still Not stable

August 25, 2014, 10:59 pm
$
0
0
The add on is still not stable to build code on Node using VS . Earlier it used to crash on unhandled exceptions and breakpoints (Did not find that in the latest dev release), but it crashes when i try to open the package.json...odd .
I find Web matrix to be a much better alternative than VS right now for writing Nod js apps , although i would love to return back to VS
↧
Search

New Post: TFS error on get latest version

August 26, 2014, 12:55 am
$
0
0
Since beta2, we can't get the latest version via the solution explorer (only for nodejstools projects):

Message error:
The operation could not be completed
Output from Source Control - Team Foundation:
TF10121: The path '' is not found or not supported. Type or select a different path.
↧
↧

New Post: TFS error on get latest version

August 26, 2014, 1:57 am
$
0
0
Does it happen for any arbitrary project (e.g., a new simple console app project), or only for some specific one?

If the latter, does it matter where the project is checked out? I'm particularly interested to know whether you end up with a path exceeding MAX_PATH (260 characters for files, 248 for folders) somewhere.
↧

Commented Unassigned: 2.5GB memory spike opening project [1349]

August 26, 2014, 7:58 am
$
0
0
Just upgraded from the 1.0 Alpha to 1.0 Beta 2 and during the project load memory usage spikes up to 2.3GB and stays there. CPU usage fluctuating between 50-70% and this is without even doing anything.

Just to elaborate on what my solution looks like, I have an Azure Cloud Services project and 3 other Class Library projects (2 of which are linked from the Cloud Services project). I have attached my packages.json file for you (incase it could be related to a particular package).

Memory issues were the very reason I have avoided upgrading so far but according to the feedback and release notes these where *supposed* to have been resolved.

I pretty much can't use this now I am going to have to revert back to Alpha build. If there is anything else I can send you for diagnostics let me know.

**Environment**
Windows 8.1
VS2013 Premium Update 1
Comments: Same issue with latest version. After one hour memory consumption is over 6 GB.
↧

Reviewed: 1.0 Beta 2 (ago 26, 2014)

August 26, 2014, 8:10 am
$
0
0
Rated 3 Stars (out of 5) - I'm using NTVS since alpha 1 and thanks for this great plugin that transforms Visual Studio in a Node JS IDE. But I use a yoga i5 with 8GB of RAM and I see that the latest version "Beta 2 released in 7/22" gets a huge use of CPU with just a solution of NodeJS open.
↧

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

August 26, 2014, 8:40 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: So the workaround for this works well in that it avoids copying the `node_modules` hence the error goes away. However, I have linked files in my project and as part of my compile process I need those files copied to the output directory. At the moment I need to manually copy the file where it's supposed to be (sometimes I forget to do this and wonder why things are breaking!). Is there any immediate workaround *just* to stop copying the `node_modules` directory?
↧
↧

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

August 26, 2014, 9:46 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: Ah, I see. Yes, there should be a way. Instead of the above target override, do this after the import: ```xml <Target Name="NodeModulesContent" BeforeTargets="CoreCompile;BuiltProjectOutputGroup;SourceFilesProjectOutputGroup"> <ItemGroup> <NodeModulesContent Remove="@(NodeModulesContent)"/> </ItemGroup> </Target> ```
↧

New Post: TFS error on get latest version

August 26, 2014, 11:06 am
$
0
0
It's happen only for nodejstools projects (we create always a "Blank Node.js Web Application").
There is no path exceeding (i've tried also without any npm packages).

Also i saw, when i open the "npm" node in the solution explorer, a similiar error will be shown in the Output console:
TF10121: The path '' is not found or not supported. Type or select a different path.
The string must have at least one character.
Parameter name: path
↧
Search

New Post: Still Not stable

August 26, 2014, 12:09 pm
$
0
0
The .json editor, with syntax coloring and IntelliSense, is part of VS 2013. When using VS 2013 Update 2, I used to get an exception with the activity log message whenever I opened my project's package.json. I haven't seen the error since I've upgraded to Update 3.

If you see more crashes, please look in Event Viewer/Windows Logs/Application to see if there is an event for it. There will usually be one in the case of a crash, and there should be an entry that has a call stack.

If you get activity log message boxes, please look at the log in the path specified in the error message box.

In both cases, sending us that information will be of great help towards improving stability.

Thanks!
↧

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

August 26, 2014, 12:14 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".

↧
↧

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

August 26, 2014, 12:15 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".

↧

Created Unassigned: Cannot reattach debugger [1366]

August 26, 2014, 12:36 pm
$
0
0
Repro Steps:
1. Use Attach to Process to start debugging a running Node process (used remote debugging with RemoteDebug.js).
2. When debugger is attached and running, stop it (pressed stop button in VS).
3. Attempt to attach to the same process again.

Result:
An error dialog comes up: "Could not attach to Node.js process at..."
↧

Created Unassigned: Able to set breakpoints on an empty line [1367]

August 26, 2014, 12:39 pm
$
0
0
Like with a C# project, NTVS project shouldn't allow developers to put breakpoints on empty lines. This isn't high priority but looks good for fit and finish.
↧
Viewing all 4630 articles
Browse latest View live
Search