MSBuild.build setParams "my.sln", then in
setParamsI do set the
PublishDir, but that setting will be relative to each project and I want it to be in
'node' is not recognized as an internal or external command, operable program or batch file.
Ok looking at the source code, there is indeed a parameter called YarnFilePath. So that takes care of specifying the path to yarn. Now from @matthid 's advice, I correctly specified, albeit manually, the path to node and running the script worked.
However, I am now struggling with dynamically adding the node path to PATH:
Environment.setEnvironVar "PATH" nodeDirPath
because when I then run
let newEnvPath = Environment.pathDirectories newEnvPath |> Seq.iter(fun x -> Trace.log (sprintf "----->%s" x))
the new path is not there
YarnFilePath(or we need to update the module to support this scenario)
On a separate but related topic, in my
Even though I've deleted the
.fake folder and the
build.fsx.lock, the latest version of "Node.js.redist" is being downloaded. What is the correct way to pin the version?
dotnet tool install fake-cli --too-pathto install fake. I also have my nuget packages defined in build.fsx as above. Now let's say I add a new Nuget package, what is the prescribed way to get the new package because running
fake run builddoesn't do it. I know that deleting build.fsx.lock and running the previous command will work but I was wondering if there is a better way