Deploy legacy asp classic websites

Hi,

I would like to bring an old thread on the table. (http://help.octopusdeploy.com/discussions/questions/5128-recommendations-for-handling-old-school-aspnet-websites)

Is there any news regarding to this in the latest version of Octopus?

Regards,
Ben

Hi Ben,

Thanks for reaching out! Things changed a bit since that post:

With the introduction of .NET core projects, we couldn’t rely on the csproj file with Octopack anymore, so we introduced a set of Pack and Push commands to our command line tool Octo.exe.

Pack - http://docs.octopusdeploy.com/display/OD/Using+Octo.exe
Push - http://docs.octopusdeploy.com/display/OD/Pushing+packages

It should be a fairly simple task to hook these 2 up in your build process so the Pack command targets the folder where you have your final website, and the Push command pushes the package to your repository.

Additionally, if you are using one of the below build servers, we added these 2 functionalities as new steps in the latest versions of the Octopus Plugins for them:

TeamCity - http://docs.octopusdeploy.com/display/OD/TeamCity#TeamCity-CreateAndPushPackageToOctopusCreatingandpushingpackagesfromTeamCitytoOctopus

TFS 2015 / Visual Studio Online - http://docs.octopusdeploy.com/pages/viewpage.action?pageId=5669025

Hope that helps,
Dalmiro