At the moment I'm really looking for the best way I can be sure there's something to roll back to.

The Project hook is probably the best bet.

Qa here consists of putting it in front of the user till it stops falling over.

>I agree with Craig. The same process should be adhered to for all apps. Just a note, QA tests in all three stages he listed and it doesn't pass to go on to the next phase until that occurs. Regression testing falls into that as well... No matter how simple the app, it's important. The simpler the app, the quicker the testing.
>
>
>>Thank Craig
>>
>>did you not read "This is a maintenance only sort of system so I'm looking for the minimalist approach.".I think if I mention build methodolgy and continuous integration to the holders of the purse strings I'll get a poke in the eye.
>>
>>but have you got a link to your concept there ?
>>
>>Nick.
>>
>>>You're putting a band-aid on a bigger problem. The band-aid is fine, but should only be temporary. You should really look at your entire build methodology and look at Continuous Integration.
>>>
>>>- Local builds should be per developer and should only affect the .exe in the development environment
>>>- Build servers should build and test your application, then report back the results.
>>>- Once results are satisfactory and pass all tests with all new functionality, you can build a release version.
>>>
>>>>When I build a new exe I'd like to automatically back up the previous copy. In case things go pear shaped and I have to revert.
>>>>
>>>>I do it manually but thats not a great way to go.
>>>>
>>>>Whats the best way to do this.
>>>>
>>>>This is a maintenance only sort of system so I'm looking for the minimalist approach.
>>>>
>>>>Thanks