Windows publishing profile

As explained in Building Web APIs with ASP.NET Core

A deployment configuration that stores the settings and options used to publish an application to a target environment.

A Windows publishing profile is a reusable deployment configuration for building an application and sending it to a Windows-hosted target. Visual Studio saves the settings in a .pubxml file under /Properties/PublishProfiles/, allowing multiple targets or deployment configurations for the same project. section 12.4 section 12.4.1

Create and configure a profile for the MyBGList web API:

• Install Web Deploy when using Visual Studio to deploy directly to IIS; open TCP port 8172 for inbound IIS management and Web Deploy traffic. section 12.3.3
• Right-click the project in Solution Explorer, choose Publish, select Azure, choose Azure Virtual Machine, connect an Azure account and subscription, select the Windows VM, and click Finish. section 12.4.2
• Open the profile’s full settings and configure the IIS site name, VM administrator credentials, destination URL, build configuration, framework, deployment mode, and runtime. section 12.4.3
• Validate the connection, save the profile, publish the application, and use the resulting post-deployment testing tasks to verify the release. section 12.4.3

MyBGList Azure VM profile

Configure Site name as MyBGList, enter the VM Administrator credentials, set Destination URL to https://win-01.mybglist.com, choose Release, net6.0, Framework-dependent, and win-x64, then validate and publish. section 12.4.3

Figure 12.22 Visual Studio’s Publish Profile configuration settings

Use the settings view to inspect and edit the profile’s connection and deployment values before publishing. section 12.4.3

How Building Web APIs with ASP.NET Core covers it

How deep it goes

Defines profile storage, target selection, connection fields, build settings, validation, and publishing, without detailing deployment internals.

Examples

Uses the MyBGList API, an Azure Windows VM, IIS site name MyBGList, and a win-x64 framework-dependent Release configuration.

What it assumes

Assumes a Visual Studio project, an Azure subscription and Windows VM, IIS site, administrator credentials, and Web Deploy availability.

What you can do after

Operate/configure Visual Studio publishing to validate a Windows target and deploy a .NET web API.

How it connects

Connects Visual Studio publishing with Web Deploy, IIS, Azure Virtual Machines, .NET publishing modes, and deployment artifacts.

liveBookmanning.com

Read Building Web APIs with ASP.NET Core on liveBook Get the book at manning.com

Related concepts

• Visual Studioconfigured by · Visual Studio is Microsoft's integrated development environment for creating, building, debugging, and testing software across programming languages and platforms.
• Web Deployproduced by · Web Deploy is a Microsoft deployment tool for synchronizing and publishing web applications and their related content to web servers.
• framework-dependent deploymenthas part · A framework-dependent deployment publishes an application without bundling its runtime, which must be installed compatibly on the target system.

This explainer was generated by Manning's knowledge graph from the text of Building Web APIs with ASP.NET Core. The section links point to the parts of the book it draws on.