Skip to content

Set TargetPath to avoid MSB8012 warning from Visual Studio #2013

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Set TargetPath to avoid MSB8012 warning from Visual Studio #2013

wants to merge 1 commit into from

Conversation

saper
Copy link
Member

@saper saper commented Apr 18, 2016 •
edited
Loading

Well, actually it seems fine. @am11 would be cool if you could have a look at this!
@coveralls
Copy link

Coverage Status

Coverage remained the same at 78.844% when pulling 8323d7b on saper:msb8012 into dad3022 on sass:master.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.6%) to 78.288% when pulling 8323d7b on saper:msb8012 into dad3022 on sass:master.
@am11
Copy link
Contributor

am11 commented Apr 19, 2016

Does renaming TargetPath to SasscPath fix the warning? (i.e. without defining extra variables)
@saper
Copy link
Member Author

saper commented Apr 19, 2016

It might, actually my first thought was that this is just a coincidence...
@xzyfer
Copy link
Contributor

xzyfer commented May 2, 2016

@saper any action to be taken here? Please ship it or close it :)
@xzyfer xzyfer added the Build label May 20, 2016
@xzyfer
Copy link
Contributor

xzyfer commented Feb 19, 2017

VS build files have seen a lot of changes recently. Is this still relevant?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Build

5 participants

@saper @coveralls @am11 @xzyfer @glebm