The following is required for Xile to function properly:
Although you can set the maximum file size allowed per instance of Xile, both DNN, IIS and ImageResizer have limitations as well. If you receive a file not found error or a broken image this is most likely the culprit.
Within your website's web.config you must increase the value of maxrequestlength.
<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" requestLengthDiskThreshold="8192" requestValidationMode="2.0"/>
Xile uses an internal key for encryption, but it's important to set your own. You can do this by adding a custom key in your web.config's appSettings:
Within your website's web.config add the following line (But change the value to something similar, but cryptic and meaningless).
<add key="XileEncryptionKey" value="FEIEFSKJFAHSHSDFIE32FSKJS998FJ" />
ImageResizer comes with a SizeLimiting Plugin to preventing abuse and limiting photo resolution. By default the plugin prevents requests that would result in an image over 3200x3200. You can increase or decrease this limit, or remove the SizeLimiting Plugin completely.
Within your website's web.config add the following code:
<?xml version="1.0" encoding="utf-8" ?>
<section name="resizer" type="ImageResizer.ResizerSection,ImageResizer" requirePermission="false" />
<remove name="SizeLimiting" />
IIS7+ has a default maxRequestLength of 30MB by default, so we have to make one more adjustment. Place the following code within the system.webServer section of your web.config. Set this to what you want. The below example is 50MB.
<requestLimits maxAllowedContentLength="50000" />