e and component states.
Hope this helps,
Don Pratt
little.forest wrote:
> Just a general question: what does Repair do?
>
>
> I know "Repairs errors in the most recent installation by fixing missing and
> corrupt files, shortcuts, and registry entries". But odd something
lp.
> http://msdn.microsoft.com/hi-in/library/aa368007(en-us,VS.85).aspx<http://msdn.microsoft.com/hi-in/library/aa368007%28en-us,VS.85%29.aspx>
>
>
> Ranganatha
>
>
> On Wed, Sep 2, 2009 at 4:55 AM, Don Pratt wrote:
>
>
>> Thanks Blair and Phil.
&g
; install, so it's applying update rules. In some cases you might see a
> message something like "{guid} will not be installed because the same or a
> higher-versioned keyfile is already installed", the same situation.
>
> Phil Wilson
>
>
> -Original Mes
stand why the action for this
component is getting set to 'Null'?
Thanks,
Don Pratt
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration
ith the XML documents that use that namespace.
Regards,
Don Pratt
DONG LEE wrote:
> Dumn novice question here. So I understand what XML schema is and that we
> need to specify one on every wxs sources, like
>
> http://schemas.microsoft.com/wix/2006/wi";>
>
> But I was wondering
Hi Karen,
We have a similar build routine here (use mallow to update
files/components, followed by candle and light) and decided to make the
jump to v3 some months back. I couldn't find a v3 replacement for
mallow, so I decided to try modifying it. Since it's (unobfuscated) .NET
code, it was e
We're using WinRAR here. It's easy to setup a batch file and integrate
into a build process. You can't specify a version number. but you can
customize the icon and title (among other things).
Don Prat
David Thielen wrote:
>I took a look at 7Z but according to it's docs it doesn't even have
every compiler and linker is probably at the mercy of Visual
Studio’s environment variables
I think that's probably an accurate assessment. Take a look at the
documentation for the Win32 CreateProcess function. There's a
parameter (lpEnvironment) that let's the calling process customize the
(directed to the list at large...)
If you put the registry value in it's own component and use the same
component GUID for al of your installs, shouldn't MSI's reference
counting keep the key around until all of the apps that need it are
uninstalled?
Don
BrianG wrote:
>My company has differen
9 matches
Mail list logo