added Nuget packager for v3.1.1

[jamesmosier]

I created a nuget folder which contains the proper files for use with NuGet (ASP.NET package manager). It will pull the exact files from the appropriate folders within the master branch. Only oddity is the version number in the Package.nuspec file. I am waiting on a response from the NuGet team, but I accidentally published a package with version 3.1.1 and unfortunately they don't allow you to overwrite a version. So instead I had to make it 3.1.02, which is of course not ideal.

[nschonni]

👍 on the nuspec, but 👎 on including the binary
I was looking at http://appveyor.com com for some Windows builds, and they offer NuGet publishing as part of the CI

[jamesmosier]

So what are your thoughts on how to achieve this? I guess I was under the impression that NuGet pushing was a manual publish process, not an automated one. I need the binary to publish it correctly. Also, how is it possible to automate it without exposing the NuGet API key?

[nschonni]

You can publish if you have the binary in your path. I don't think people on other platforms (like Bower) want to pull down the extra 1.6 megs for the NuGet binary.

[jamesmosier]

I see, that makes sense. I removed it and will just manually re-add it in whenever I need to build future version(s). Does that solve the issue?

[nschonni]

Protip: If you don't squash down the commits, the EXE is still going to end up bloating the git history

[jamesmosier]

squashed the past 3 of my commits...

[glebm]

This can only be built on Windows? It uses a different version format? I won't merge this as I cannot even test it

[jamesmosier]

Correct. It is used with Visual Studio on Windows. And that's alright, I'll just use it personally instead...

[nschonni]

@glebm I believe it can be run with Mono, but it is a .Net package manager so the main user base is on Windows.

[glebm]

@nschonni I am all for supporting another package manager, so if we can build this with Mono, this can be merged. However, as it is now, I don't think I can run it because no PowerShell even with Mono?

[nschonni]

@Jamez14 if you update the <files> section to map to the existing repo location, then the powershell script shouldn't be needed (I think). Then it is just a matter or running nuget pack Package.nuspec to create the zip/package

[jamesmosier]

Cleaned up the publish.ps1 to pull from existing repo location. Also I have it pull down binaries in publish file. Not sure if this solved the issue of being able to run on Mono or not. If it's still not up to par, I'll just make it the unofficial Nuget package for bootstrap-sass. I'm currently using it at work with our app successfully.

[glebm]

@Jamez14 I started reading about Mono, Nuget, Pash, and looks for now Windows is the way to build this. In light of this, a separate repo with a Nuget build script would be best. Perhaps then it can be made official too. /cc @twbs/team

[jamesmosier]

Alright, should I create this separate repo or hold off for now?

[glebm]

@Jamez14 Go for it 👍

[cvrebert]

Perhaps Outercurve could do the packaging? They already manage the Less-based Bootstrap package: http://www.nuget.org/packages/bootstrap/

[glebm]

Didn't know about Outercurve, would be great.

[jamesmosier]

Just as an FYI, I updated my NuGet package to v3.2.0 this morning. I'm not sure if we ever came to a conclusion on this, but either way, here's the source/package links: GitHub project & NuGet package