Azure Cloud Service projects debug folder structure not equivalent to deployment
This suggestion is migrated to Developer Community. Please use below link to view the current status.
When debugging an Azure Cloud Service project in Visual Studio 2015, the folder structure contained within the "csx" directory does not match the structure of the cssx contents of the cloud service package (cspkg).
For example, packaging from VS2015 by selecting "Package" from the cloud service project context menu will result in a cspkg that contains a cssx directory. Within cssx, for a web role with a site, you'll see a "sitesroot" folder.
However, when simply running Debug for the solution, the IIS host will contain <solution_dir>\Debug\roles\<role_name>\approot, but no sitesroot directory. No degree of changing the physicalPath properties in the csdef change this behavior. The VS Debugger (full IIS host) never yields the exact same folder structure as generated in the cspack.
Matthew Morgan commented
@catherine Yes. In my use case, the role start sets folder permissions relative pathing from the role root directory. I have multiple web sites within a single web role so I am expecting /sitesroot/0 & sitesroot/1 to be valid physical paths hosted by local IIS during emulation.
catherine wang [cawa@MSFT] commented
Thanks Matthew. We are looking into this now. Would you elaborate more on what problems the folder structure would cause in your scenario?