Changing TARGETDIR in Installer Class

Question

1.00/5 (1 vote)

See more:

VB

Hi Friends,

Changing [TARGETDIR] in Installer Class...

Posted 30-Nov-12 21:22pm

PunithaSabareeswari

Add a Solution

Comments

JITHIL P PONNAN 1-Dec-12 4:28am

Is this a question or just some quotes?????

Please don't spoil this site's quality.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2012-12-01T03:25:00

You shouldn't be doing that unless you have a damn good reason to do so. Changing the TARGETDIR at the wrong time during an installation can break your app installation AND make it impossible to uninstall.

You have to keep more than a few things in mind when doing this. You can't just assume your installer wil ever be used to do just an install. There are also Admin installations, Maintenance (Repair) installs, and Uninstalls. Changing the TARGETDIR for an Install doesn't necessarily mean that the same method you use for changing the TARGETDIR during install is going to get executed during the other uses for your installer.

Read this[^].

If you really are going to process to do this, DO NOT DO IT using the Setup project in Visual Studio. Use a professional installation package builder project, like InstallShield.

Oh! And another thing. You also have to consider the possibility that your app is being installed/maintained/uninstalled on a 64-bit machine where the Program Files folder can have a different name depending on the bitness of your installer/app.