"Build number exists" error in Package Builder

[Thoric 2]

I'm building a package, frequently, in VIPM Builder. I'm up to Build number 98. Normally the build number auto-increases, but today it stayed the same as it was the last time I ran the builder. Consequently it is popping up an error message "The package "xxxxx.vip" already exists, do you wish to replace it?". If you choose not to replace it, VIPM then stops the build instead of increasing the build number.

 

The Build number is a disabled field, so I can't change it myself. How do I get VIP Builder to increase the build number and not overwrite an existing output VIP file? (without hacking the XML content)

Edited October 4, 2013 by Thoric

[Michael Aivaliotis 18]

Can you move the vip file somewhere else? Then it will continue.

[Thoric 2]

Can you move the vip file somewhere else? Then it will continue.

As a workaround, that's what I did. Then built it a second time to get the expected build number and restore the previous VIP file.

This wouldn't be an issue if I wasn't keeping every build, of course, so I guess most users will just choose to overwrite the existing VIP.

[Michael Aivaliotis 18]

I'm not following the problem here. VIPM, by default automatically increments the build number. So you should never have an overwrite issue. I don't know how you're getting in this situation. What is your workflow?