Skip to content

Visual Studio 2015 not using output folder #4075

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ghost opened this issue Jul 29, 2015 · 3 comments
Closed

Visual Studio 2015 not using output folder #4075

ghost opened this issue Jul 29, 2015 · 3 comments
Labels
External Relates to another program, environment, or user action which we cannot control.

Comments

@ghost
Copy link

ghost commented Jul 29, 2015

When I create a blank node.js console app then in the project properties select "redirect to output folder" the output continues going to the default location.

You can see this in the small project at: https://github.com/kevinpas/Klib6
(look at branch AddVS15)

@ghost
Copy link
Author

ghost commented Jul 29, 2015

I the branch AddVS15 of https://github.com/kevinpas/Klib6

there is a Tools folder. In that folder there is a vs 15 project that should be used. But this is easily duplicated by creating a new project in vs 15 and trying to use the "redirect to output folder" option.

@danquirk
Copy link
Member

this is with the Node Tools for Visual Studio then? Might be an issue on that side.

@paulvanbrenk us or NTVS?

@DanielRosenwasser DanielRosenwasser changed the title Visual Studio 15 not using output folder Visual Studio 2015 not using output folder Jul 29, 2015
@ghost
Copy link
Author

ghost commented Jul 29, 2015

I think you're right this should be in Node Tools...

I had it over there but closed it to keep this one and typescript issue #4076 together.

Anyway when I run: tsc -module commonjs -t ES5 -outDir ../../Output NameValue.ts

the output shows up where I expect.

@ghost ghost closed this as completed Jul 29, 2015
@danquirk danquirk added the External Relates to another program, environment, or user action which we cannot control. label Jul 29, 2015
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
External Relates to another program, environment, or user action which we cannot control.
Projects
None yet
Development

No branches or pull requests

1 participant