Upgrading
Assembly and license upgrade
To upgrade the assembly and license, follow these steps
-
Install the v5 dll – Get the SlickUpload 5 package, and replace the old version dll in your project with the version 5 dll.
-
Install the v5 license – Remove the current Krystalware.SlickUpload.xml.lic or AssistedSolutions.SlickUpload.xml.lic file and replace it with the new v5 Krystalware.SlickUpload.xml.lic file you
received. See the installing the SlickUpload license topic for more information.
SlickUpload 4 to SlickUpload 5
Upgrading from SlickUpload 4 to SlickUpload 5 is straightforward. Some of the control names have
changed, but the behavior is substantially the same.
Upgrading the UploadManager control
The SlickUpload 4 UploadManager control has been replaced by the SlickUpload control in SlickUpload 5. To convert an UploadManager control to
a SlickUpload control:
- Change the control type from
<kw:UploadManager to <kw:SlickUpload.
- Change the progress template name from
<ProgressAreaTemplate> to <ProgressTemplate>.
- Change the progress element control types from
<kw:ProgressElement to <kw:UploadProgressElement and from <kw:ProgressBarElement to <kw:UploadProgressBarElement. This can be done in one step by doing a search and replace from "kw:Progress" to "kw:UploadProgress".
- Remove the UploadAreaStylesheet template if it exists and move any styles to the page that contains the SlickUpload control.
- To add a file list template, copy in the following default template inside the
<kw:SlickUpload control:
<FileTemplate>
<kw:FileListRemoveLink ID="FileListRemoveLink1" runat="server" Title="Remove">
[x]
</kw:FileListRemoveLink>
<kw:FileListFileName ID="FileListFileName1" runat="server" />
<kw:FileListValidationMessage ID="FileListValidationMessage1" runat="server" ForeColor="Red" />
</FileTemplate>
- To add an uplevel file selector button template, copy in the following default template inside the
<kw:SlickUpload control:
<UplevelSelectorTemplate>
<input type="button" value="Add Files" />
</UplevelSelectorTemplate>
Upgrading custom location based configuration
If you have any custom configurations based on an UploadHandlerLocation, such as UploadHandlerLocation="UploadHandler.aspx":
- Add a new SlickUpload HttpHandler to bind the location configuration to. For example:
<add path="SlickUploadCustom.axd" verb="GET,HEAD,POST,DEBUG" type="Krystalware.SlickUpload.SlickUploadHandler, Krystalware.SlickUpload" />
- Change the path attribute of the location key to point to the new handler.
- Remove the UploadHandlerLocation attribute and add an UploadUrl attribute that points to the new handler. For example:
UploadUrl="~/SlickUploadCustom.axd".
SlickUpload 3 to SlickUpload 5
Perform the following steps in addition to the SlickUpload 4 to SlickUpload 5 upgrade steps outlined above.
-
Remove SlickUpload.ashx – The SlickUpload.ashx file is no longer used by SlickUpload 5, so you can delete it.
-
Add the SlickUpload.axd handler – Add the following section to your web.config:
<httpHandlers>
<add path="SlickUpload.axd" verb="GET,HEAD,POST,DEBUG" type="Krystalware.SlickUpload.SlickUploadHandler, Krystalware.SlickUpload" />
</httpHandlers>
-
Configure custom upload handlers – If you have customized the upload selection page (e.g. UploadHandler.aspx), you'll need to set the
UploadHandlerLocation property on the UploadManager control to point to it. SlickUpload 3 used UploadHandler.aspx by default, but SlickUpload 5
points at a default autogenerated handler so you must specify the custom handler manually.
If you have any questions or need assistance upgrading, contact support.
Related topics:
|