erichexter / twitter.bootstrap.mvc

nuget package to make bootstrap easy with mvc4
Apache License 2.0
248 stars 134 forks source link

Update to use twitter.bootstrap 3 #98

Closed serra closed 9 years ago

serra commented 10 years ago

With #97 we fixed the dependency on TB 2.3.2; we should investigate what would be necessary to support TB 3.0.

Note: I've read that VS 2013 will come with a twitter bootstrap theme too; might be worth a small investigation.

schellem commented 10 years ago

I'm hoping to get some time to investigate this a bit further and also use this as an opportunity to get some GitHub 'workflow' and NuGet packaging experience as well.

Anyway there were a handful of class names that changed in TB 3.0.0 along with CSS\JS file name\location changes.

Do I just click the + link to 'fork' the project and that makes a branch for me?

erichexter commented 10 years ago

I just pushed the packages to the main feed. it may take a few minutes for the process to complete.

Eric Hexter

blog | http://Hex.LosTechies.com info | http://www.linkedin.com/in/erichexter

On Thu, Oct 10, 2013 at 7:17 AM, schellem notifications@github.com wrote:

I'm hoping to get some time to investigate this a bit further and also use this as an opportunity to get some GitHub 'workflow' and NuGet packaging experience as well.

Anyway there were a handful of class names that changed in TB 3.0.0 along with CSS\JS file name\location changes.

Do I just click the + link to 'fork' the project and that makes a branch for me?

— Reply to this email directly or view it on GitHubhttps://github.com/erichexter/twitter.bootstrap.mvc/issues/98#issuecomment-26048523 .

serra commented 10 years ago

@schellem - yes that's the typical way to start a fork. See this help page for more on forking, hack away, push to your own repo and open a pull request. Just let me know if you need some more help.

schellem commented 10 years ago

Reference for upgrading to TB 3.0.0 Migration Guide and Upgrade Tool

kmiloaguilar commented 9 years ago

@erichexter with the pull request #103 this one is fixed.