This blog entry might be useful...
http://blogs.msdn.com/b/ed_maurer/archive/2007/12/14/nxcompat-and-the-c-compiler.aspx
I previously did this with a post build step like what is described here.
John
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesda
We had a similar requirement and I found that I could use editbin.exe to set
the NXCOMPAT flag to no, this then stops Windows checking DEP. This applied to
a .Net exe as the compiler defaults to enabling DEP checking.
It worked for us but your app may be different.
Neil
-Original Message-
Sigh. That was it. I did actually try it the correct way before, but it didn't
work due to an unrelated error.
Now that I tried the property name in my simple (i.e. only containing the
InstallDir dialog) example it works. I will clean up my more complicated
project to correct this.
Thank you Bo
On 13-Jul-11 10:26, mylan wrote:
> InstallCertificates: Error 0x80070057: Invalid Certificate.Attributes.
Please file a bug. A workaround is to specify @Overwrite="no".
--
sig://boB
http://joyofsetup.com/
--
AppSumo P
On 12-Jul-11 10:54, Peter Stein wrote:
> It seems I can't get rid of this 2343 Error no matter how I set the
> WIXUI_INSTALLDIR property.
How did you set it? As documented, its value must be the name of the
directory property you want to specify.
--
sig://boB
http://joyofsetup.com/
-
On 13-Jul-11 11:18, Roy Chastain wrote:
> Currently I have the InstallCondition for the .MSI set to "1" to
> always force it to run regardless of whether Burn thinks it is
> installed or not. I guess another way to ask the question is, "what
> would make Burn realize that a file, msi, exe etc -
Sorry, I should have been more exact. Can you share a *verbose* log file.
Non-verbose log files are generally useless (sadly).
On Wed, Jul 13, 2011 at 7:01 AM, Peter Stein wrote:
> See below.
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Wednesday, J
> Hmm, sounds like Burn did not fully rollback the Bundle when your MSI
> failed. In that case, you might want to uninstall the previous Bundle
before
> trying the new one. Also, the Burn log file should show you (during
Detect)
> whether a package was already cached or not.
Yes, the log indicates
I'm trying to install a certificate on IIS 6 using the certificate element.
When using the CertificatePath as below, it does not work.
In log file, I found the following entry:
Entrypoint: InstallCertificates
InstallCertificates: Entering InstallCertificates in
C:\windows\Installer\MSI26A.tmp,
I think you want a "retargetable" Merge Module. I think that keyword will
help in the documentation.
On Wed, Jul 13, 2011 at 5:07 AM, Leigh Wetmore wrote:
> Hi Rob,
>
> Thanks - I ran Orca (a great tool!) on my MSI, and I found out that the
> merge module files are actually installing to a subfo
I'm trying to execute a batch file (.bat) that is copied into a predefined
location during install. I have the FileKey for the batch file generated by
heat.exe. I do not need to pass any parameters to this bat file which
contains VBScript code. The important point is that if I just manually
execute
See below.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, July 13, 2011 12:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] can't eliminate Error 2343 for InstallDirDlg.wxs in
Toolset 3.5
Nope, first email.
> The WixStdba currently prompts before downloading from internet. That
was
> very useful for testing some cases but the default is planned to
change to
>just do it...
The point of the question was that it asked AND DOWNLOADED an exe that
was not used. (Did not need to be installed.) Should it
Hi Rob,
Thanks - I ran Orca (a great tool!) on my MSI, and I found out that the
merge module files are actually installing to a subfolder within the
structure created by the MSI. The MSI files are going to:
TARGETDIR/ProgramFiles/INSTALLLOCATION
whereas the merge module files are going to:
TAR
Actually there are some discussions about related subjects here in the
mailing list. You can search the list e.g. here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
Points of interest are maybe:
- Create transforms:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Mul
By the sound of it you created an MSI that contains only your hotfixed file ?
That would explain the behaviour you're seeing.
You could make:
Major upgrade
Hotfix patch
There's a minor update but it probably won't give you any advantages over a
major upgrade.
The easiest, if you have the original
16 matches
Mail list logo
