I think you also need /HIDECONSOLE - you will still see a brief console window
but it should be present all the time.
Neil
-Original Message-
From: Nick Miller [mailto:nmil...@livetechnology.com]
Sent: 02 May 2013 05:25
To: General discussion for Windows Installer XML toolset.
(wix-use
I had a similar requirement and I chose to move the SQL install out of the main
installation and in to a post install application I wrote.
Neil
-Original Message-
From: Nick Miller [mailto:nmil...@livetechnology.com]
Sent: 02 May 2013 00:03
To: General discussion for Windows Installer X
Does the installer throw a command-prompt during it's install? Burn will
hide the install package but Burn can't hide child processes if the install
package doesn't do it itself.
On Wed, May 1, 2013 at 9:25 PM, Nick Miller wrote:
> Hi All,
>
> My BA is supposed to install SQL Server express sile
Hi All,
My BA is supposed to install SQL Server express silently, however there is this
ugly black command prompt window that appears during the process. I am fairly
certain my install commands are correct, but I could be wrong... Is this a
known problem? Expected behavior? Or am I doing som
Hi this is my full working code:
extern "C" UINT __stdcall InstallDrivers(MSIHANDLE hInstall)
{
HRESULT hr = S_OK;
UINT er = ERROR_SUCCESS;
HANDLE hFile = INVALID_HANDLE_VALUE;
BYTE* pbData = NULL;
DWORD cbData = 0;
char pwzFilename[MAX_PATH], szDriv
The software I am installing is pretty complex. One of the MSI's creates 60
databases, and executes about 30Mb of SQL scripts. Verifying a working
connection to SQL is a must, and I have since realized that installing as a
prerequisite will not work as the installer allows users to connect to
FYI - The Wix Toolset (3.7) still compiles msi and burn packages on XP with
either the command line tools or via VS2010.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, April 30, 2013 10:54 AM
To: General discussion for Windows Installer XML toolset.
I came across a peculiar problem today while using Pyro to build a patch -
error PYRO0013, complaining that the length of an internal Id was too long. It
appears that Pyro had taken a file or component Id from my installer, and added
the prefix "Patch." to generate its internal Id. Pyro said tha
XP may be on its deathbed but some of us have to support it and will for quite
a while.
-Original Message-
From: David G. van Hoose [mailto:david.g.vanho...@gmail.com]
Sent: Tuesday, April 30, 2013 8:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Thanks for the suggestion. Making the MSI read-only isn't ideal because it
means the Summary tab is displayed grayed out, but it does stop the
properties from being editable. I guess I'll plan on doing this, unless a
better solution presents itself.
--
View this message in context:
http://windo
Interesting question and I've never noticed or thought about it.
By default it looks like you can edit the properties of any data file like
that, .exes seem to be blocked.
If you digitally sign your MSIs then the signature is broken if these are
edited, which is expected.
You can make the file read
11 matches
Mail list logo
