Updated NuGet version

Updated NuGet version
And there's a fresh build!

And there's a fresh build!
Even fresher

Even fresher
Merge pull request #74 from MaxKot/master

 Fix for issue #14 (Use GET to determine node accessibility).
Update src/MvcSiteMapProvider/MvcSiteMapProvider/DefaultSiteMapProvider.cs

Moved the BuildSiteMap caching into the finally block. This allows exceptions to be caught and, if required by the application, for the sitemap to be refreshed.

Currently an exception thrown while building (eg in a dynamicnodeprovider) will result in a sitemap being partially built without the cachekey being added, meaning that the refresh method won't work.
Merge pull request #77 from chaoaretasty/master

DefaultSiteMapProvider can't be refreshed if an exception was thrown
Fix for Issue #78, #67

The previous fix for #67 hid rather than fixed the problem and caused new issues for non-area controllers.

This fix reverts the previous edit and amends ResolveControllerType instead.

This should now allow type resolving properly in the following cases
*A non-area route provides non-default namespaces
*Non-unique controller names appear inside and outside of an area

Problems will be caused in the following case:
*When non-area routes are to check only within a given namespace and not the defaultnamespaces

This is a much less common edgecase than either above case, it is bucking the "convention over configuration" view of MVC so comes with an expectation of more potential issues.
Merge pull request #88 from chaoaretasty/patch-1

Fix for Issue #78, #67
Support controllers that are open generic types
Merge pull request #92 from pmarflee/master

Support controllers that are open generic types
AuthorizeAttributeAclModule null reference exception fix.
Multiple sitemap providers sharing cache keys bug.
Merge pull request #111 from waynebrantley/master

Two bugs I found...
Fresh build created

Fresh build created
Update Build.bat

No more pause at the end!
IAclModule had a dependency on DefaultSiteMapProvider class instead of the base.  This made it impossible to replace DefaultSiteMapProvider with a class of your own.
SiteMapNode did not handle multiple sitemaps defined in the web.config.  If you defined the sitemap in code via attributes, there was no way to specify which sitemap the node belonged to.  Added this functionality.  By default if you only have one sitemap, everything works as it did, otherwise there is a new 'SiteMapProviderName' property of a MvcSiteMapNode.

The logic used to determine the area using the namespace was returning areas when it should not have. A namespace of Company.Webs.MainSite.Controllers would return 'Webs' as the area.  According to the default conventions, there is no area here.  The default convention looks like Company.Webs.MainSite.Areas.MyAccount.Controllers where MyAccount is the area.  Adjusted logic to properly parse the area out of namespaces.
Merge pull request #117 from waynebrantley/master

Fix for defining multiple sitemaps using MvcSiteMapNode.
Remove route attribute from RouteValueDictionary

When mvcSiteMapNode is populated with 'route' attribute, it selects the
correct route but adds it as a query param as well, e.g. '?route=bfs'.
This commit ensures route query param is removed only if route is
present.
Merge pull request #122 from beresovskiy/master

Remove 'route' param from query string when routeName is supplied
Modified the SiteMapTitleAttribute to allow multiple instances of the attribute per action. There are no checks on whether or not multiple instances are applied at the current or parent nodes.