/build/static/layout/Breadcrumb_cap_w.png

NAI files

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

Answers (3)

Posted by: nheim 15 years ago
10th Degree Black Belt
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
Posted by: anonymous_9363 15 years ago
Red Belt
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.
Posted by: TheNerd 15 years ago
Yellow Belt
0
Thanks VBScab. That's sorta what I was thinking I just wanted to make sure.

Cheers!
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