Tags: Episerver Find

Episerver Find finally renamed to Episerver Search & Navigation!

With Update 346 released today, the product name has finally been changed from «Episerver Find» to «Episerver Search & Navigation» in the user interface.

The dependencies for the Episerver.Find.CMS nuget package has been updated to this:
Dependency: Microsoft.AspNet.WebApi.WebHost >= 5.2.3 && < 6.0.0

But internally they are referncing a newer version:
Screenshot from DotPeek showing version 5.2.7 of System.Web.Http, System.Web.Http.WebHost and System.Web.Mvc

So, if you are using Microsoft.AspNet.WebApi.WebHost 5.2.3 you will get a runtime error!

Server Error in ‘/’ Application.


Could not load file or assembly 'System.Web.Http.WebHost, Version=5.2.7.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)r

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'System.Web.Http.WebHost, Version=5.2.7.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4250.0

Upgrade the NuGet package Microsoft.AspNet.WebApi.WebHost to version 5.2.7 and Microsoft.AspNet.Mvc also to version 5.2.7 and you are all good!

Alternative solution: If you do not want to update those packages, an assemby redirect should also do the trick. Example:

<dependentAssembly>
   <assemblyIdentity name="System.Web.Http.WebHost" publicKeyToken="31bf3856ad364e35" culture="neutral" />
   <bindingRedirect oldVersion="0.0.0.0-5.2.7.0" newVersion="5.2.3.0" />
</dependentAssembly>

The issue is supposedly fixed in EPiServer.Find 13.4.0.