I'd appreciate any advice on building a package containing about a dozen versioned dlls and exe's with many more non versioned xml files and document templates *.doc and *.dot.

I know that some of the non versioned files may be modified by either the users or the application, thus causing later msi's to view these as user data and not replace them. I may need to be able to replace some of these in a patch or upgrade before there is another release of the versioned files

My current package contains one exe or dll per component with the remaining non versioned stuff spread over 3 or 4 additional components.

The stuff I'm not sure about is

1 How to handle the keypaths for those components containing non versioned files so that I will be able to replace them.
2 Does adding a version to the file table have any effect for a non versioned file
3 4 Are companion files a workaround or do I need a CA to ensure the file is updated

I just need a few pointers - I'm happy to google the rest - Thanks
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Using the Version in the File table means you'll have an administrative headache. Companion files are a good choice, too. The simplest route - and one I default to, generally - is to add the containing folder(s) to the RemoveFile table.
Answered 11/04/2011 by: VBScab
Red Belt

Please log in to comment
That's what I had thought initially but I thought that InstallValidate does a sort of audit on what's happening, sees the file is to be deleted but then replaced, and says 'hold on- I"ll not bother deleting that"

Perhaps I am giving it too much credit

[EDIT] Looked that up since - seems I was wrong

Thanks for the speedy reply
Answered 11/04/2011 by: clarkeg
Yellow Belt

Please log in to comment