/build/static/layout/Breadcrumb_cap_w.png

RemoveFileTables

Hi,

I am new to Wise Package Studio. I haveno idea in editing the tables in Wise Package Studio. I need to edit RemoveFileTables to add some some files so as to delete the files after installation. Could anybody help me by giving an example to illustrate how to edit in RemoveFileTables.

Thank You,
S.Yuvaraj.

0 Comments   [ + ] Show comments

Answers (19)

Posted by: zipsantro 16 years ago
Purple Belt
0
I suggest you to use "Installation Expert" to make entires to RemoveFiles Table as you are new to WPS.
1. Goto Files section under Installation Expert
2. Goto the directory where required files are available. You should see the list of files.
3. Click Operation --> Remove File.
4. Provide the filename and select Uninstall in "Remove During" list.
Doing this will automatically makes an entry in your RemoveFiles Table. In this way you dont have to specify the key name of your directory or file and it automatically selects/creates the Component.
For safer side just go and verify the RemoveFiles Table and make sure that the component selected is not permanent.

NOTE - You can use wildcards in FileName section accroding to your requirement. For Example -
Delete all Files = "*"
Delete all dlls = "*.dll"

Jeeoo!
Santro
Posted by: Yuvaraj_Subramanian 16 years ago
Senior Purple Belt
0
Thanks for your reply. Actually we are creating a mst for avendor msi. Actually while installing the vendor msi it puts all files into directly C: Drive So as per your advice can i do the same. Kidnly advice.

Thanks & Regards,
S.Yuvaraj.
Posted by: zipsantro 16 years ago
Purple Belt
0
Yes you can still use it.
Is your files are installing directly in C:\ or into some directory like C:\Application?

Jeeoo!
Santro
Posted by: Yuvaraj_Subramanian 16 years ago
Senior Purple Belt
0
Yes it is installing directly C:\
Posted by: zipsantro 16 years ago
Purple Belt
0
I am afraid, in this case you can't use "Installation Expert" as file component points to TARGETDIR and Operation button will be disabled. You need to add it manually in RemoveFile Table.
So, your entry may look like this
FileKey Component FileName DirProperty InstallMode
------------------------------------------------------------------------------
RemoveFile01 Component1 FileName.txt TARGETDIR 2
------------------------------------------------------------------------------
Where Component1 is the one who is installing the file and can be found in File Table.
Filename will be the actual filename.
DirProperty will be the Directory_ column of your Component Table.
InstallMode will be 2 (Unsinstall)

Jeeoo1!
Santro
Posted by: anonymous_9363 16 years ago
Red Belt
0
ORIGINAL: zipsantro
I am afraid, in this case you can't use "Installation Expert" as file component points to TARGETDIR and Operation button will be disabled. You need to add it manually in RemoveFile Table.
One *could* use the UI to build (what I call) a placeholder entry in the RemoveFile table and then edit the table directly afterwards. That might make the operation a little less scary for the beginner.

Yuvaraj, follow Santro's advice as above in post #2 but pick an innocuous file from your workstation, e.g. a log file from the Windows folder.

Oh and remember to choose 'During Install' or, if editing the table directly, to set the InstallMode to '1' (Install) - Santro has been advising you about removing during uninstall, whereas you asked for remove during install.

EDIT:
Look what I found, using this new-fangled search thingy called Google: http://www.prairienet.org/~pops/msi_tips.html

Lastly, this post really belongs in the 'Package Development' forum.
Posted by: Yuvaraj_Subramanian 16 years ago
Senior Purple Belt
0
Hi,

I have added all the installation that has to be removed after the application is installed but still it is not working(i.e) the files are not getting removed.

Here is how i worked:
1) I entered Installation Expert in Wise Package Studio
2) Under Files Section in destination computer it showed all application files.
3) Rightclicked the file selected operation and selected Remove File and entered the below datas:
i) Under directory i gave the value as Globall Assembly Cache (since the installation file puts all the installation file directly in C:\)
ii) Under file name i entered the file name that is to be deleted
iii) Under Remove During we selected Installation.
4) After providing the above data the same files comes with red 'x' mark under Global Assembly Cache.
But still it does not delete any files after the msi is being installed kindly help me to overcome this.
Posted by: anonymous_9363 16 years ago
Red Belt
0
ORIGINAL: Yuvaraj_Subramanian
3) Rightclicked the file selected operation and selected Remove File and entered the below datas:
i) Under directory i gave the value as Globall Assembly Cache (since the installation file puts all the installation file directly in C:\)
Why did you do that? The GAC has nothing to do with your files. Post a list of files and the containing folders that you want to remove. That is, produce a list that looks something like this:

C:\Setup
C:\Setup\Setup.EXE
C:\Setup\Setup.INI
C:\Setup\ProgFiles
C:\Setup\ProgFiles\MyProduct
C:\Setup\ProgFiles\MyProduct\MainEXE.EXE
Posted by: Yuvaraj_Subramanian 16 years ago
Senior Purple Belt
0
Hi,

The Problem is that it actually put the file directly into the root drive like below:

C:\setup.msi
C:\eula.1028.txt
C:\install.red.dll
C:\a.bmp

Kindly advice how to remove these files in removefile table.
Posted by: zipsantro 16 years ago
Purple Belt
0
Files installing under C:\ are points to "TARGETDIR" in your MSI not GAC. Select TARGETDIR in DirProperty in your RemoveFile Table. If you actually look and understand directory table, it starts from SourceDir-TARGETDIR-Programfiles-InstallDir and many more. Your RemoveFile Table should look like this.

FileKey Component FileName DirProperty InstallMode
------------------------------------------------------------------------------
RemoveFile01 Component1 setup.msi TARGETDIR 1
RemoveFile02 Component1 eula.1028.txt TARGETDIR 1
RemoveFile03 Component1 install.red.dll TARGETDIR 1
RemoveFile04 Component1 a.bmp TARGETDIR 1
------------------------------------------------------------------------------
To know full detail please refer Windows Installer Help.

Jeeoo!
Santro
Posted by: anonymous_9363 16 years ago
Red Belt
0
ORIGINAL: Yuvaraj_Subramanian
The Problem is that it actually put the file directly into the root drive
Don't forget, once you have your working MSI, to send an email to the vendor offering your services for packaging their software into something resembling appropriateness. Who on earth in this day and age thinks it's acceptable (or even possible) to drop junk on the root directory of the system drive? I mean, it's not like %TEMP% is a State secret, is it? Jeez....

Now, please, do follow though with that. All the while these fools get away with this stupidity, they'll just carry on doing it.
Posted by: Cybermage 16 years ago
Orange Belt
0
VBScap,

I totaly argree with you're arguments. I have regulare basis sometimes hard conversations with vendors. But with medical applications is the most time the reality that there is only 1 vendor/supplyer. Even with ms office i can choice openoffice but not with most medical stuff. So the vendor say you doing it our way or the highway :< and the get away with it!
Posted by: anonymous_9363 16 years ago
Red Belt
0
I don't mean that you should try and find an alternative, just that you 'educate' them. Why not offer them your MSI when it's complete? That will bring them into 2008, as opposed to 1985.
Posted by: Yuvaraj_Subramanian 16 years ago
Senior Purple Belt
0
Hi,

I am giving an example below as how i entered the values in the RemoveFile Table

FileKey Component FileName DirProperty InstallMode
------------------------------------------------------------------------------
RemoveFile01 Component1 setup.msi TARGETDIR 1

For Component_ i entered the value of the file name that is shown in component eg: C_VC_red_a

For File name i entered as e.21.txt

am i right?
kindly advice.
Posted by: Cybermage 16 years ago
Orange Belt
0
VBScab

Beleave me the sessions i have with vendors are very educative for them and lot of free advise.
But there are few reasons i do not offer my MSI's to the vendors

1) The most msi i built and tested true only for the specific envirements i build for. Most time the msi contains envirement specific settings so the msi are not 1 tot 1 portable without modifications. (and knowledge of modifying of building msi's is just what the most vendors lack of it)

2) I do not know how it in you're country i do not think it is a nice sitution when a other site used by vendor deliverd msi build by me and something there go's very wrong. In the most positive way you have to support the other site if the vendor point the finger to the builder or a more worse case a sitution when layer came around.




ORIGINAL: VBScab

I don't mean that you should try and find an alternative, just that you 'educate' them. Why not offer them your MSI when it's complete? That will bring them into 2008, as opposed to 1985.
Posted by: Jamie B 16 years ago
Orange Senior Belt
0
I've seen instances of MSI's dumping assemblies directly to the root of c: when either the wrong version of .NET is installed on the target box or .NET isn't installed at all....
Posted by: anonymous_9363 16 years ago
Red Belt
0
ORIGINAL: Cybermage
1) The most msi i built and tested true only for the specific envirements i build for. Most time the msi contains envirement specific settings so the msi are not 1 tot 1 portable without modifications. (and knowledge of modifying of building msi's is just what the most vendors lack of it)

2) I do not know how it in you're country i do not think it is a nice sitution when a other site used by vendor deliverd msi build by me and something there go's very wrong. In the most positive way you have to support the other site if the vendor point the finger to the builder or a more worse case a sitution when layer came around.
That's fine. I just thought you might want to make a few pennies out of a brain-dead vendor. How long would it take to remove your site/client-specific stuff? An hour? A day? As for support, your sale contract would button that up, by assigning responsibility to the vendor. Anyway, you're clearly not interested so we'll leave it there, shall we? :)
Posted by: anonymous_9363 16 years ago
Red Belt
0
ORIGINAL: Jamie B
I've seen instances of MSI's dumping assemblies...<snip>
No apostrophe required for plurals, JB. The 'apostrophe-S' construct is for indicating possession, as in "The boy's football" i.e. the football belonging to the boy versus "The boys were playing football" i.e. more than one boy was playing football.

Happy to help...LOL
Posted by: Yuvaraj_Subramanian 16 years ago
Senior Purple Belt
0
built and tested true only for the specific envirements i build for. Most time the msi contains envirement specific settings so the msi are not 1 tot 1 portable without modifications. (and knowledge of modifying of building msi's is just what the most vendors lack of it)

Hi,

I have solved this problem by writing a vbscript in the custom action.

Kindly accept my sincere thanks for giving me some idea in remove file table since i am new to this wise package studio.

Thanks & Regards,
S.Yuvaraj
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ