You may have other problems to deal with also. At places I've worked, the doco
people have been really horrible. The first typical problem ( which you are
already describing ) is that they have no concept of integration, design by
contract or abstraction.Not only will their build output
Yes you are right, guys... Dynamical file linking is normally very
dangerous operation, from logic reasons... But there are situations,
when it is really useful.. In my case we have any static-html
documentation of our web application and i need to include it as it
comes from our documentation team
I know the feeling. I have it baked into my build automation to run a unit
test that compares the available files to an administrative install. If any
files are new in the build area but missing in the installer, a build error is
thrown.From there we find out who put the files there and m
Hey Chris,
I would say that dynamically linking files can be an issue but there are
some products out there that need to do this. The biggest thing I can see is
not what files should be included. In our product deployment cycles we would
run binary delta compares to ensure release integrity, know
Richard <[EMAIL PROTECTED]> wrote:
>> A semi easier solution is to write something that calls "heat dir" each
time
>> to generate a .wxs you include in your build. Should take about a day of
>> dev/testing.
>Ah, much better, thank you.
Funny, InstallShield has had this functionality
Yes you are right - I forgot uninstall :-(
The problem is, that directory with documentation is delivered by
third party company and I do not want to check directory structure
everytime after documentation delivery...
So I created folowing functionality using mallow.exe utility:
1.) Into our .wixp
In article <[EMAIL PROTECTED]>,
"Karthik Krishnan" <[EMAIL PROTECTED]> writes:
> You'll need a custom action for that. You'll have to include code that
> cleans up your unzipped files on uninstall so you don't leave files on the
> system.
And you'll need code that handles rollback. And you
I'm just guessing here, but I take it the directory structure and/or names
of your documentation files are unpredictable, and you want to get around
that by zipping up the files into a predictably named zip file?
You'll need a custom action for that. You'll have to include code that
cleans up your
> I need to include ZIP archive (documentation in any directory
> structure...) into MSI and after installation I need to unzip it. Does
> anybody any idea how to do it?
> Encapsulation of documentation's directory structure is not so useful
> for me...
Why do you want to do this? The files will
In article <[EMAIL PROTECTED]>,
"David Stindl" <[EMAIL PROTECTED]> writes:
> I need to include ZIP archive (documentation in any directory
> structure...) into MSI and after installation I need to unzip it.
Why don't you just distribute the files with a CAB? Then everything
is integrated w
10 matches
Mail list logo
