2
Vote

.csdef and .cscfg files not honored

description

The current version of the command line tools seems to skip over .csdef and .cscfg files and create it's own. This is a problem if a developer needs to create a custom configuration (Sure they could edit the deploy files, but why the extra hassle).
 
I located this when I was creating a worker role. In order to create a worker role 2 parameters must be passed on the command line. The tool then creates the configuration file automatically with the worker role in it. While this works it is far from ideal. In order to make the command line tool more usable and efficient the .cscfg and .csdef files should be read from the project directory and used.
 
For possible implementation, the user could pass the file names as an optional parameter on the command line, if the parameter is not available look for the default names of ServiceDefinition.csdef and ServiceConfiguration.cscfg, if those files are not available build them automatically as they are now.

comments

wham wrote May 3, 2011 at 10:16 PM

I'm having the same issue also with Web.config file. Project version contains some rewrite rules and after each build I have to merge them into newly created Web.config file manually.