Stack Empty Exception - caused by "Bootstrap().Dropdown"

[shawty]

Synopsis

Creating a test harness to learn the library, using samples from website/docs causes a "Stack Empty Exception" to be thrown.

Software Used

Visual Studio 2013 Ultimate (Update 4) Windows 7 X64 Bootstrap 3.1.1 (NuGet Package) FluentBootstrap.Mvc (Current NuGet Package) .NET Runtime V4 IIS7.5

Hardware Used

Intel Core I7 3ghz 4 core w hyper threading enabled

To Reproduce

• 1) Fire up VS2013, start a new Web Application project (Make sure it's the web application for VS2013 - NOT The MVC4 template under the VS2012 subtree.
• 2) Make sure you create an EMPTY web application, and add MVC and Web API capabilitys
• 3) Use NuGet and add the current Bootstrap, FluentBootStrap & FluentBootStrap.Mvc packages
• 4) Create a simple controller called 'HomeController', add an 'Index' action and have it return a view
• 5) When creating the view, choose to use a layout file, and let VS scaffold it for you
• 6) Add the following line (Copied from the docs) to the view and run the app [Note: everything works] - @Html.Bootstrap().Alert(AlertState.Info, "Warning", "Yikes, this is a warning.")
• 7) Add the following line (Copied from the docs) to the view and run the app [Note: the exception is seen] - @Html.Bootstrap().Dropdown("My Dropdown").SetSize(ButtonSize.Xs).SetState(ButtonState.Warning)

  Supporting Materials

YSOD as produced when running the solution

View that causes the above YSOD

_layout.cshtm (Used to produce full view)

Resolution

Removal of the line used to create the dropdown from the view and re-running prevents the empty stack exception.

A project configured for NuGet package restore can be zipped and provided if requested.

[daveaglick]

Thanks again for the detailed issue. I am able to reproduce. It appears that just doing @Html.Bootstrap().Dropdown("My Dropdown") is enough to throw the exception.

The problem is that certain components (such as Dropdown) check an internally maintained stack of FluentBootstrap components during rendering. For example, the Dropdown checks if it's in a Navbar. In all my tests, I've apparently always wrapped these components in something else (so there's already something on the stack). A simple empty check should do the trick.

Stupid mistake - a fix (and test) should be available in source and on NuGet momentarily.

[shawty]

No probs, will wait 5 mins then will do a NuGet update and re-test.

[daveaglick]

Better wait 10 - AppVeyor can sometimes take a few... :)

[shawty]

NuGet upgraded, can confirm issue resolved.

[daveaglick]

Awesome, thanks.