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

Edited Unassigned: Publish to Azure not working [1372]

August 28, 2014, 1:13 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://i57.tinypic.com/1h2mty.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?
↧
Search

Edited Unassigned: Publish to Azure not working [1372]

August 28, 2014, 1:14 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://i57.tinypic.com/1h2mty.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://i62.tinypic.com/f3dm5w.png)

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

Edited Unassigned: Publish to Azure not working [1372]

August 28, 2014, 1:14 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://i57.tinypic.com/1h2mty.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 is stuck like

![Image](http://i62.tinypic.com/f3dm5w.png)

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

Reviewed: Latest dev build (Aug 28, 2014)

August 28, 2014, 4:49 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? --- Additional information --- I set a breakpoint and followed the code execution into a couple of our modules but VS2013.3 soon crashed with: Application: devenv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException Stack: at Microsoft.NodejsTools.Analysis.UnionComparer.Equals(Microsoft.NodejsTools.Analysis.AnalysisProxy, Microsoft.NodejsTools.Analysis.AnalysisProxy) at Microsoft.NodejsTools.Analysis.AnalysisSetDetails.AnalysisSetTwoUnion.Add(Microsoft.NodejsTools.Analysis.AnalysisProxy, Boolean ByRef) at Microsoft.NodejsTools.Analysis.Analyzer.TypedDependencyInfo.AddType(Microsoft.NodejsTools.Analysis.AnalysisProxy) at Microsoft.NodejsTools.Analysis.TypedDef
↧

Reviewed: Latest dev build (Aug 28, 2014)

August 28, 2014, 4:51 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? --- Additional information --- I set a breakpoint and followed the code execution into a couple of our modules but VS2013.3 soon crashed with http://pastebin.com/EHhLmqk5.
↧
↧

Commented Unassigned: Publish to Azure not working [1372]

August 28, 2014, 9:31 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://i57.tinypic.com/1h2mty.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 is stuck like

![Image](http://i62.tinypic.com/f3dm5w.png)

Any idea's what's going on here?
Comments: Can you copy/paste Tools -> Node.js Tools -> Diagnostic Info (this should have the exception details)?
↧

Created Issue: Basic Azure Express template gives "One or more errors occurred". [1373]

August 28, 2014, 4:17 pm
$
0
0
If the user doesn't have the Azure SDK installed we give a terse message. We should instead check to see if the component is present and if not give a nice message.

```
<entry>
<record>282</record>
<time>2014/06/02 18:45:52.821</time>
<type>Error</type>
<source>VisualStudio</source>
<description>CreateInstance failed for package [CommonAzureToolsPackage]</description>
<guid>{1E863AE9-93F6-42FD-A301-D3391F876208}</guid>
<hr>80070002</hr>
<errorinfo>Could not load file or assembly 'Microsoft.VisualStudio.WindowsAzure.Utilities.1.0, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.</errorinfo>
</entry>
```
↧

Commented Feature: JS-style comment autocompletion missing? [880]

August 28, 2014, 7:35 pm
$
0
0
I've been trying out NTVS, and I can't figure out how to get JS-style comments to autocomplet in .js files that are part of an NTVS project. I have Resharper and VS Web Essentials installed as well.

When I'm editing a JavaScript file, I want to type this:

```
/**
```

And the editor should autocomplete (where the pipe is the cursor):

```
/** | */
```

Now, I should be able to press enter as many times as I want when I edit this comment, and it should add *s at the beginning of the line, indented as appropriate.

When I'm editing .ts files and .js files that are not part of an NTVS project (e.g. as part of a website), then this desired behavior occurs. However, I can't figure out how to get it to work for .js files in an NTVS project. It seems like a pretty minor thing to be missing but it's actually pretty irritating to have to manually indent and align all of the *s properly to fit the style guidelines.

Is there an option that I'm missing somewhere or is this not supported right now? Thanks for your help.

Comments: I can not see tip of comment description of function node.JS. please check out attachment file.
↧
Search

Commented Unassigned: Publish to Azure not working [1372]

August 29, 2014, 1:20 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://i57.tinypic.com/1h2mty.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 is stuck like

![Image](http://i62.tinypic.com/f3dm5w.png)

Any idea's what's going on here?
Comments: Diagnostics for preview scenario
↧
↧

Commented Unassigned: Publish to Azure not working [1372]

August 29, 2014, 1:21 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://i57.tinypic.com/1h2mty.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 is stuck like

![Image](http://i62.tinypic.com/f3dm5w.png)

Any idea's what's going on here?
Comments: Diagnostics for publish scenario (weirdly, I noticed the publishURL setting is <undefined>)
↧

Commented Unassigned: Publish to Azure not working [1372]

August 29, 2014, 1:25 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://i57.tinypic.com/1h2mty.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 is stuck like

![Image](http://i62.tinypic.com/f3dm5w.png)

Any idea's what's going on here?
Comments: Also, one other small quirk I have noticed. When I am prompted for authentication to Azure I am getting like 3-4 login pages thrown up at the same time.
↧

New Post: Debug js code running in pure v8

August 29, 2014, 4:37 am
$
0
0
Hi all,

I have a custom (native, c++) application which embeds v8 and executes some js scripts.
As I've read that NTVS uses the native v8 debug protocol, I was wondering if it's possible to use it to debug the js code I run in my app through the embedded v8 engine.
To set things up, what I have in mind is:
  • enable v8 debugging in my application as explained on v8 documentation
  • load the js files I use in my application into a NTVS project
  • run my application locally and attach the NTVS debugger in "Local Attach" mode as described here, specifing my executable with debugging on, instead of node.exe
Any chance this is going to work?
I simply don't know if there are any node-specific mechanism needed by NTVS for the debugger to work.

Thank you in advance,
ricky
↧

New Post: Cannot run generated unit test

August 29, 2014, 6:28 am
$
0
0
I have created new NTVS project and added new Mocha JS unit test from template:
var assert = require('assert');

describe('Test Suite 1', function() {
    it('Test 1', function() {
        assert.ok(true, "This shouldn't fail");
    })

    it('Test 2', function() {
        assert.ok(1 === 1, "This shouldn't fail");
        assert.ok(false, "This should fail");
    })
})
Run it from VS2013. Jasmine test runner was launched in a browser with obvious error: "Uncaught ReferenceError: require is not defined". Indeed browser knows nothing about require().
So it doesn't work out of the box. How it is supposed to be run?
↧
↧

New Post: Cannot run generated unit test

August 29, 2014, 9:53 am
↧

New Post: Debug js code running in pure v8

August 29, 2014, 12:51 pm
$
0
0
It's not something that we've tried, and it's not officially supported - but provided that the version of V8 you embed talks the same protocol as the one used by Node, I don't see why it wouldn't work. Might be worth a try.
↧
Search

Edited Issue: Property values are shown in bold [809]

August 29, 2014, 2:06 pm
$
0
0
The values in the property window should not be bold.
↧

Created Unassigned: TestAdapter probablly fails when /InIsolation is used [1374]

August 29, 2014, 8:13 pm
$
0
0
Node.js Tools for VS appears to have the same problem as PTVS:
https://pytools.codeplex.com/workitem/2643

Copy pasted from there:
If vstest.console.exe is passed /InIsolation or /EnableCodeCoverage the PTVS Test Adater fails in TestExecutor.cs:RunTests from these sequence of events:
◾Due to Isolation being used the Test Adapter is running inside vstest.executionengine*.exe.
◾The execution engine gets passed a /parentProcessId argument, but that PID isn't Visual Studio.
◾VisualStudioApp.FromCommandLineArgs() returns a non-NULL instance of VisualStudioApp.
◾InterpreterOptionsServiceProvider.GetService() receives the non-NULL instance.
◾InterpreterOptionsServiceProvider.GetService calls app.DTE which returns NULL due to the parent process not being VisualStudio.
◾InterpreterOptionsServiceProvider.GetService passes in NULL to "new ServiceProvider" which throws an ArgumentNullException and the PTVS Test Adapter ends up crashing as a result.

If we avoid trying to create the "new ServiceProvider" then the Test Adapter successfully runs the Python test cases.

This is with VS2013 and PVTS 2.1 RC. The core of the problem seems to stem from FromCommandLineArgs() returning a non-null VisualStudioApp when the .DTE property will return NULL when asked.

Fyi,
Bill


↧
↧

New Post: Cannot run generated unit test

August 30, 2014, 2:58 am
$
0
0
Oh, thank you. I didn't realize that running tests from test explorer and from unit test sessions leads to different behavior.
↧

Reviewed: 1.0 Beta 2 (Sep 02, 2014)

September 2, 2014, 9:55 am
$
0
0
Rated 2 Stars (out of 5) - This project WAS awesome until you totally borked intellisense. I understand wanting to make things more efficient for larger projects, but this update renders the IDE completely useless as an editor. Still great for debugging and such, but please bring back the awesome power of the built-in in intellisense engine.
↧

Reviewed: 1.0 Beta 2 (Sep 02, 2014)

September 2, 2014, 9:03 pm
$
0
0
Rated 3 Stars (out of 5) - Not a big fan of the new, faster and (unfortunately) semi-crippled intellisense engine. Paren and brace matching, snippets, VSDOC comments, and more are all borked for me. Bummer.
↧
Viewing all 4630 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>