SpecsFor.Mvc 4.4.0 is now live! This release includes improvements contributed by two very awesome individuals. E-mail addresses containing a ‘+’ character now work correctly, and you can now wait for an element on a form to become visible using the fluent interface. Read on to learn more about these changes! [more] First from Mark McCaigue: […]
Happy Friday the 13th, everyone! Remember, if you decide to go camping tonight, watch out for hockey players! Courtesy of http://crustula.com/2013/09/13/happy-friday-the-13th/ [more] Things you should check out… Woot! New (beta) version of balsamiq Mockups! This is still my favorite tool for doing UI mockups. If you’re an entrepreneur or a micro-ISV, there are a slew […]
I routinely get questions about using an IoC container, like StructureMap, with ASP.NET Identity, particularly with the way it’s set up in the default ASP.NET MVC project template. In this post, I’ll show you the quickest way to IoC-enable the starter app. [more] First, fair warning: the default MVC app template is rough. I would […]
There are two new releases on the SpecsFor front today. First, thanks to Neuhoffm again, SpecsFor.Mvc now supports radio buttons properly. You can “check” a radio button by string value or by using a strongly-typed value: SUT.FindFormFor<Task>() .Field(m => m.Title).SetValueTo("use radio buttons") //By string… .Field(m => m.Complete, "false").Click() .Submit(); SUT.FindFormFor<Task>() .Field(m => m.Title).SetValueTo("use radio buttons") .Field(m […]
AngularJS has a TON of directives. Here’s a quick list of 10 built-in AngularJS directives that I find myself using more often than any others. [more] ng-controller – Binds a section of the view to a controller. This directive is going away in AngularJS 2.0 (for good reason!), and I don’t use it as often […]
There’s a new build of SpecsFor.Mvc available on NuGet tonight! This version adds support for navigating to controllers within areas that are decorated with the RouteAreaAttribute class. Now you can do things like NavigateTo<TController>() against controllers that are in areas without using the MvcFuture’s ActionLinkAreaAttribute. My thanks go out to Neuhoffm for this improvement!