问题
I just upgraded my web role project (and solution) from Azure SDK 2.4 to Azure SDK 2.6 using the upgrade functionality under project properties > application.
When I am building my application, everything works well but when I try to run it (and start up the Azure emulator and such) it gives the following error when I click "NO" if I want to proceeed with build errors:
unable to get setting value Parameter name: profileName
See build output:
Nothing more. When I open my output I can not find anything related to this. It looks like the build is done successfully.
If I click "YES" VS serves a popup with this message:
Failed to debug the Microsoft Azure Cloud Service project. The output directory "D:\path\to\folder\src\project\csx\O" does not exist.
Maybe it has something to do with the emulator?
Can some one help? Much appreciated!
回答1:
We also encountered this issue.
It appears that even if the Service Configuration you've selected in the Run/Debug settings is say, Dev.Local - you need to have a service configuration called ServiceConfiguration.Local.cscfg or you'll encounter this precise error.
At any case, once we created a cscfg called ServiceConfiguration.Local.cscfg this problem ceased, even though we were not referencing it.
回答2:
It's something nasty about diagnostics which the 2.7 upgrade (in my case) attaches everywhere. Remove diagnostics from your roles (web.config, role definitions) and I bet you'll have some luck.
Update: we never got to the bottom of this. Unless you are happy without diagnostics, life really is simpler if you just give in and make sure you have a Foo.Local.cscfg!
回答3:
This seems to be a catch-all error. I've just encountered it, and the root cause in my case appears to be that I had the thumbprintAlgorithm for a certificate incorrectly set. I found this out when I tried to Package... it and got a useful error message, so that's one thing to try.
回答4:
Check if you have an XML syntax error in ServiceConfiguration.Cloud.cscfg
来源：https://stackoverflow.com/questions/30196556/build-error-after-upgrade-azure-sdk-from-2-4-to-2-6