Right now we still modify ServiceDefinition.csdef to publish and startup with AzureSetup.exe. We should simply stop modifying that file, and force user to add new item -> web role support files, and copy paste the necessary xml into the csdef manually.
- We shouldn't push people using AzureSetup.exe, as it's the old way.
- Modification to ServiceDefinition.csdef doesn't work 100% of the time
- AzureSetup.exe won't pip install the requirements.txt, but the powershell script will.
- Our documentation will have fewer exceptions and gotchas
Of course, we need to keep AzureSetup.exe deployment working for existing cloud service projects. But for anyone creating new cloud service projects, they should have to use powershell script.