Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 09 22:01

    csigs on hb_935_20190909220043911

    (compare)

  • Sep 09 22:00

    csigs on master

    LEGO: check in for master to te… LEGO: Merge pull request 2228 … (compare)

  • Sep 09 22:00
    csigs closed #2228
  • Sep 09 22:00
    csigs opened #2228
  • Sep 09 22:00

    csigs on hb_935_20190909220043911

    LEGO: check in for master to te… (compare)

  • Sep 06 22:00

    csigs on hb_935_20190906220033758

    (compare)

  • Sep 06 22:00

    csigs on master

    LEGO: check in for master to te… LEGO: Merge pull request 2227 … (compare)

  • Sep 06 22:00
    csigs closed #2227
  • Sep 06 22:00
    csigs opened #2227
  • Sep 06 22:00

    csigs on hb_935_20190906220033758

    LEGO: check in for master to te… (compare)

  • Sep 04 21:15

    armanio123 on master

    Updated VsSDK Preview Nuget feed Merge pull request #2226 from a… (compare)

  • Sep 04 21:15
    armanio123 closed #2226
  • Sep 04 21:06
    armanio123 opened #2226
  • Aug 29 01:39
    armanio123 closed #2127
  • Aug 29 01:39
    armanio123 commented #2127
  • Aug 29 01:33
    armanio123 assigned #2127
  • Aug 29 01:32

    armanio123 on master

    Changed how unit tests shows on… Refactored post events on unit … Address PR commnts and 2 more (compare)

  • Aug 29 01:32
    armanio123 closed #2225
  • Aug 29 01:31
    armanio123 synchronize #2225
  • Aug 29 01:18
    armanio123 synchronize #2225
Almis90
@Almis90
My visual studio continuously crashing when I opening nodejs project even without running after few minutes. It seems that vs reaches 3gb of ram without doing anything anyone know what is wrong?
IPWright83
@IPWright83
Has anyone had any issues un-installing NodejsTools? I encountered this bug (Microsoft/nodejstools#208) so decided to un-install. However even after doing so I'm still getting this error
Brendan Forster
@shiftkey
hey gang, i had a security-related question about the NodeJS tools land in my inbox (long story, don't ask). rather than writing it up here i'd like to pass it on to the team directly - what's the best way of doing that?
Andrey Kurdyumov
@kant2002
Ping @mousetraps , either here, or on GitHub
@shiftkey , see my response above
Or maybe @mjbvz could help you with your security related question
Sara Itani
@mousetraps
@Shiftkey please shoot me a mail - sitani at Microsoft com
Master Chief
@masterchief36
is there any plan on adding support for electron apps on the NodeTools for VS?
Shawn Hempel
@hempels

It would be awesome if we were able to launch using nodemon.js as a node.exe option when using "Start Without Debugging" but alternately launch without nodemon when using "Start Debugging".

Nodemon appears to be incompatible with the VS debugger. However, it's is extremely useful for "normal" development, where I typically don't attach the debugger unless I'm trying to track down a bug.

Any thoughts on how this could be achieved? Or ways to make the debugger play nice with nodemon?

Steve Lee
@SteveALee
Hi - I'm coming back to NTVS after a break and this time using in the context of Azure Apps. I'm using VS2015 and NTVS1.1 and I created a proj using the template Basic Azure Node.js Express 4 Application. I immediately hit MAX_PATH (arrrrgggggg) for Azure SDK even with a fairly short path.
What surprises me is the interactive node window in VS says node is 0.12.2 but with NVM-windows I have 5.10.0 and thus npm 3.x.x Thus I would expect to have maximally flat node_modules.
SO my question is doesn't NTVS pick up the node in use rather than use it's own?
Shawn Hempel
@hempels
@SteveALee the node process that is used is configurable in the project's properties. Right click on the project in Solution Explorer, choose Properties, then tweak the string in "Node.exe path".
Steve Lee
@SteveALee
@hempels ahah, now I remember! Thanks.
Steve Lee
@SteveALee
That worked once I pointed to my 64 bit installation
Alex Sorokoletov
@alexsorokoletov
Hi guys, can anyone help me find ApplicationId and Password for my bot? Guide shows button "Create Microsoft App Id and Password" but I don't have it in my bot properties.
Alex Sorokoletov
@alexsorokoletov
just understood this room is for the node.js tools and not node.js tools for bot builder.
sorry for the offtopics, guys
ronyrun
@ronyrun
Hello
Sorry I'm a beginner with your amazing tool
does anyone know how to run an app.js with visual studio ?
Seth Bromberger
@sbromberger
hi all
so - it appears that the node.js tools only works on Windows?
(since it appears to be an MSI installer)
Seth Bromberger
@sbromberger
ah, this doesn't appear to be for VS Code
Leo Jiapei Lin
@leoxy520
Hi, how do I deploy my nodejs app to Azure with this tool? Do I use the out of the box publish tool is VS? or there is something specific I can use from this tool ?
Sam Harwell
@sharwell
I'm getting a test discovery error using Mocha for our tests. The output to the Tests window in Visual Studio shows the following, which appears to contain a truncated message on the line starting with "Test discovery error:" (perhaps because it spans multiple lines?). Do you know if the complete error text is available somewhere?
------ Discover test started ------
Processing: J:\dev\antlr4ts\target\test\TestMocha.js
 Test discovery error: [SyntaxError: J:\dev\antlr4ts\target\test\TestMocha.js:4
Processing finished for framework of Mocha
Discovered 0 testcases.
========== Discover test finished: 0 found (0:00:00.7930225) ==========

The line in question contains the following:

const MurmurHash_1 = require('../src/misc/MurmurHash');

which was presumably produced by the following line in TestMocha.ts, the original TypeScript source file for the test in question.

import {MurmurHash} from '../src/misc/MurmurHash';
Sam Harwell
@sharwell
@BurtHarris :arrow_up: that's the error I was mentioning to you
Burt Harris
@BurtHarris
OK, I'm trying to reproduce this.
Burt Harris
@BurtHarris
Is the following message from ActivityLog.xml an issue with nodejstools?
  <entry>
    <record>606</record>
    <time>2016/10/05 19:09:34.451</time>
    <type>Error</type>
    <source>Editor or Editor Extension</source>
    <description>System.InvalidOperationException: Operation is not valid due to the current state of the object.&#x000D;&#x000A;   at Microsoft.VisualStudioTools.Project.Automation.OAProjectItem.get_Collection()&#x000D;&#x000A;   at Microsoft.VisualStudio.Web.Editor.Package.Lint.WebLinter.LinterUtilities.IsFileSupported(String fileName)&#x000D;&#x000A;   at Microsoft.VisualStudio.Web.Editor.Package.Lint.ErrorTagger.LintErrorTaggerProvider.CreateTagger[T](ITextBuffer textBuffer)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.GatherTaggers(ITextBuffer textBuffer)</description>
  </entry>
Sam Harwell
@sharwell
I was running Node.js 0.12.2
Sam Harwell
@sharwell
Updating to Node 6.7.0 fixed the problem described above.
Tushar Mathur
@tusharmath
Are these tools supported for mac ?
Marcus Besjes
@marcusbesjes
Hi, I just downloaded Node tools for visual studio and Visual Studio Code for linux, but now I don't see how to add the node tools download to the visual studio
NTVS 1.2 VS 2015.msi also seems like a windows kind of file
not sure if it's compatible with Visual Studio for linux
at extentions I see "Install from VSIX file", but that .msi file is not a VSIX file it seems
Pavel Botezat
@botezatpv
Hello, How can I install on VS 2017?
John Nicholl
@ltheONEl
Are the tools read for vs2017 yet?
Andrey Kurdyumov
@kant2002
Tools included in VS 2017. Select Node.js Workload in the installer
Lea Fox
@lfox91
hello new to vs, how does one set environment variables. I've added them to properties, built the project, and run start from npm task runner but no luck. when I type process.env in the node console they are no wear to be found.
BG Bruno
@bgbruno
@kant2002 Hello I install VS2017 on MacOS right now and I don't saw that "Select Node.js Workload in the installer" within installing or I don't see in wizard it either - Q please where it is?
Arjun Ganesan
@arjun-g
hello guys, how do i use "npm start" to debug my application instead of a startup script file ?
Andrey Kurdyumov
@kant2002
@brunogarett sorry for late response. I did not try VS on Mac yet.
But as far as I know VS on Mac is different product and likely has different work flow. I don't even sure that Node.js Tools for VS work for that edition
@arjun-g you could run '.npm start' within Node Interactive window
Arjun Ganesan
@arjun-g
@kant2002 it starts my application but i am unable to debug my application. i am developing a angular 4 application with typescript. instead of a script file to start the application i use "ng serve" in root directory to start the application. "npm start" is configured to run "ng serve"
how can I start my application with debugger ?
Andrey Kurdyumov
@kant2002
I get it.