+1 on this... something like C#'s XML Documentation or Sandcastle for WiX
would be huge.
Seeing that WiX projects are just XML files, probably the solution would
involve some sort of XSL translation.
DexterSinister wrote:
>
> How are folks here documenting their installation packages ?
>
> Ar
Our product versions mostly conform to the major.minor.build convention
specified by the MSI standard, but sometimes we have to put letters in the
strings to indicate an update or "hotfix", i.e. 1.0.5.U1 or 2.4.16.HF02.
Obviously this is a big no-no to have letters in ProductVersion property.
Wor
here that has to deal with weird product
versions...
lesterbangs wrote:
>
> Our product versions mostly conform to the major.minor.build convention
> specified by the MSI standard, but sometimes we have to put letters in the
> strings to indicate an update or "hotfix", i
Per the howto in the v3 helpfile, I've been first defining the folder
structure of a project then adding the files via DirectoryRef's.
Now that I am adding more functionality to my projects, I find it much
easier to work with if I separate the file into logical chunks, such as IIS
configuration
Our products run on an Oracle 9i/10g backend; one of the requirements for
installation is to verify a particular version of a DB schema on the server.
Right now this is accomplished via running "sqlplus.exe @scriptname.sql",
logging the output to a file, then parsing the result.
In order to ma
Using WiX 3.0.5106.0, I'm not seeing this behavior; Inside a fragment, I am
specifying file entries under a directory ref like so:
etc...
When the product is installed, the assemblies appear in both MyFolder, and
the GAC. This is contrary to what Eitan is saying (Ass
Our products require Oracle. The default Oracle Home on the target machine
needs to be determined in order to configure the product. This value is
stored in the registry but unfortunately it is not easy to retrieve due to
the convoluted way Oracle configures multiple homes.
Basically the proced
I am using the Bootstrap Manifest Generator to build a bootstrapper which will
search for and install third-party prerequisites on the target machine (Flash,
Acrobat, etc).
Since BMG-- and most other bootstrapper builders I have encountered-- leave the
bare MSI exposed in the same location a
I am converting an installer written in InstallShield 12 (non-MSI based) to
WiX. The InstallShield one manages to violate nearly every best practice,
so even forcing the end-user to do a complete uninstall of it before running
the MSI leaves the system in a potential mess. Some of the things I h
Hi Hukum, you can achieve this using "QtExec". Look in the WiX.chm help
file under Advanced WiX Topics->Standard Custom Actions->Quiet Execution
Custom Action for more info.
Hukumchand Shah wrote:
>
> Hi All,
>
> I am executing some batch files from wix custom actions. I want to
> suppress
>
again for your help, and Chris too!
Richard-45 wrote:
>
>
> In article <1240352013685-2672846.p...@n2.nabble.com>,
> lesterbangs writes:
>
>> In this case, is it ok to run this cleanup procedure as an immediate
>> action?
>> What are the potential pitfalls
11 matches
Mail list logo