Hi,

Thanks for the help, but unfortunately I can't use the \App_Code folder for my site custom files. For example one of the files is a javascript file, and placing it in the \App_Code folder causes an application error due to language incompatibility.

I tried putting all the files in an \App_Data\<site code name> folder which worked great in the export but for some reason made some of the files, like the javascript file, unusable within the site itself. (i.e. simply viewing the .js file returned blank code)

My main aim is to try and keep the <web project> folder tidy by not having lots of idividual <web project>\<site code name> folders for all my custom files for each site. When you have for example 10-20 sites all with custom folders, the <web project> folder gets quite messy with all the CMS folders mixed with <site code name> folders.

It would be nice to have one sub-<web project> folder I can place all my individual <site code name> folders, where they would also be recognised by the CMS to be included in the export process, and also allow me to include any file types I wish.

One work-around I found is to add the custom files to a site Media Library, and import the file links to the CMS database. That way they are included in the export package, but only if I check the "Export physical files" under the Media Library section in Step 2 of the export. Which isn't really ideal, but works.

A better option i've found is to split the file types and include all my custom images and javascript files in an \App_Themes\<site code name> folder, and all my custom c# files in an \App_Data\<site code name>. This seams to work best in accessing the files and also including them in the Export package without having to select extra options.

Thanks,
Tim