We are implementing Team Build and know that we need to write MSBuild scripts to create our legacy VB 6 app is. It is configured to use binary compatibility and we sometimes break the relevance and we want our new automatic building process to automatically be able to automatically break compatibility.
How does anyone have to do this or is it even possible?
Alternatively, I know that brakes are just as consistent with the changes in compatibility, compilation, binary and recompilation. If someone knows how to change the compatibility with the command line, it will also be helpful.
Contemporary compatibility with the change, I used to do things like Unix-style tools (sed, Awk, and / or perl) in the project file. Do not change the original project file, but instead create a new / temporary project file, and create it with. Here is an example:
sed -e "s / compatible mode = 0 / compatible mode = 2" & lt; MyProj.vbp & gt; TmpProj.vbp
You can use this technique for other purposes, like entering the version number in the project file.
Comments
Post a Comment