v4.4.1
Important Manual Update Recommended for DI Modules
If you installed v4.4.0 into a new project AND you installed one of the MvcSiteMapProvider.MVC[x].DI.[ContainerName] packages, you probably did not get the important update that it included. This release fixes the NuGet package logic, but unfortunately the damage has already been done on your project and some manual updating is required.
You can check whether you got the update by looking at the packages.config file in your project. It should include MvcSiteMapProvider.MVC[x].DI.[ContainerName].Modules that is the same version as MvcSiteMapProvider.MVC[x].DI.[ContainerName]. If you didn't get the update, the modules package will likely be 4.0.17, which was out of date at the time you installed MvcSiteMapProvider.
The safest way to fix this is to see the diff in commit 425c15cdfef7ee70b3226845daf2f91c8d3d7f12 and use it as a guide to manually update your DI module. You only need the one for the DI container you are using.
A more brute force way to apply the fix is to use the following package manager console command to update your modules package. This will overwrite any customizations you have done to the DI module or other startup code, so making a backup is highly recommended.
PM> Update-Package MvcSiteMapProvider.MVC[x].DI.[ContainerName].Modules -Version 4.4.1 -IgnoreDependencies -FileConflictAction Overwrite
Change Log
- Bug: Fix for #233, web.config format changes when installing.
- Bug: Fix for #234, upgrading updates Web.config package.
- Bug: Fix for #222, sitemaps index page links broken when hosted in sub-application.
- Bug: Fixes problem with new DI NuGet package installation not installing the most recent version of modules.