New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy an official NuGet package #16692

Closed
supergibbs opened this Issue Jun 23, 2015 · 62 comments

Comments

Projects
None yet
@supergibbs
Contributor

supergibbs commented Jun 23, 2015

I know this has been brought up many times but Bootstrap can currently be installed via a GitHub download/clone, CDN, Bower, npm, Composer and Meteor. Adding NuGet would be a helpful addition.

The best NuGet Bootstrap Package is managed by Outercurve Foundation. Unfortunately their package has had issues in the past and is often out of date (still on v3.3.4 currently).

@mdo suggested I open an issue to see how much interest there is. If this is something the core team would consider, I believe it could be fully automated with the addition of a couple files. I'd be happy to take on setting it up.

@mdo

This comment has been minimized.

Member

mdo commented Jun 24, 2015

Yeah, if there's enough support out there, we can consider adding it to our release process—if it's not too much of a nuisance that is. Having someone own it is helpful, but a streamlined process that keeps things up to date for folks is always advantageous.

@sandeepmovva

This comment has been minimized.

sandeepmovva commented Jun 24, 2015

+1

@aaronhudon

This comment has been minimized.

aaronhudon commented Jun 24, 2015

1++

@berwyn

This comment has been minimized.

berwyn commented Jun 24, 2015

+1

@ghost

This comment has been minimized.

ghost commented Jun 24, 2015

+1 (I would also add a similar request for the sass port)

@jsheely

This comment has been minimized.

jsheely commented Jun 24, 2015

+1 Surprised this is not already a thing.

@mdo

This comment has been minimized.

Member

mdo commented Jun 24, 2015

None of us on the core team are really on Windows machines, so it hasn't come up for us. Previously someone else was managing it. If we add this, we'll likely want to snag that package name from those folks. Anyone want to try to spearhead this for us?

@supergibbs

This comment has been minimized.

Contributor

supergibbs commented Jun 24, 2015

No prob, I'll shoot them a message. I was looking into https://www.myget.org/ too. Seems like an easy way to publish not only NuGet but npm and bower too. @mdo made it sound like a pretty manual process.

@chakrabar

This comment has been minimized.

chakrabar commented Jun 24, 2015

VS 2015 is using bower, so it should be already ready for that. But not all professional developers are going to jump to VS 2015 immediately. So, NuGet will be really helpful.
And ideally, the process should not be complex or manual!

@vtforester

This comment has been minimized.

vtforester commented Jun 24, 2015

+1

How would you set up the folder structure for the package? Or would you keep the same structure that Outercurve uses?

@ahsteele

This comment has been minimized.

ahsteele commented Jun 24, 2015

+1
Having an official NuGet package would be a big win.

@jraq

This comment has been minimized.

jraq commented Jun 24, 2015

+1

Nuget would be awesome. @chakrabar the VS 2015 vnext web application project will be using bower, but every other web application project will still use nuget in VS 2015. I agree that not everyone will be jumping to upgrade their projects or visual studio immediately.

@gichamba

This comment has been minimized.

gichamba commented Jun 24, 2015

+10 here

@ericberens

This comment has been minimized.

ericberens commented Jun 24, 2015

+1

1 similar comment
@druzzo

This comment has been minimized.

druzzo commented Jun 24, 2015

+1

@devdelimited

This comment has been minimized.

devdelimited commented Jun 24, 2015

+less #pleasepleasepleasepleasepleaseplease

@chakrabar

This comment has been minimized.

chakrabar commented Jun 24, 2015

@jraq agreed. An official NuGet will still be awesome for non-vNext web projects on VS 2015.
I wonder what would be the percentage of developers using vNext projects in next 6 months, more than 20% ?

@BramVercaigne

This comment has been minimized.

BramVercaigne commented Jun 24, 2015

+1

@jraq

This comment has been minimized.

jraq commented Jun 24, 2015

@chakrabar I don't know what the percentage would be, but I believe since VS 2015 is already in release candidate it will be released before vnext. I follow the community standups that @shanselman does for vnext and it sounds like they are planning to release vs 2015 before vnext, but I'm not 100% sure. I know this is probably a stretch and I'm not sure if they will see these github comments, but it would be cool if @shanselman or @DamianEdwards could comment. I see them the most in the standups

@jerone

This comment has been minimized.

Contributor

jerone commented Jun 24, 2015

👍

2 similar comments
@turchenkoalex

This comment has been minimized.

turchenkoalex commented Jun 24, 2015

+1

@jenscski

This comment has been minimized.

jenscski commented Jun 24, 2015

+1

@stigur

This comment has been minimized.

stigur commented Jun 24, 2015

Offical - would be much better :)

@cubitouch

This comment has been minimized.

cubitouch commented Jun 24, 2015

+1 :)

@MichaelPetrinolis

This comment has been minimized.

MichaelPetrinolis commented Jun 24, 2015

+1

3 similar comments
@Sycro

This comment has been minimized.

Sycro commented Jun 24, 2015

+1

@heymega

This comment has been minimized.

heymega commented Jun 24, 2015

+1

@akrohn

This comment has been minimized.

akrohn commented Jun 24, 2015

+1

@grprakash

This comment has been minimized.

grprakash commented Jun 25, 2015

VS 2015 supports bower, it will take years for all the customers to upgrade to it. (One of my clients are still in 2010). It would be great to have a official nuget package

@Alex-Sokolov

This comment has been minimized.

Alex-Sokolov commented Jun 25, 2015

+1

1 similar comment
@itomek

This comment has been minimized.

itomek commented Jun 25, 2015

+1

@NelsonReis

This comment has been minimized.

NelsonReis commented Jun 26, 2015

+1

2 similar comments
@gsferreira

This comment has been minimized.

gsferreira commented Jun 26, 2015

+1

@rmarinho

This comment has been minimized.

rmarinho commented Jul 1, 2015

+1

@shanselman

This comment has been minimized.

shanselman commented Jul 2, 2015

Sorry, better to use Bower or npm, that's what they are for. NuGet is for
compiled .NET binaries.

On Wed, Jul 1, 2015 at 8:14 AM, Rui Marinho notifications@github.com
wrote:

+1


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

Scott Hanselman
Donate to fight diabetes: http://hnsl.mn/fightdiabetes

@jraq

This comment has been minimized.

jraq commented Jul 3, 2015

@shanselman I built an asp.net 4.6 mvc project in vs 2015 rc and it uses nuget to pull down bootstrap 3.0 in the packages.config. In the last standup, I believe @DamianEdwards said vnext won't be in rc until November. If I'm wrong let me know. My company use nuget for bootstrap right now. When we update our projects to vnext this winter and start using bower it would be less stressful for me (and QA) that we are using the latest version of bootstrap.

p.s. I love this developers life

@grprakash

This comment has been minimized.

grprakash commented Jul 3, 2015

@shanselman I second @jraq. I still have clients using VS 2010 and don't see them upgrading to VS 2015 anytime soon. Till most of the people upgrade, having a official nuget package would be great

@moyuling

This comment has been minimized.

moyuling commented Jul 3, 2015

+1

@drmcclelland

This comment has been minimized.

drmcclelland commented Jul 12, 2015

+1 - yes please!

@natalka01

This comment has been minimized.

natalka01 commented Jul 21, 2015

just another +1

@jimdavis1026

This comment has been minimized.

jimdavis1026 commented Jul 22, 2015

A nuget package for Bootstrap would be used a lot. Consider this a vote for it. +1

@Eonasdan

This comment has been minimized.

Eonasdan commented Jul 22, 2015

This is a little late the game here guys. Nuget is going to stop delivering front end packages like this to all new .Net 5+ projects (MVC 6, Webforms, etc). All .Net developers are going to have to use bower to add front-end packages in the future.

See this: NuGet/Home#930

@supergibbs

This comment has been minimized.

Contributor

supergibbs commented Jul 22, 2015

@Eonasdan yes this has been brought up but there will a long transition to the new system so there is no harm in supporting a nuget distro in the mean time.

Not an automated process yet but currently up to date with v3.3.5:
https://www.nuget.org/packages/Bootstrap/
https://www.nuget.org/packages/Bootstrap.Less/

@sirkirby

This comment has been minimized.

sirkirby commented Jul 22, 2015

I'll plan to redirect https://www.nuget.org/packages/Twitter.Bootstrap.Less/ to Bootstrap.Less with the next update...Did the same thing when switching from Twitter.Bootstrap to Bootstrap when Outercurve took over the maintenance. Issue referenced above. thanks @supergibbs for the heads up.

@Untit1ed

This comment has been minimized.

Untit1ed commented Jul 30, 2015

+1.
Outdated bootstrap packages was one of the reasons I switched to bower from NuGet.
I agree it's a little too late now, but better late than never.

@taspeotis

This comment has been minimized.

taspeotis commented Aug 5, 2015

+1 although I've never had a problem with the Outercurve managed NuGet package.

@ichpuchtli

This comment has been minimized.

ichpuchtli commented Aug 13, 2015

+1

@cvrebert cvrebert added the v3 label Aug 19, 2015

@tiesont

This comment has been minimized.

Contributor

tiesont commented Aug 30, 2015

@supergibbs Not sure if you're managing the package, but the 3.3.5 version does not include the Glyphicon font files. Is this intentional? I notice they're still referenced in the CSS file, so...

@supergibbs

This comment has been minimized.

Contributor

supergibbs commented Aug 30, 2015

@tiesont I just checked and it seems fine to me. Make sure you are using the official packages; there are lots of others.

https://www.nuget.org/packages/bootstrap
https://www.nuget.org/packages/bootstrap.less

The font files are included in both. In the less package, you may have to change the font path in the variables.less file depending on your setup.

Let me know if it's still not working for you!

@tiesont

This comment has been minimized.

Contributor

tiesont commented Aug 30, 2015

@supergibbs True enough. Should have checked the .nupkg first.

For whatever reason, when I updated from the 3.3.4 version, the font files were not copying over. Using Update-Package –reinstall bootstrap, the fonts got copied in. Probably just something weird about this project. Thanks!

@cvrebert cvrebert added this to the v3.3.6 milestone Oct 13, 2015

@cvrebert

This comment has been minimized.

Member

cvrebert commented Oct 13, 2015

Fixed by #16710.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment