Hi Guys,

Complete packaging newbie here!
My employer in their wisdom as asked me to package a program that is stumping me at almost every turn.

Using Wise package studio im creating a new project, (packing for windows installer)
Run the create package
Now the program itself consists of 3 .exe setup "modules" and a few separate dll's (needs registration) , one .exe (needs to be registered) and a few xlt files. All the separate files need to be manually copied over existing files from the 3 .exe setups and registered.

I proceed to edit the package, removing unwanted files and reg entries etc and compile.
As for the manually copied files, the files are set to self-register unordered (ive tried customer actions too)

When I run the new msi via gui or commandline silent I get an error that the manually copied files cannot be registered.

Anything I can look at here (knowing that I probably havent given nearly enough information)?

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
ORIGINAL: Tyrelever

Hi Guys,

Complete packaging newbie here!
My employer in their wisdom as asked me to package a program that is stumping me at almost every turn.

Using Wise package studio im creating a new project, (packing for windows installer)
Run the create package
Now the program itself consists of 3 .exe setup "modules" and a few separate dll's (needs registration) , one .exe (needs to be registered) and a few xlt files. All the separate files need to be manually copied over existing files from the 3 .exe setups and registered.

I proceed to edit the package, removing unwanted files and reg entries etc and compile.
As for the manually copied files, the files are set to self-register unordered (ive tried customer actions too)

When I run the new msi via gui or commandline silent I get an error that the manually copied files cannot be registered.

Anything I can look at here (knowing that I probably havent given nearly enough information)?

Thanks


What folders are the files getting installed to and is there any information in the registry that is associated with the original files before you add the new ones to your package, also do the files already exist on the target PC?
Answered 04/24/2007 by: Tone
Second Degree Blue Belt

Please log in to comment
0
Hi Tone,

Thanks for the reply.

All files are being installed into a folder under program files (no files being copied to windows system areas etc)

The manual copy files are replacing files that already exist and mostly have reg entries (the relaced files are installed via one of the 3 .exe setups).
The senario is the vendor has given us 3 .exe setup that install 3 modules required for installation. They also provided some other files that are "hotfixes" and should replace the orginal files form the setups.

Thanks,
Answered 04/25/2007 by: Tyrelever
Senior Yellow Belt

Please log in to comment
0
first step dont manually register files.

what you want to do.

register the MSI on machine then copy the file into app as normal.

goto the component which contains the item you just copied in, you have options on right click to rescan advertising.

this will import the registry required.


alternatively there is a tool called Wisecomcapture.exe on the wise server installation.

Use this in a similar way to regsvr32. the difference being this will create an output file in .reg format which you can them import into your package.

using either of these methods will allow reference counting etc to function as designed.

manually registering is dangerous from a sociability perspective.
Answered 04/26/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Thanks jmcfadyen,

When you say register the msi on the machine - How is this possible during the setup capture session?

I understand it so - register something and copy the file into the app (within the setup cpature)

then once fully captured goto the component and rescan etc.

Is that correct?
Answered 04/26/2007 by: Tyrelever
Senior Yellow Belt

Please log in to comment
0
oops typo ..

i meant register the DLL on the machine you are editing the MSI on.
Answered 04/26/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
ah ok, so during the capture; copy the files over and register (regsver32) them. Once complete refresh the components etc?
Answered 04/26/2007 by: Tyrelever
Senior Yellow Belt

Please log in to comment
0
Or, capture the installation without registering them, then, save your project.. Use wisecomcapture to extract the registry information from your dll's.. Import the regkeys in your project. That should work aswell..
Answered 04/27/2007 by: neo2000
Purple Belt

Please log in to comment
0
yeah what he said..
Answered 04/29/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity