code 128 vb.net free <%= Html.RouteLink("WDG0003", "special-widget-route", new { widgetCode = "WDG-0003" }, null) %> in VS .NET

Create Code 128A in VS .NET <%= Html.RouteLink("WDG0003", "special-widget-route", new { widgetCode = "WDG-0003" }, null) %>

This code will look for a route with the name special-widget-route. You re unlikely to need to use this technique unless the URL generated by routing isn t the desired one. Try to solve the issue by altering route ordering or with route constraints. Use RouteLink as a last resort. Sometimes you need to obtain a URL, but not for the purposes of a link or form. This often happens when you re writing Ajax code and you need to set the request URL. The UrlHelper class can generate URLs directly; it s used by the ActionLink method and others. Here s an example:

When compared with the rest of the ASP.NET MVC Framework, testing routes isn t easy or intuitive because a number of abstract classes need to be mocked out before route testing is possible. Luckily, MvcContrib has a nice fluent route-testing API that we can use to make testing these routes easier. But before we look at that, listing 16.10 demonstrates how you d test a route with NUnit and Rhino Mocks.

using using using using using System.Web; System.Web.Routing; NUnit.Framework; NUnit.Framework.SyntaxHelpers; Rhino.Mocks;

namespace BadRoutingTestExample.Tests { [TestFixture] public class NaiveRouteTester { [Test] public void root_matches_home_controller_index_action() { const string url = "~/"; var request = MockRepository .GenerateStub<HttpRequestBase>(); request.Stub(x => x.AppRelativeCurrentExecutionFilePath) .Return(url).Repeat.Any(); request.Stub(x => x.PathInfo)

.Return(string.Empty).Repeat.Any(); var context = MockRepository .GenerateStub<HttpContextBase>(); context.Stub(x => x.Request) .Return(request).Repeat.Any(); RouteTable.Routes.Clear(); MvcApplication.RegisterRoutes(RouteTable.Routes); var routeData = RouteTable.Routes.GetRouteData(context); Assert.That(routeData.Values["controller"], Is.EqualTo("Home")); Assert.That(routeData.Values["action"], Is.EqualTo("Index")); } } }

If all our route tests looked like listing 16.10, nobody would even bother testing. Those specific stubs on HttpContextBase and HttpRequestBase weren t lucky guesses either; it took a peek inside Red Gate s Reflector tool to find out what to mock. This isn t how a testable framework should behave! Luckily, we don t have to deal with this if we re smart. MvcContrib s fluent routetesting API makes everything a lot easier. Listing 16.11 is the same test, using MvcContrib.

using System.Web.Routing; using MvcContrib.TestHelper; using NUnit.Framework; namespace BetterRouteTestExample.Tests { [TestFixture] public class FluentRouteTester { [Test] public void root_matches_home_controller_index_action() { MvcApplication.RegisterRoutes(RouteTable.Routes); "~/".ShouldMapTo<HomeController>( Invokes ShouldMapTo x => x.Index()); extension method } } }

This is all done with the magic and power of extension methods and lambda expressions. Inside MvcContrib there s an extension method on the string class that builds up a RouteData instance based on the parameters in the URL. The RouteData class has an extension method to assert that the route values match a controller and action B. You can see from listing 16.11 that the controller comes from the generic type argument to the ShouldMapTo<TController>() method. The action is then specified

with a lambda expression. The expression is parsed to pull out the method call (the action) and any arguments passed to it. The arguments are matched with the route values. See the code for yourself on the MvcContrib site: http://mng.bz/rHBX. Now it s time to apply this to our widget store s routing rules and make sure that we ve covered the desired cases. We do that in listing 16.12.

using using using using System.Web.Routing; StoreExample.Controllers; MvcContrib.TestHelper; NUnit.Framework;

namespace StoreExample.Tests { [TestFixture] public class ComplexRouteTests Uses NUnit { [TestFixtureSetUp] public void FixtureSetup() { RouteTable.Routes.Clear(); MvcApplication.RegisterRoutes(RouteTable.Routes); } [Test] public void root_maps_to_home_index() { "~/".ShouldMapTo<HomeController>(x => x.Index()); }

[Test] TestHelper public void privacy_should_map_to_home_privacy() { "~/privacy".ShouldMapTo<HomeController>(x => x.Privacy()); } [Test] public void widgets_should_map_to_catalog_index() { "~/widgets".ShouldMapTo<CatalogController>(x => x.Index()); } [Test] public void widget_code_url() { "~/WDG-0002".ShouldMapTo<CatalogController>( x => x.Show("WDG-0002")); } [Test] public void widget_buy_url() { "~/WDG-0002/buy".ShouldMapTo<CatalogController>( x => x.Buy("WDG-0002")); }

[Test] public void basket_should_map_to_catalog_basket() { "~/basket".ShouldMapTo<CatalogController>(x => x.Basket()); }

[Test] public void checkout_should_map_to_catalog_checkout() { "~/checkout".ShouldMapTo<CatalogController>(x => x.CheckOut()); } [Test] public void _404_should_map_to_error_notfound() { "~/404".ShouldMapTo<ErrorController>(x => x.NotFound()); } } }

Each of these simple test cases uses the NUnit B testing framework. They also use the ShouldMapTo<T> C extension method found in MvcContrib.TestHelper.