WIP: Paket

[forki]

Doesn't work yet

[forki]

Waiting for fsprojects/FSharp.Formatting#197 to get fixed

[forki]

@vasily-kirichenko @dungpa
what do you think?

[dungpa]

Why does Paket generate two new fsx files in seperate folders? We probably want only one depending on the framework we target.

[forki]

this content adding stuff is still open in Paket. fsprojects/Paket#157
will fix this manually

[dungpa]

This is cool. Look much easier to maintain in the long term.

There are two new warnings about strong name FSharp.Core at https://ci.appveyor.com/project/dungpa/visualfsharppowertools/build/1.5.0-a1409231530/messages. Could you take a look?

[forki]

There are two new warnings about strong name FSharp.Core

Should be fixed

[dungpa]

All good.

Another question: how NuGet target can find NuGet binaries for creating a package now https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/build.fsx#L157-L173?

[ovatsus]

You need to add NuGet.CommandLine to the paket.dependencies file. See fsprojects/FSharp.Data@86dfbf2

[forki]

I always forget that one ;-)

Will add it to the auto-transform-tool and update PR.

2014-09-24 13:56 GMT+02:00 Gustavo Guerra notifications@github.com:

You need to add NuGet.CommandLine to the paket.dependencies file. See
fsprojects/FSharp.Data@86dfbf2
fsprojects/FSharp.Data@86dfbf2

—
Reply to this email directly or view it on GitHub
#713 (comment)
.

[dungpa]

@ovatsus @forki Thank both.

[forki]

done

[dungpa]

Thanks a lot. We would love to have GitHub release target that works beautifully on Paket :).

[forki]

very cool.

Will send PR soon.

[forki]

see #720