Software Deployment

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

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.

Yes you can still use it.
Is your files are installing directly in C:\ or into some directory like C:\Application?

Jeeoo!
Santro

Yes it is installing directly C:\

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

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.

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.

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

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.

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

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.

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!

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.

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.

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.

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....

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? :)

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

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