Bootstrap NuGet package moving to Outercurve
As of v22.214.171.124, the Twitter.Bootstrap package will begin redirecting users to the Bootstrap package managed by the Outercurve foundation.
As of v126.96.36.199, the Twitter.Boostrap package will begin redirecting users to the Bootstrap package managed by the Outercurve foundation. The reason for this move is pretty simple. Bootstrap is a cleaner namespace since the project dropped the Twitter name a few releases ago, and Bootstrap now officially ships with the Visual Studio 2013 ASP.Net templates. So to avoid confusion on which release is "official," we've agreed to redirect everyone to the new Microsoft maintained namespace.
Here are some things to note about the transition. The new package uses a slightly different structure than mine. For instance, the CSS files are available directly in the
Content root and the
fonts directory is located in the project root. I used a bootstrap subdirectory in Content, keeping the fonts directory in the Content root. Not a huge change, but something to be aware of...or as Scott Hanselman likes to say..."who moved my cheese."
I also maintain two other related packages Twitter.Bootstrap.MVC and Twitter.Bootstrap.Less, which will not be moving over as part of this transition. I have, however, issued an update to the MVC package, which now takes a dependency on Bootstrap and references the new CSS locations in the bundling code. For those just using the MVC or Less packages, this entire transition should be seamless.