#1
|
|||
|
|||
version control
how does VBP handle version control in the "Make VS.NET" action? for example, does it look for AssemblyInfo.* files, Version.* files, etc.?
Specifically, i have a few VC++ projects that don't have AssemblyInfo files, and when I ask VBP to update the version in those projects, it doesn't happen. Is there a specific file or creiteria that VBP looks for to update the version in a VS project? |
#2
|
|||
|
|||
AssemblyInfo.*
Alternatively, you can use a separate Make VS.NET step with the assemblyinfo filename to update in the Filename field on the Project/Solution tab. http://www.visualbuild.com/Manual/vs...olutiontab.htm |
#3
|
|||
|
|||
So if i keep version information in a file that is not called AssemblyInfo.*, the only way to update the version in it is by using a text replacement tool?
|
#4
|
|||
|
|||
You can use a separate Make VS.NET step with the assemblyinfo filename to update in the Filename field on the Project/Solution tab.
http://www.visualbuild.com/Manual/vs...olutiontab.htm |
Thread Tools | |
Display Modes | Rate This Thread |
|
|