wavefullpac

1. Download Visual Studio

December 14th, 2009Developing and refining your code is an important part of building your application. Once it’s built, you need to deploy that before your customers can start seeing the benefits of using the application. For many applications, the most reliable way to deploy is to build a setup project that packages your application’s components into an easily installable package with a familiar interface for your customers.Today you can use the Visual Studio Installer project template to create a setup project; however, we have heard from our customers that they need more. They need capabilities such as the ability to build using Team Foundation Server, a simpler, more modern developer experience and most importantly a runway to advanced deployment capabilities that scale along with their applications.To address this feedback, we have partnered with Flexera, makers of InstallShield to create, just for Visual Studio 2010 customers, InstallShield Limited Edition 2010. This is a Visual Studio extension you can download and use today to build Windows installer-based deployment packages for your application that can be deployed on the Windows platform. It provides comparable functionality to the Visual Studio Installer project but in addition, you get the easy to use, modern, graphical development environment of InstallShield, as well as the ability to build your deployment projects using Team Foundation Server.

First look at deployment in Visual Studio. 5 minutes to read.In this articleBy 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 that are not described here.)See the Quickstarts and Tutorials for step-by-step deployment instructions.

For an overview of deployment options, see. Deploy to local folderDeployment 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,. 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 choose Publish. (If you have not previously configured any publishing profiles, you must then click Create new profile.) Next, choose Folder. For more information, see.Windows desktop You can publish a Windows desktop application to a folder using ClickOnce deployment. Users can then install the application with a single click. For more information, see (C# and Visual Basic). NoteIf you do not already have an Azure account, you can.Publish to Web or deploy to network share.ASP.NET, ASP.NET Core, Node.js, and Python: You can use the Publish tool to deploy to a website using FTP or Web Deploy.

For more information, see.In Solution Explorer, right-click the project and choose Publish. (If you have previously configured any publishing profiles, you must then click Create new profile.) In the Publish tool, choose the option you want and follow the configuration steps.For information on importing a publish profile in Visual Studio, see.You can also deploy ASP.NET applications and services in a number of other ways. For more information, see.Windows desktop You can publish a Windows desktop application to a web server or a network file share using ClickOnce deployment. Users can then install the application with a single click.

For more information, see (C# and Visual Basic). For C/CLI, see or, for C/C, see.Publish to Microsoft StoreFrom Visual Studio, you can create app packages for deployment to Microsoft Store.UWP: You can package your app and deploy it using menu items. For more information, see.Windows desktop: You can deploy to the Microsoft Store starting in Visual Studio 2017 version 15.4.

To do this, start by creating a Windows Application Packaging Project. For more information, see.Deploy.NET packages to NuGet.orgTo deploy bundled code into 'packages' that contain compiled code (as DLLs) along with other content needed in the projects that consume these packages, you can use Visual Studio to create the NuGet package and a CLI tool to issue the final deployment command.Deploy to a device (UWP)If you are deploying a UWP app for testing on a device, see. Create an installer package (Windows desktop)If you require more a complex installation of a desktop application than 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 using the. This is a command-line toolset.

For Visual Studio 2019, get the.An MSI or EXE installer package can be created using from Flexera Software. InstallShield may be used with Visual Studio 2017 and later versions (Community Edition not supported). Note that InstallShield Limited Edition is no longer included with Visual Studio and is not supported in Visual Studio 2017 and later versions; check with about future availability.An MSI or EXE installer package can be created using a Setup project (vdproj). To use this option, install the.You can also install prerequisite components for desktop applications by configuring a generic installer, which is known as a bootstrapper. For more information, see.Deploy to test labYou can enable more sophisticated development and testing by deploying your applications into virtual environments. For more information, see.

Download Visual Studio

Continuous deploymentYou can use Azure Pipelines to enable continuous deployment of your app. For more information, see. Deploy a SQL database.Deployment for other app types App typeDeployment ScenarioLinkOffice appYou can publish an add-in for Office from Visual Studio.WCF or OData serviceOther applications can use WCF RIA services that you deploy to a web server.LightSwitchLightSwitch is no longer supported starting in Visual Studio 2017, but can still be deployed from Visual Studio 2015 and earlier.Next stepsIn this tutorial, you took a quick look at deployment options for different applications.