Software Deployment

Hi Craig,

I have used this technique often, and it works great. We have actualy adopted it as standard practice. Using wise, when you ad the same sourcefile to an installation twice, an entry in the duplicate file table is created automaticaly. I am sure other tools will have this feature too. For the best result put the duplicate file info in the same (top level) feature as any current user keys (this minimizes the number of components being repaired).

GL

Well...

A quick test using Adminstudio 5.5 shows me not to be to sure about anything. It did not pickup the duplicate file automaticaly, it looks like it just added the same file to the source again...

Ilikebananas,

I am experiencing the same behavior. I have tried it several different ways, all without success.

The only difference is that I AM using WPS, which is where you said you had success. Is there anything special, different, or subtle you do for this when using Wise?


Craig --<>.

Hi Craig,

I'm curious to find out what the difference is.
I will tell you the way I go about it:

--If the file is already in my project, I remove it and save.
--In the Installation Expert under the files tab, I browse to the source file I want to add and select it.
--I then browse to the location in my project where I want the file to repair from (usualy I create a subfolder in the applicationfolder) and click Add File.
--I then browse to the location in my project where the file should repair to and click Add File again.
Wise automaticaly creates an entry in the DuplicateFile table.

The version I am currently using is Wise Package Studio Professional 5.00.0.151.

So far this has worked every time (last time was two minutes ago [;)] ).

Although you could always manualy edit the tables, its a lot easier if Wise does it for you...

Ilikebananas

That is definitely different than the way I have been attempting to do it, and I will give it a try here is just a few minutes.

BTW - thanks for making some time in your day to do some testing on your end.

Per jmcfadyen in the WPS forum, here is the way he suggested, and - therefore - the way I have been attempting to do it:

you need to ensure that when you put the files into the app they come from the same location.

for example

if you have

filex.dll which needs to be delivered to here

c:\test\filex.dll

and here

c:\test1\filex.dll

you need to ensure that when you add this file both locations need to come from

x:\blahblah\filex.dll

ie you drag this

x:\blahblah\filex.dll into here c:\test\filex.dll

then you drag

x:\blahblah\filex.dll into here c:\test1\filex.dll

then it will populate automagically . .

I would be happy to get it working through any means.


Craig --<>.

Ilikebananas,

You can go ahead and close this helpdesk ticket [;)] Doing all of the adding of folder and files through the Installation Expert took care of it. This is probably what jmcfadyen was telling me to do, too. For some reason, I was thinking and working outside of the Windows Installer Editor.

Craig --<>.

Ilikebananas,

Have you ever had to overcome any 2919, 2602, or any other errors after adding files?


Craig --<>.

Craig,

I'm afraid not those specific ones. The errors I came across usualy were unrelated or weren't errors, but problems with the intended repair not working. I would have to investigate them from scratch myself...

GL

Ilikebananas

Ilikebananas,

I got past the error issues I was having. It was a matter of flawed testing methodology, so I won't even get into that.

I am now on to the testing of the intended repair (without having the source .msi available), and it is not working as expected. It still looks for the .msi. I would be interested to hear some of the issues you have encountered with this, and how you resolved them.

Thanks as always,

Craig --<>.