@pblasucci what do we do with this?

@forki Personally, it seems a bit "off" to me. I understand wanting to speed up incremental builds. But I strongly believe the Release target should work off of a fully clean rebuild. Also, I've never found the perf difference between "Build" and "Rebuild" to be worth the headache of having separate commands. What are your thoughts?

Yeah I think we should not merge it. I mean it's a good idea for some use
cases but I think we should play it safe for the scheduling process.

On Aug 10, 2016 2:39 PM, "Paulmichael Blasucci" notifications@github.com
wrote:

@forki https://github.com/forki Personally, it seems a bit "off" to me.
I understand wanting to speed up incremental builds. But I strongly believe
the Release target should work off of a fully clean rebuild. Also, I've
never found the perf difference between "Build" and "Rebuild" to be worth
the headache of having separate commands. What are your thoughts?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#260 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNIi892Qd8FGaHhe7ArwHWNzI2Pqsks5qecaVgaJpZM4I2NX6
.

Agreed. Also, when you consider the way certain things (in VS/MSBuild) get cached, this doesn't feel like a "safe default".

Closing as "too specialized".

@Chicker we still really appreciate that you took the time and effort. It's not a bad idea. I hope you can understand the reasoning.