Hi Toru,
Can you define, and schedule the Dialog but put a condition as FALSE(0) for
it?
and I'm afraid I don't understand this
*"if call the MSP is hiddenn. if you dont call the MSP is display."*
thanks!
William L.
On Thu, Mar 8, 2012 at 3:19 PM, Toru Takeguchi
wrote:
> Hi there,
>
> I'm using
Hi,
This is only partially a Wix question but if anyone can help, I'd appreciate it.
I am writing a Wix installer for a windows service that will be installed on a
server. The installer puts files (dll, exes) into the ProgramFilesFolder and
starts the service. It is installed for all users. M
Hi,
I have a problem with a property, used in a CopyFile element, which either
should contain a complete subdirectory
path, or be empty. I guess my problem has a solution, but I don’t know how to
do it.
Description to follow.
If application XXX is installed, the environmental parameter XXX_HOME
While installing an MSI that we created with WIX we get the following. Any
Ideas?
WriteIIS7ConfigChanges: Error 0x800700b7: Failed add application to collection
WriteIIS7ConfigChanges: Error 0x800700b7: Error creating application in config
WriteIIS7ConfigChanges: Error 0x800700b7: Failed to co
As I understand from MSDN "...The *MsiFileHash* table can only be used with
unversioned files..." Within WiX is it possible to force the use of this
table for file components of versioned file types?
Thank you.
--
Virtuali
The the theoretical world, if you are following proper versioning patterns
when building your Versioned PE (Program Executable... DLL,SYS,OCX,EXE et
al ) then you shouldn't need to worry about the hash.
If you aren't ( foo.dll 1.0.0.0 or worse foo.dll version [null] doesn't
uniquely descr
I appreciate the reply. I am very aware of proper versioning practices when
developing software.
Back to the original question... I can leverage the MSIHashTable for other
reasons if it can be used for all files rather than just non-versioned
files.
So, can the use of the table be "forced" in any
I'm glad to know that you know the best practices. To answer your original
question, *NO*.
If you follow the proper practices, you won't have a need to do what you
are trying to do therefore the Windows Installer team didn't provide for a
way for you to do it.
---
If the Bundle is author correctly, you should get those extra files
correctly. They are called "layout-only Payloads".
On Wed, Mar 7, 2012 at 2:20 PM, James Johnston wrote:
> And the nice thing about an ISO is you get non-essential files as well.
> For
> example, a readme file - which I highly d
As noted above, we'll definitely be looking into improving layout
experience of WiX toolset Bundle. Clearly we missed the importance of it
and the feedback here is very useful to remind us... although the bug (
http://sourceforge.net/tracker/?func=detail&aid=3477462&group_id=105970&atid=642714)
was
Yes, it's a bug. We don't test regularly on WinXP (too many platforms to
test) so finding and reporting bugs on XP quickly is very much appreciated.
I *think* it'll be fixed for Monday.
On Wed, Mar 7, 2012 at 2:37 PM, Grant Samuels wrote:
> Hi All
>
> I was hoping someone from the Wix team could
I use heat to generate a WXS file with Fragments. I used the -var arg to
replace the path to the files with a preprocessor variable. I can specify
the variable's value in the command line to candle with the -d argument.
But, I have a wxi file that I would like to include.
I can transform the ou
I have some MSU's and MSP's that I'm running as part of an SCCM task
sequence and I'm seeing something concerning.
If I run wusa and the MSU interactively ( as either myself or system using
srunas -l ) it completes in 33 seconds.
If I run wusa and the MSU via SCCM it takes 5 minutes.
I'm w
Hi,
When I run the administrative installation of the msi (msiexec /a setup.msi) I
would like to also copy over files that are not contained in the msi (things
like the setup.exe bootstrapper, etc). What is the best way to accomplish this?
I have tried populating the MOveFile table to copy these
14 matches
Mail list logo
