Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@paulvanbrenk
Copy link
Contributor

Various fixes we want to get into Update 3 for VS 2017

@paulvanbrenk
Copy link
Contributor Author

@digeff can you give this a spin with PZ tomorrow, ping me on what to test.

@paulvanbrenk paulvanbrenk requested a review from billti May 17, 2017 01:39
@paulvanbrenk paulvanbrenk changed the base branch from future to master May 17, 2017 21:25
Paul van Brenk added 4 commits May 17, 2017 15:00
note: adding support for the legacy webkit debugger requires changes
to the IVsDebugLaunchTargetProvider. So I decided against that for now.
// marked completed.
this.currentCommand = this.commandQueue.Take();
if (this.currentCommand != null)
if (this.commandQueue.TryTake(out var command, Timeout.Infinite) && command != null)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reason for this change? I don't see any change in semantics.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Take throws an exception when the collection is marked as completed, where TryTake returns false. There was a racecondition I saw a couple of times between Dispose and Take being called.

// We check the registry to see if any parameters for the node.exe invocation have been specified (like "--inspect"), and append them if we find them.
var nodeParams = NodejsProjectLauncher.CheckForRegistrySpecifiedNodeParams();
if (!string.IsNullOrEmpty(nodeParams))
{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming setupInstance.GetInstallationPath() can return a path with spaces, and this is all just being concated with args into one long string, does this require any quoting?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And possibly all the other paths we handle here....

@digeff Thoughts?

$@"Microsoft\VisualStudio\NodeAdapter\{visualStudioInstallationInstanceID}\out\src\nodeDebug.js""");
}

var target = vsDebugTargetInfo.bstrExe;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can the user not specify the working directory to use in the NTVS property pages for the project?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is the open folder scenario though. We don't use the project properties there.

Copy link
Member

@billti billti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look into the comments I left. If no issue, looks good to me.

@paulvanbrenk paulvanbrenk merged commit 1c02088 into microsoft:master May 19, 2017
@paulvanbrenk paulvanbrenk deleted the 15.3rollup branch May 19, 2017 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.