Son Do
Jul 20, 2015
visibility 4861
star star star star star
(0 votes)

Exporting media content using DataExporter

I want to export CMS media file and I found that using EPiServer.Enterprise.DataExporter make sense.

In project, create new page with code behind below:

public partial class ExportMedia : System.Web.UI.Page
    {
        private static Injected _tabDefinitionRepository;
        private static Injected _propertyDefinitionRepository;
        private static Injected _contentRepository ;
        private static Injected _categoryRepository;

        protected void Page_Load(object sender, EventArgs e)
        {
            DataExporter exporter = new DataExporter();

            //Get all page references and data
            List startPageReferenceList = new List();
            List startPageDataList = new List();
            ContentFolder rootFolder = _contentRepository.Service.GetChildren(EPiServer.Web.SiteDefinition.Current.GlobalAssetsRoot).FirstOrDefault() as ContentFolder;

            exporter.Frames.AddRange(Frame.List());
            exporter.TabDefinitions.AddRange(_tabDefinitionRepository.Service.List());
            foreach (var propertyDefinition in _propertyDefinitionRepository.Service.ListDynamic())
            {
                exporter.DynamicPropertyDefinitions.Add(propertyDefinition);
            }

            exporter.Categories.AddRange(_categoryRepository.Service.GetRoot().Categories);

            //Set rootFolder to exporter
            ExportSource sourceRoot = new ExportSource(rootFolder.ContentLink, EPiServer.Core.Transfer.ExportSource.RecursiveLevelInfinity);
            exporter.SourceRoots.Add(sourceRoot);

            //property settings
            exporter.ExportPropertySettings = true;
            exporter.IncludeImplicitContentDependencies = true;

            if (Request.QueryString["debug"] != null)
            {
                Response.Clear();
                exporter.Stream = new MemoryStream();
                exporter.Export();
                if (exporter.Log.Errors.Count > 0)
                {
                    foreach (string s in exporter.Log.Errors)
                    {
                        Response.Write(s + "; ");
                    }
                }
                else
                {
                    Response.Write("OK");
                }
            }
            else
            {
                Response.Clear();
                string file = Path.GetTempFileName();
                exporter.Stream = new FileStream(file, FileMode.OpenOrCreate, FileAccess.Write | FileAccess.Read, FileShare.Read);
                exporter.Export();
                exporter.Close();
                if (exporter.Log.Errors.Count > 0)
                {
                    throw new Exception("errors occured,try &debug=true");
                }
                Response.ContentType = "binary/octet-stream";
                Response.AddHeader("Content-disposition", "attachment; filename=MediaContent.episerverdata");
                exporter.Stream.Close();
                Response.WriteFile(file);
            }
            Response.End();
        }
    }

Navigate to this page in browser, we will get export file. And we can use this file to import media content.

Jul 20, 2015

Comments

May 15, 2017 05:10 PM

error Please login to comment.
Latest blogs
The Silent Success: When Your Optimizely SaaS CMS Config Push Succeeds with "0" Changes

  Picture this frustratingly common scenario in headless, code-first development with Optimizely SaaS CMS: You’ve defined a brilliant new element,...

Vipin Banka | Jul 13, 2026

Architecting an Enterprise-Grade Development Pipeline in Optimizely SaaS CMS

Most enterprise teams show up to Optimizely SaaS CMS with a clear roadmap for their release pipeline: DEV → QA → Stage → Prod. Four logical...

Vipin Banka | Jul 12, 2026

Bynder DAM Connector for Optimizely SaaS CMS: Improved Metadata Property Synchronization

While working with the Bynder DAM Connector for Optimizely SaaS CMS , one of the key areas I explored was how Bynder asset metadata is synchronized...

Vipin Banka | Jul 11, 2026

Optimizely DXP: Every Supported Culture, One Searchable Page

Quick one for anyone building multi-language sites on Optimizely DXP. I put together a reference tool listing all 806 supported cultures. More...

Adnan Zameer | Jul 10, 2026 |

A day in the life of an Optimizely OMVP: London Meetup 2026

On 2nd July 2026 the Optimizely London Developer Meetup returned to The Lightwell, and the running theme across the evening was less about individu...

Graham Carr | Jul 10, 2026

Optimizely’s Summer ’26 Roadmap: The CMS Is Starting to Look Less Like a Publishing Tool and More Like Marketing Infrastructure

Optimizely’s Summer ’26 Product Roadmap event was not just a list of product updates. At least, that is not the part I found most interesting. The...

Augusto Davalos | Jul 9, 2026