ImageResizer can be installed side-by-side with the following content management systems - no additional steps are required.
- DotNetNuke
- EPiServer
- Umbraco 4, 5, 6
Additional information for certain CMSes
Articles on using ImageResizer with Umbraco
- heltBlank: Umbraco and ImageResizer
- uBootstrap for Umbraco now includes ImageResizer to handle responsive imaging needs
Walkthroughs on using ImageResizer with EPiServer
- Frederik Vig: Add powerful image resizing, cropping and manipulation support to your EPiServer website
- Anders Hattestad: Automatically change images in a responsive design to scale (EPiServer)
Ektron includes ImageResizer
Ektron 8.6 and higher include ImageResizer Essential Edition, but do not register the HttpHandler properly. This means ImageResizer.dll may already be installed in /bin, but you will still have to modify Web.config.
Follow standard installation instructions. If you get an assembly binding error, you may need to upgrade to a newer release of Ektron (Ektron 8.6 uses a version-specific assembly reference to ImageResizer; this should be fixed in later releases).
Sitecore and ImageResizer
Standard installation steps work with SiteCore, but you cannot use the jpg.ashx syntax - so ensure you're using IIS integrated mode. All functionality should be accessible with the normal, non-suffixed syntax (/resizer.debug, /image.jpg?width=100).
Sitefinity and ImageResizer
Sitefinity 3.X and earlier versions require no additional steps.
Sitefinity 4.X and later versions prevent external libraries and code from accessing uploaded files in a standardized manner (They no longer support ASP.NET's VirtualPathProvider system, nor do they provide an equivalent).
URIs are a good way to identify files, and we are disappointed that Sitefinity 4.X+ does not provide an API which accepts a virtual path.
While we are looking for a solution that supports all Sitefinity 'Providers' and 'Libraries' in an integrated way, you can use our existing plugins to access the data-stores behind the providers directly. SqlReader can be used if you're uploading files to SQL, and S3Reader, AzureReader, or RemoteReader if you're uploading to blob storage. If you're uploading to the local filesystem, you can use the VirtualFolder plugin to modify the path.
Orchard and ImageResizer
Standard installation steps are sufficient for the Essential Edition, but an additional Web.config file must be changed for DiskCache to work properly.
Older versions of Orchard Contrib.Cache duplicate content once for each handler for the HttpApplication.PreSendRequestHeaders event See bug report on CodePlex
While the ImageResizer architecture is designed to make multi-tenanting support easy to implement, no Orchard guru has yet stepped forward to implement the glue. Thus, there is not a good multi-tenanting story for ImageResizer and Orchard yet.
Articles on Orchard and ImageResizer
Dave Gardner wrote a fantastic 7-part article on how to make a gallery module for Orchard using the ImageResizer.
Bertrand Le Roy (Orchard author): State of .NET Image Resizing: how does imageresizer do? * Note the performance chart is bogus due to a mistake in the Bertrand's benchmark code. The corrected chart displays actual apples-to-apples data, instead of comparing low-quality and high-quality image resizing as the original benchmark does.
Orchard + ImageResizer Disk Cache
Strangely, Orchard disables the serving of static files at the site root level by removing all httpHandlers. For Disk Caching to work, you will need to customize the imagecache/Web.config file.
Restoring the StaticFileHandler mappings should re-enable efficient disk caching.
<?xml version="1.0"?>
