I have two publish profiles defined for my project in Visual Studio 2010: one uses ftp for production and the other copies to my local file system for debugging and day to day development.
I have web.config transformations in place for debug and release build configurations. My project is a Facebook application where I set the application ID and secret depending on the deployment.
I would like to be able to enforce a rule such that it is impossible to use the production ftp publish profile with the debug build configuration. This combination would be disastrous and entirely break my production environment.
How can I enforce this rule?
I am open to alternative deployment methods, but am pretty happy with the simplicity of what I have now with the exception of the potential for overlooking the build configuration when pushing to production.
I have come to accept the conclusion that it is not possible, so apparently the answer is….NO