Software Deployment

Why not just kludge the SourceList entry in the registry to point at the original source?

[font="trebuchet ms"]I have missed the original source. So, even if i place the next build (version has changed from 3.02.0000 to 3.02.0004) source pkg, its not taking it.
Also, I tried changing the version of the next build's msi from 3.02.0004 to 3.02.0000. But still the problem exists.

Oh, hang on...do you mean you misplaced i.e. lost the original source?

If all you want to do is remove it, you could:

- delete all the files
- delete all the package's registry entries
- use MSIZap to expunge all trace of its existence from the registry.

If, however, you want to be able to use the build's source, you could build a dummy, making sure you use the Product Code and Package Code from the installed base and that you match the file versions and/or datestamp.

BTW, it sounds like you could usefully invest in some Source Control and back-up software.

[font="trebuchet ms"]yes exactly, i lost the source.
This is what i did. Capture all the installation changes using 3rd party tool like installrite.
Deleted the reg entires.

Is this the right way to remove the installed appl..

How do we create an installer from requiring the original sourve during uninstallation?

Thanks.

If the suggestion that VBScab made about creating a dummy doesn't work for you, (obviously I have no idea what your installation does), have you tried running your uninstall with logging enabled? Look at the log to see why it's asking for the original source. Maybe there's a file that it's looking for in a particular path and it just simply can't find it, you could just copy what it's asking for the the right location and it may work from there. It may not be the best solution, but it might one of your only ways out of the mess.

If you somehow backup your network share, you may be able to restore your original media. If not, maybe you should invest in some Source Control and some backup utility ;o)