Hi There,

Sorry if I am asking a duplicate question but I was unable to find anything through a search.

When I create a package with WinINSTALL LE it tells me it's converding the NAI file to MSI but leaves the NAI file in the directory. Do I need this file or can I safely remove it?

Just curious.
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
Hi Dennis,
this question points in a wrong direction.
To create an package, is a developer job. You do it on machine where you concentrate all the stuff, which is needed to develop.
Then you take the result (the MSI) and test it on a other machine (VM). Once the result is ok, you move it to your deployment system.
If you do something like this, your question will be solved by itself.
Hope, this gives you some ideas.
Regards, Nick
Answered 03/28/2009 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
It's a while since I used WinInstall but, from what I remember, the NAI file is the native file format for WinInstall, if you were using that product for the deployment as well.

IIRC, when creating an MSI, WinInstall uses the NAI as a list of source files (and registry data?) for the MSI. Thus, if you delete it, the only way to recreate your files would be to perform an admin install from the MSI. That, of course, wouldn't get you your registry data: for that, you'd need to go to each key and export it to a .REG. Painful...

Leave the NAI where it is.
Answered 03/28/2009 by: VBScab
Red Belt

Please log in to comment
0
Thanks VBScab. That's sorta what I was thinking I just wanted to make sure.

Cheers!
Answered 03/28/2009 by: TheNerd
Yellow Belt

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