Running ImageVault 3 & 4 on the same site
Configure Episerver CMS6 R2 for ASP.NET v4
If you use Episerver CMS6 R2 you need to configure it to run under ASP.NET 4. See: http://world.episerver.com/Articles/Items/EPiServer-CMS-60-now-supporting-ASPNET-40/
NB! If the following element structure exists in your web.config, please make sure to change the providerOption, CompilerVersion to "v4.0", like below:
<system.codedom>
<compilers>
<compiler ...="" >
<providerOption name="CompilerVersion" value="v4.0" />
</compiler>
</compilers>
</system.codedom>
Installing ImageVault 3.5.10
ImageVault 3.5.10 can be fetched through the ImageVault NuGet feed, http://nuget.imagevault.se/nuget. Package name is ImageVault3.EPiServer6.
The package contains three DLL:s (in lib/4.0) that should be added/replaced in the Epi site's bin folder:
- Add ImageVault3.EPiServer6.dll
- Replace ImageStoreNET.dll
- Replace ImageVault.dll
- Remove the file ImageVault.EPiServer6.dll (ImageVault3.EPiServer6.dll is now used instead)
Run SQL script
Apply the SQL script included in the NuGet package (in the content folder) on the Epi database.
Modify web.config
All references to ImageVault.EPiServer6 should be replaced with ImageVault3.EPiServer6. Change AssemblyBindings for ImageStoreNET and ImageVault3.EPiServer6 to the latest version 3.5.10.x.
ImageVault 4 web.config changes
If both versions run on the same site some changes need to be done in the web.config for ImageVault 4 UI.
The ImageVault 4 UI configuration file can be found at C:\ImageVault\Ui\<yourSiteName>\web.config
Add the following to the system.webServer/modules section, if not already existing:
<system.webServer>
<modules>
<remove name="ImageVault" />
<remove name="IIS5XWildCardExtensionFix" />
This will make sure the modules used by ImageVault 3 does not conflict with the ImageVault 4 UI.