Cannot create NuGet package with version "1.0.0"

[SimonHohenadl]

I currently have the problem that I cannot build a NuGet package for Machine.Fakes with version "1.0.0", because Fake normalizes the version to "1", which is not accepted by nuget.exe.

I suppose there are other ways to solve this, but I don't see why FAKE should tamper with the version supplied by the user anyway. If I want the version normalized, I can always call the NormalizeVersion function in my build script.

[forki]

It's breaking but I think you're right.
However the breaking change should be no real problem.
If package version is invalid it can't be uploaded and the build will fail.
In this case we can use NormalizeVersion as you suggested.

[SimonHohenadl]

Right, I hadn't thought of the fact that it would be a breaking change.
Any idea when you will be able to release this?

[forki]

Simon it is already released on nuget.

[SimonHohenadl]

Wow, you release faster than I can read my email. :-)
Thanks!

[forki]

It's deployed via push to master.
That's called "continous deployment". I heard you gave a session about this at devspace ;-)

[SimonHohenadl]

Next time, you better give that session. :-)

[funnelweb]

@forki - what's the end-to-end for your continuous deployment setup? I guess you use FAKE itself, but which CD server do you use etc.? I've not set up a CD system before.

Could we reuse the same setup/server etc. for the F# compiler, fsharpx and fsharpbinding? It would be a huge step forward if we did, e.g. we could build linux packages this way, and nuget packages based of the F# open source (e.g. for F# compiler-as-a-service).

[forki]

Im using http://teamcity.codebetter.com - you can easily get an account.

See http://teamcity.codebetter.com/viewType.html?buildTypeId=bt335&tab=buildTypeStatusDiv for the "Fake self build"

I'd happy to help. Maybe we should discuss this in a issue or the mailing list.

[funnelweb]

OK, lets continue the discussion here: fsharp/fsharp#48