London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
Note: The functionality described in this article is not available in Commerce versions 11 and up.
Note: Episerver uses the Episerver asset system by default. If you want to enable the legacy asset management system, set the UseLegacyAssetSystem configuration setting to true in the web.config files of both the Commerce Manager and the front-end sites.
Episerver Commerce is configured to use the .xsd http handler by default. To display assets or make them downloadable, add an .xsd Application extension in Internet Information Services (IIS) and configure it the same way as the .axd Application extension.
Note: If the installation procedure for Episerver Commerce is properly executed, you can skip steps 7-9. If the handler settings does not appear as above, continue with steps 7-9.
To verify that the asset management is working, go to Assets in the Episerver Commerce administration interface, and select any file that you saved in the folders. You should be prompted for a location to the save the file, or a new window that displays the selected file.
Last updated: Oct 12, 2015