I have some directories that are 0 in size that my setup creates. When running the Repackager, it does not get those directories, I'm guessing since their's no files in them; however, when I run the created msi file and then launch the program, it fails due to not finding these directories. Any ideas? I'm thinking about manually editing the xml file and adding those directories just to see, but I'd rather the program itself get what it should.
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
We'll take a closer look- it should indeed include the new directories even if no files are being placed in them.

Thanks,
Bob
Answered 10/28/2008 by: bkelly
Red Belt

Please log in to comment
0
FYI... I tried again and this time I put some garbage txt files in those empty directories and finished the the Repackager wizard. It must have noticed those occupying directories because it worked for me this time. Might be a bug in the program.
Answered 10/28/2008 by: rgaudet
Senior Yellow Belt

Please log in to comment
0
Ok... Is it just me not knowing how to use this program or making assumptions I shouldn't. I have it band-aided with the junk files in the directories referenced above, so I think I'm home free, so I recreate the project to include an ini files it creates after launching the software to point to some data paths. I then finish the wizard of the Repackager to find that it does not see those files (those are definitely file in existance and are bigger then 0k). Shouldn't the software look at all files regardless of if they are of size or extention?
Answered 10/28/2008 by: rgaudet
Senior Yellow Belt

Please log in to comment
0
Yes it should detect any changes (including newly created empty directories). The size and extension should not play a role at all. As long as it is a file or registry change made after the initial snapshot and before the second, the repackager should detect and include the item. The development team is looking into it now. Please continue to post any details here as it will help to ensure we understand the problem and can ensure a fix is in our official 1.0 release due very soon (still beta right now).

Thanks!
Bob
Answered 10/28/2008 by: bkelly
Red Belt

Please log in to comment
0
Just for giggles, I tried WinInstall LE and it worked fine. The only issue with it is instead of packaging it into one msi file, it creates the new directories, reg key, etc... outside of the msi and ties to it. I'd rather use the Repackager to get the one file if possible so I'll stay tuned.
Answered 10/28/2008 by: rgaudet
Senior Yellow Belt

Please log in to comment
0
Bob,

Does AppDeploy Repackager add to the CreateFolder table for empty folders as otherwise Windows Installer during install will remove these (empty) folders included in the package.
Answered 10/28/2008 by: AngelD
Red Belt

Please log in to comment
0
I'm glad you pointed this out, the current beta is not using the CreateFolder table; taking that on as a bug now.

Thanks!
Bob
Answered 10/29/2008 by: bkelly
Red Belt

Please log in to comment
0
NP, is it fixed now [;)]

/Kim
Answered 10/29/2008 by: AngelD
Red Belt

Please log in to comment
0
I just downloaded beta 2 and again, tried packaging my application with it. Seems like it did a little better job, but still skipped my empty directories which my app didn't like.
Answered 11/06/2008 by: rgaudet
Senior Yellow Belt

Please log in to comment
0
Unfortunately, in the "known issues" you'll see the creation of empty folders was still an issue in Beta 2. The hope is to release the final build today, but time will tell ;)

http://itninja.com/blog/view/appdeploy->-appdeploy-tools->-known-issues
Answered 11/07/2008 by: bkelly
Red Belt

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