abcx
05-03-2005, 03:51 AM
Hi there.
The "Protocol" field of the "Repository" page of a Subversion command can accept only a limited number of characters. You can't enter a macro like %SVN_REPOSITORY_PROTOCOL% in it, you must rename it to something smaller.
Some actions I miss:
Delete file
Delete directory (recursive, with the option of not failing if the folder does not exist)
Move file
Move directory (Copy File is a little too much for this)
A checkbox for the devenv.exe command line option /useenv would be nice. A list box/combo box where you could select which projects from the solution to build would also be welcomed (corresponding to the /project command line option).
You could also add a action to execute DOS commands, so you won't have to add %DOSCMD% anymore, but this is not so important.
When you set an environment macro from a script language (Python in my case), it's a little annoying that you must restart the build. To have fully automated builds I must set these kinds of macros from Visual Build itself and this limits a bit the build flexibility.
Beside these little things, Visual Build Professional is excellent.
The "Protocol" field of the "Repository" page of a Subversion command can accept only a limited number of characters. You can't enter a macro like %SVN_REPOSITORY_PROTOCOL% in it, you must rename it to something smaller.
Some actions I miss:
Delete file
Delete directory (recursive, with the option of not failing if the folder does not exist)
Move file
Move directory (Copy File is a little too much for this)
A checkbox for the devenv.exe command line option /useenv would be nice. A list box/combo box where you could select which projects from the solution to build would also be welcomed (corresponding to the /project command line option).
You could also add a action to execute DOS commands, so you won't have to add %DOSCMD% anymore, but this is not so important.
When you set an environment macro from a script language (Python in my case), it's a little annoying that you must restart the build. To have fully automated builds I must set these kinds of macros from Visual Build itself and this limits a bit the build flexibility.
Beside these little things, Visual Build Professional is excellent.