Due to the differences between website and web application projects, the system cannot import from one to another automatically.
For packages that contain physical files, you need to complete the standard import procedure, and then manually perform the following steps to ensure that your web application runs correctly:
The import places all physical files from the imported package into the ~/App_Data/CMSTemp/ImportExport/Files folder (or a different folder if your application has the CMSTemporaryFilesFolderPath web.config key set to a custom folder). Copy the content of the folder into the CMS folder of your web application project.
We strongly recommend creating a backup of your project before you overwrite any files.
Open the solution file (WebApp.sln) in Visual Studio from the web project directory.
- Include the files that did not exist in the project before the import:
- Click Show all files at the top of the Solution Explorer.
- Locate the newly added files.
- Select the files you wish to include one-by-one while holding the Ctrl key.
- Right-click one of the files and select Include in Project.
- Convert the project to the web application format:
- Visual Studio 2012: Right-click the project node (CMSApp) in the Solution Explorer and select Convert To Web Application.
- Visual Studio 2013: Select the project node (CMSApp) in the Solution Explorer, open the PROJECT menu on the main toolbar and select Convert To Web Application.
- Rebuild the solution.
If you are importing a package from another web application project, you do not need to convert the files (step 4), but it is still necessary to include the imported files in the project.
Importing into precompiled projects
If you are running a precompiled website, you cannot import:
- Physical files that require compilation (such as cs, vb, aspx, ascx)
- The App_Code folder
- Virtual objects that contain ASP.NET markup:
To add files or objects that require compilation, you need to perform the import on the original project and run the precompilation again.