Remote Publish ASP.NET 5 in IIS

Question

I have an ASP.NET 5 project that I would like to deploy to a remote server. I do not have access to the remote desktop on this computer, otherwise I could follow the same method that most people use when deploying to IIS.

I can install on my IIS 8.5 just fine on the same machine as my development. First, I pack my project to get reference materials and wwwroot directories. Then I point IIS to my wwwroot and everything works fine.

The problem is trying to deploy remotely. Normally I would zip up my MVC 5 project and use IIS leagues to “import” the application.

This does not work for my MVC 6 project. Either I don't loop properly, or MVC 6 projects cannot be deployed this way.

How do you publish a vNext application on a remote IIS server?

Edit:

Just FYI, I use the Microsoft Web Deploy Remote Agent to deploy this to the server. http://www.asp.net/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-(remote-agent )

It works great for MVC 5 applications because developers can easily deploy web applications and IT resources can restrict access to machines, but the problem is trying to deploy MVC 6 applications using this agent.

I will not doubt how to deploy MVC 6 projects in IIS, because I already answered here , this applies to remote deployment for IIS.

Answer 1

I solved this by updating Web Deploy 3.6 . The latest version includes a specialized provider for deploying ASP.NET 5 applications.

Details on how to use it can be found on this blog: http://azure.microsoft.com/blog/2014/08/11/web-deploy-3-6-beta-released/

The download link is as follows: http://www.microsoft.com/en-us/download/details.aspx?id=43717

Use the contentPathLib provider or enable contentlibextension .

Usage example:

C: \ Program Files (x86) \ IIS \ Microsoft Web Deploy V3> msdeploy -verb: sync -source: iisapp = C: \ release \ Publish \ wwwroot -dest: iisapp = "Default website / ExampleApp", computerName = machine name -enablelink: contentlibextension

To my knowledge, there is not yet a GUI that supports these deployment methods. I assume this is due to the fact that vNext is in beta and is expected to have changes.