-->

By deploying an application, service, or component, you distribute it for installation on other computers, devices, or servers, or in the cloud. You choose the appropriate method in Visual Studio for the type of deployment that you need. (Many app types support other deployment tools, such as command-line deployment or NuGet, that aren't described here.)

See the quickstarts and tutorials for step-by-step deployment instructions. For an overview of deployment options, see What publishing options are right for me?.

In Visual Studio 2012, Microsoft removed the ability to make quick installers for your application. Now they recommend using a third party like Wix or InstallShield. This tutorial will go over using InstallSheild’s free light version to make an installer for your application. Aug 15, 2013 In Visual Studio 2010 we partnered with Flexera Software to included InstallShield Limited Edition, a free version of Flexera’s installation development solution, with Visual Studio. InstallShield Limited Edition added capabilities not found in Visual Studio Setup Projects, such as TFS and MSBuild integration, support for creating new web. Yup, Visual Studio menyediakan Setup and Deployment untuk anda yang ingin men-package software anda untuk didistribusikan. Bila anda menggunakan Visual Studio 2010/2012, maka terdapat Setup and Deployment yang berisikan “default” dan “Install Shield”. Choose the Language packs tab in the Visual Studio Installer. Select the language you prefer. Follow the prompts. Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance. Bila anda menggunakan Visual Studio 2010/2012, maka terdapat Setup and Deployment yang berisikan “default” dan “Install Shield”. Nah, pada tutorial ini kita akan membahas tentang deployment dengan menggunakan Install Shield tetapi kita akan mencoba fungsi fungsi dasar terlebih dahulu.

Deploy to a local folder

Deployment to a local folder is typically used for testing or to begin a staged deployment in which another tool is used for final deployment.

• ASP.NET, ASP.NET Core, Node.js, Python, and .NET Core: Use the Publish tool to deploy to a local folder. The exact options available depend on your app type. In Solution Explorer, right-click your project and select Publish. (If you haven't previously configured any publishing profiles, you must then select Create new profile.) Next, select Folder. For more information, see Deploy to a local folder.

• Windows desktop: You can publish a Windows desktop application to a folder by using ClickOnce deployment. Users can then install the application with a single click. For more information, see the following articles:

  • Deploy a .NET Framework Windows desktop app using ClickOnce.
  • Deploy a .NET Windows desktop app using ClickOnce.
  • Deploy a C++/CLR app using ClickOnce or, for C/C++, see Deploy a native app using a Setup project.

Publish to Azure

• ASP.NET, ASP.NET Core, Python, and Node.js: Publish to Azure App Service or Azure App Service on Linux (using containers) by using one of the following methods:

  • For continuous (or automated) deployment of apps, use Azure DevOps with Azure Pipelines.
  • For one-time (or manual) deployment of apps, use the Publish tool in Visual Studio.

  For deployment that provides more customized configuration of the server, you can also use the Publish tool to deploy apps to an Azure virtual machine.

  To use the Publish tool, right-click the project in Solution Explorer and select Publish. (If you've previously configured any publishing profiles, you must then select Create new profile.) In the Publish dialog box, select either App Service or Azure Virtual Machines, and then follow the configuration steps.

  Starting in Visual Studio 2017 version 15.7, you can deploy ASP.NET Core apps to App Service on Linux.

  For Python apps, also see Python - Publishing to Azure App Service.

  For a quick introduction, see Publish to Azure and Publish to Linux. Also, see Publish an ASP.NET Core app to Azure. For deployment using Git, see Continuous deployment of ASP.NET Core to Azure with Git.

  Note

  If you don't already have an Azure account, you can sign up here.

Publish to the web or deploy to a network share

• ASP.NET, ASP.NET Core, Node.js, and Python: You can use the Publish tool to deploy to a website by using FTP or Web Deploy. For more information, see Deploy to a website.

  In Solution Explorer, right-click the project and select Publish. (If you've previously configured any publishing profiles, you must then select Create new profile.) In the Publish tool, select the option you want and follow the configuration steps.

  For information on importing a publish profile in Visual Studio, see Import publish settings and deploy to IIS.

  You can also deploy ASP.NET applications and services in a number of other ways. For more information, see Deploying ASP.NET web applications and services.

• Windows desktop: You can publish a Windows desktop application to a web server or a network file share by using ClickOnce deployment. Users can then install the application with a single click. For more information, see the following articles:

Installshield Limited Edition For Visual Studio Tutorial Youtube

Publish to Microsoft Store

Installshield Limited Edition For Visual Studio 2017

From Visual Studio, you can create app packages for deployment to Microsoft Store.

• UWP: You can package your app and deploy it by using menu items. For more information, see Package a UWP app by using Visual Studio.

• Windows desktop: You can deploy to Microsoft Store by using the Desktop Bridge starting in Visual Studio 2017 version 15.4. To do this, start by creating a Windows Application Packaging Project. For more information, see Package a desktop app for Microsoft Store (Desktop Bridge).

Deploy to a device (UWP)

If you're deploying a UWP app for testing on a device, see Run UWP apps on a remote machine in Visual Studio.

Create an installer package (Windows desktop)

If you require a more complex installation of a desktop application than ClickOnce can provide, you can create a Windows Installer package (MSI or EXE installation file) or a custom bootstrapper.

• An MSI-based installer package can be created by using the WiX Toolset Visual Studio 2017 Extension. This is a command-line toolset.

• An MSI or EXE installer package can be created by using InstallShield from Flexera Software. InstallShield may be used with Visual Studio 2017 and later versions. Community Edition isn't supported.

  Note

  InstallShield Limited Edition is no longer included with Visual Studio and isn't supported in Visual Studio 2017 and later versions. Check with Flexera Software about future availability.

• An MSI or EXE installer package can be created by using a Setup project (vdproj). To use this option, install the Visual Studio Installer Projects extension.

• You can also install prerequisite components for desktop applications by configuring a generic installer, which is known as a bootstrapper. For more information, see Application deployment prerequisites.

Deploy to a test lab

You can enable more sophisticated development and testing by deploying your applications into virtual environments. For more information, see Test on a lab environment.

Continuous deployment

You can use Azure Pipelines to enable continuous deployment of your app. For more information, see Azure Pipelines and Deploy to Azure.

Deploy a SQL database

Deployment for other app types

Next steps

In this tutorial, you took a quick look at deployment options for different applications.