I'm specializing in Windows Tools, that's unknown in the world market. So if you know any, please send me an email about it.
If you want to make a perfect application without errors, then write the end user manual, before writing any source code lines, so follow my guidelines:
#1: Ask the company about a meeting with the CEO, and the end user, that's supposed to use the wanted application, where you are sure that the specification requirements are reviewed with all relevant facts about the features, but also about operating systems service packs, language and end users administrators credentials or not, and about the level of User Account Control, and the applications RequestedExecutionLevel manifest.
#2: Don't to start scripting the application. Not even a single line.
#3: Write a complete manual to the end user, with all the details, so that it is ready to use, without having to be revised.
#4: If it's part of the scripting, write the ini setting file according to the manual, with all the needed remark details, so that it is ready and easy to use for the end user, without having to be revised.
#5: If it's a small project, I don't think its feasible, but if it's a large complex project, send the manual to 1 weeks evaluation at the end user.
#6: Script the program and test it in relation to your manual, and solve any errors in your application and your manual, and your ini settings file if it's used.
#7: Send your application and your manual for a BETA test of the company's end user.