As many of you know, I'm working on a custom installer for the Folding @ Home console for Team Pimprig. Part of the process for making this as complete an installer as possible is the creation of an uninstaller, not that we want you to uninstall the console, but when updates are released, having a clean slate to install on is a good idea as I have no idea how I will be handling (or even IF I'll be handling) rolling out an updater vs a brand new installer every time an update is released for the console.

The problem I have is this: Is there a way in VB.NET to have a program delete itself upon completion? Or, should I have it write a batch that will delete the program and the directories it resided in?

But, doing that method, how would I remove the batch file?

See? An interesting problem (tho one that's easily solved if I decide to say 'screw it!' and leave a file somewhere on the drive) isn't it?

This isn't a make or break kind of problem, just one for my own curiosity.

D

Yeah I think InstallSheild basically leaves around uninstall.exe.

Uninstall.exe just reads a file, follows the instructions in the file and nukes the file.

So one file left seems to be standard.

-MF

VB.NET comes with a feature called the setup wizard/setup project. It generates an installer/uninstaller program for you and it's fairly customizable. Saves a lot of time, I find. It's under setup and deployment projects in the new projects menu.

Shoulda updated this about a week or more ago. Did some messing around with batch files and solved my problem. Thanks for the input, tho.