busytoby
03-14-2007, 06:45 AM
I see that support for specifying the product version from the command line has been added -- this is awesome! Are there any plans to add support for command line switches to modify other attributes? For example, we have an msi project that is built in several automated loops drawing from different source files (per-revision, nightly, release, and manual builds).
It is a little kludgey in my opinion to use automation to more or less open the project, update the paths, resave the project, and then rebuild based on the new source location considering that we might do this 20-30 times in a day when we're trying to push a release out the door.
right now it's accomplished this way by a vbscript wrapper that accepts command line arguments like -IPATHVARIABLE=X:\source\location .. it works, but it seems silly to me that this sort of script is needed at all.
It is a little kludgey in my opinion to use automation to more or less open the project, update the paths, resave the project, and then rebuild based on the new source location considering that we might do this 20-30 times in a day when we're trying to push a release out the door.
right now it's accomplished this way by a vbscript wrapper that accepts command line arguments like -IPATHVARIABLE=X:\source\location .. it works, but it seems silly to me that this sort of script is needed at all.