In most organizations, application developers deploy to a local test environment before deploying to a production environment.  This allows you to thoroughly test in a safe environment before moving the application into production.

Iron Speed Designer normally runs your application on the local machine running Iron Speed Designer iteself.  This is almost always a development or test environment.  When you are ready to deploy the tested application into a production environment, several additional steps are required, depending on the type of application being deployed and how you want to configure it.

Iron Speed Designer’s Deployment Wizard offers these deployment methods:

• MSI Installer.  This is by far the easiest and best way to deploy your application. This option also creates a deployment folder as specified in the next option. We highly recommend it!  See Deploying Applications with the Deployment Wizard for details.  Starting with .NET Framework 4.5, Microsoft has changed the deployment methods and eliminated the MSI installer in favor of the Deployment folder.

• Deployment folder.  Creates a deployment project folder for your application.  A single application DLL will be created and only the necessary .aspx, .ascx, binary, image, and other content files will be included.  Prior to the .NET Framework 4.5, the deployment project folder contains the folder, "deploy\Release",  can be copied to your production server for deployment.  Starting with the .NET Framework 4.5, deployment is handled by Publishing A Deployment Package, which contains the deployment folder.

• SharePoint Solution Package (WSP).  Creates a deployment project folder for your application.  A single application WSP is created which can be deployed to your SharePoint server.

• Publish to network server.  Creates a deployment project folder for your application.  Your application is then copied to a specified location on your network.

• Publish to cloud.  Creates a deployment project folder for your application.  Your application is then copied via FTP (file transfer protocol) to a specified server location.

• Manual deployment.  See Manually Deploying an Application to a Production Server for details.

• Application hosting provider.  See Deploying to Application Hosting Service Providers for details.

See Also

Step 1: Select the Deployment Type

Step 2: Select the Deployment Project Folder

Step 3: Select the Server Path (Network Deployment)

Step 3: Select the Server Path (Cloud Deployment)

Step 4: Enter Application Assembly Information

Step 5: Publish Your Application

Publishing A Deployment Package

MSI Installer Deployment

SharePoint Solution Package (WSP) Deployment