Yeah that makes sense. I guess forcing people to use this isn't such a bad
idea given how important it is.

If they really object they can manually change each time.

Robert Moore
+61 400 777 763
Readify | Senior Consultant

On 10/11/2013, at 10:59 PM, Jake Ginnivan <notifications@github.com> wrote:

In src/GitHubFlowVersion/install.ps1:

> @@ -0,0 +1,34 @@
> +param($installPath, $toolsPath, $package, $project)

The problem is currently you have to run it from a version specific
directory in the packages folder, also that breaks package restore if you
build through it. I think putting in that dir by default, then people can
move before they commit?
Sent from my Windows Phone ________________________________ From: Robert
Moore<mailto:notifications@github.com <notifications@github.com>> Sent:
ý10/ý11/ý2013 14:32 To: JakeGinnivan/GitHubFlowVersion<
mailto:GitHubFlowVersion@noreply.github.com<GitHubFlowVersion@noreply.github.com>>
Cc: Jake Ginnivan<mailto:jake@ginnivan.net <jake@ginnivan.net>> Subject:
Re: [GitHubFlowVersion] Copy to tools folder on install
(#31<https://github.com/JakeGinnivan/GitHubFlowVersion/pull/31>)
In src/GitHubFlowVersion/install.ps1:
 @@ -0,0 +1,34 @@ +?param($installPath, $toolsPath, $package, $project)
If people want to do something difference should we let them move it and
leave this here or should we expose this as a function they can call from
the NuGet Package Manager console as a command e.g.
Install-GitHubFlowToolsDir. In my minds eye I see other commands in the
future that do things like inject stuff into .csproj files to patch
assembly versions and stuff like that. — Reply to this email directly or
view it on GitHub<
https://github.com/JakeGinnivan/GitHubFlowVersion/pull/31/files#r7548749>.

—
Reply to this email directly or view it on
GitHub<https://github.com/JakeGinnivan/GitHubFlowVersion/pull/31/files#r7548802>
.