I changed the startup file to be wrong in web.config, but kept it correct in web.cloud.config. Then publish to cloud service. Site doesn't work. I remote connect to the azure machine and noticed that web.config and web.cloud.config are different.
Comments: I have, I think, the same problem. I have a Windows Azure Web Site that I converted to a Windows Azure Cloud Service using the convert wizard. When I publish the site, everything shows up on approot as expected, and the setup_web.cmd runs, which copies web.cloud.config over web.config (among other things). So far so good. The problem is that there is another set of files at sitesroot\0, which also contains both web.cloud.config and web.config. This set of files does not reflect the changes applied by setup_web.cmd (most notably the web.cloud.config -> web.config copy overwrite). This version of web.config does get a new <system.web> section added with machineKey config. Unfortunately, the web.config in sitesroot\0 is the one that node/iisnode actually uses, which in my case, means my cloud service won't run. FWIW, "web.cloud.config is now gone" is not exactly helpful. In my project, which this tool created, I have a web.cloud.config with my cloud settings and a web.config with my local settings (and there are some important differences). If there is some new world order that doesn't involve having both files, but still somehow allows for configuration differences between the local/emulator and the cloud environments, then I'd like a little more information (enough to work around this problem).
Comments: I have, I think, the same problem. I have a Windows Azure Web Site that I converted to a Windows Azure Cloud Service using the convert wizard. When I publish the site, everything shows up on approot as expected, and the setup_web.cmd runs, which copies web.cloud.config over web.config (among other things). So far so good. The problem is that there is another set of files at sitesroot\0, which also contains both web.cloud.config and web.config. This set of files does not reflect the changes applied by setup_web.cmd (most notably the web.cloud.config -> web.config copy overwrite). This version of web.config does get a new <system.web> section added with machineKey config. Unfortunately, the web.config in sitesroot\0 is the one that node/iisnode actually uses, which in my case, means my cloud service won't run. FWIW, "web.cloud.config is now gone" is not exactly helpful. In my project, which this tool created, I have a web.cloud.config with my cloud settings and a web.config with my local settings (and there are some important differences). If there is some new world order that doesn't involve having both files, but still somehow allows for configuration differences between the local/emulator and the cloud environments, then I'd like a little more information (enough to work around this problem).