Answered by:
where is a build/solution deployed in Azure Web/Worker Role.

Question
-
We deploy our Visual Studio Solution (asp.net web solution, deployed on web role) either using directly Visual Studio or using Powershell. The solution is deployed somewhere on Azure Cloud. Azure Cloud Automation creates a web role instance and installs the solution on it, as per my understanding.
I am wondering where is the solution/build deployed after we deploy it in Azure? Can any please tell me the complete flow.
Regards Restless Spirit
Answers
-
Yes you are right, when you do the deployment to Azure cloud services from VS wizard then it uploads the cspkg and csdef files 'somewhere' in the storage account you mentioned and then deploys to your cloud service by referring to that location. Now this location is willingly kept hidden from end users as you wont want to access it directly, would you?
If you wish to do the deployment by keeping cspkg and csdef files in your control then the best option is - upload those to your own storage account inside some container like 'manual deployments' and then deploy it from there.
- Marked as answer by Restless Spirit Wednesday, August 3, 2016 8:13 AM
All replies
-
Hello,
Greetings from Microsoft Azure!
You can configure your Visual Studio Team Services team projects to automatically build and deploy to Azure web apps or cloud services.
For more information, kindly refer “Continuous delivery to Azure using VSTS”.
And also, check “How to deploy only worker/web role in Azure”.
Hope this helps.
Regards,
Pradeep
Kindly click "Mark as Answer" on the post that helps you, this can be beneficial to other community members reading the thread and also “Vote as Helpful”.
- Proposed as answer by CHEEKATLAPRADEEP-MSFTMicrosoft employee, Moderator Sunday, July 31, 2016 9:52 AM
-
Yes you are right, when you do the deployment to Azure cloud services from VS wizard then it uploads the cspkg and csdef files 'somewhere' in the storage account you mentioned and then deploys to your cloud service by referring to that location. Now this location is willingly kept hidden from end users as you wont want to access it directly, would you?
If you wish to do the deployment by keeping cspkg and csdef files in your control then the best option is - upload those to your own storage account inside some container like 'manual deployments' and then deploy it from there.
- Marked as answer by Restless Spirit Wednesday, August 3, 2016 8:13 AM
-