ASP.NET 5 (vNext) Deployment through TFS 2015

We are trying to work through a new chain of tools to create and deploy a CoreCLR ASP.NET 5 (vNext) website in a server cluster. Between changes to the new compilation and changes to TFS, I'm not sure how everything is now created and deployed. The scenario is as follows:

  • Built-in TFS for version control and build agent
  • Orientation of ASP.NET 5 in CoreCLR hosted through IIS

Questions:

Using TFS for continuous integration builds (and hopefully deploying to a local IIS server), how to create and deploy this new type of application?

It seems that MSBuild can still be used to specify the .sln file to indirectly call dnu.exe, is this correct? Is this a good way to do it now?

Should we run the build script task instead of running dnu.exe?

How are these new CoreCLR builds deployed? Just a direct copy to a directory on a remote machine?

This is a new application, and we use a multi-tier application architecture where DAL and business logic are in CoreCLR's own projects, if that matters.

Thank you in advance for clarifying the situation.

+6
source share
2 answers

Here's what we ended up with:

+6
source

To create and deploy ASP.NET 5 through the vNext TFS2015 build system, you need to:

1). Create a PowerShell script (e.g. Prebuild.ps1) to install DNX. Details of the PowerShell script can be found: https://msdn.microsoft.com/en-us/Library/vs/alm/Build/azure/deploy-aspnet5 . Add the script file to the TFS version control.

2). Add the PowerShell script build step to the build definition. Run the Prebuild.ps1 script in this step:

enter image description here

3). In the MSBuild step, specify the project that you want to create, and add the following / p: DeployOnBuild = True / p: DeployTarget = MSDeployPublish / p: CreatePackageOnPublish = True / p: MSDeployPublishMethod = InProc / p: MsDeployServiceUrl = localhostAppPpp Dep default website / TFSTest 1 "/ p: VisualStudioVersion = 14.0 for publishing the project to IIS.

+1
source

All Articles