Hi All,
We have a problem with a directory property being changed unintentionally
during MSP install which results in all of the files being installed to the
wrong directory. The value that it is getting changed to is the value of
another directory property. This is happening in our SP2 relea
That's interesting. I also work for a very large software company and we have
a highly formal process for evaluating tools with a group of people that study
these things in extreme detail and while I did have to jump through some
compliance hoops ( for example we did Fortify security scans and
I found it pretty easy and straightforward using VS2008 to attach to a setup
program awaiting user input from a message box. It was very easy...
This MSND article touches on it -
http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx -
just attach to the process that has your message
I just sat through a meeting at my employer for the last 3 months (a
significantly large software company) who told me the CPL license WIX is
released under was too restrictive to allow me to use it as a development
tool. Of course I just spent the last 2 months porting a horrific
InstallShield in
I have been wrestling with this problem for a few hors now, and I can't seem
to figure it out, or find any solid help.
I run my setup once and it install what it should and all is good. Then I
change the version number and the product ID to cause a major upgrade.
When I run it again, I'd like t
1. I have a library with some commonly used stuff call it
Library.Common.wixlib
2. I have a library which uses some parts of Library.Common.wixlib call it
Library.Product1.wixlib (so it references Library.Common.wixlib)
3. I have an additional library which uses some parts of
Library.Common.wixlib
I set the environment variable MsiBreak for native code (
http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx
http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx ) and
MMsiBreak for managed code (
http://blog.torresdal.net/2008/10/26/WiXAndDTFDebugAManagedCustomActionAndH
Wouldn't you want to just remove the TrueType="yes" attribute from each
one, thus treating them as normal files?
TrueType YesNoType Causes an entry to be generated for the file in the
Font table with no FontTitle specified. This attribute is intended to be
used to register the file as a TrueType f
You may be able to use the MSI logging if you want to trace data into the MSI
log file. Another cheap trick I've used is to set interestingly named
properties to whatever I want to see the values of. The setting of these
properties and values is logged.
Phil Wilson
-Original Message-
Ah, yes, sorry. It is a wix compiler error:
The Component element contains an unhandled extension element
'util:XmlFile'. Please ensure that the extension for elements in the
'http:⁄⁄schemas.microsoft.com⁄wix⁄UtilExtension' namespace has been
provided.
I googled this line and found a few referen
90 projects & old hardware is my guess.
We have 120 projects across 3 solutions which takes my Core 2 Q6600
approximately 25 minutes to build from a command script. The C++, C# &
Fortran projects are done in the first 15 minutes & the installers take
the last 10 (could optimize more by using more
On 25-Aug-10 09:37, Ross Inglis wrote:
> I've tried installing the 'final' WIX 3.0 build, but the errors remain.
> I'm thinking this looks like it
> 'might' be an installer SDK issue, but as far as I know, the installer
> SDK comes in with the Visual
> Studio 2008 (SP1) I'm using for this build (
Wilbert van Dolleweerd wrote:
> 2010/8/25 Ross Inglis :
>
>
>> Hi All.
>>
>> I'm hoping for some ideas here.
>>
>> I am trying to move a large project build environment from an old slow
>> Windows-XP (32)
>> machine to a (hopefully) faster Windows 7 (64) machine - mainly to cut
>> down on the cu
2010/8/25 Ross Inglis :
> Hi All.
>
> I'm hoping for some ideas here.
>
> I am trying to move a large project build environment from an old slow
> Windows-XP (32)
> machine to a (hopefully) faster Windows 7 (64) machine - mainly to cut
> down on the current
> 3-hour build time for this project. I'
Hi All.
I'm hoping for some ideas here.
I am trying to move a large project build environment from an old slow
Windows-XP (32)
machine to a (hopefully) faster Windows 7 (64) machine - mainly to cut
down on the current
3-hour build time for this project. I'm using Visual Studio 2008 SP1.
I've g
You have to extract the binary in a custom action and then run it.
Disclaimer: I recommend rethinking the problem and not doing it :)
There's a BinaryWrite CA in http://msiext.codeplex.com -
http://code.dblock.org/Source/msiext/1.1/Docs/_msi_binary_8h.html#e1b642e8fa3ad62c069a7a76eb90f688.
Her
If you're developing a custom action (or many), you might save yourself a lot
of time in the future by investing a bit upfront into unit testing your CA.
This would allow you to invoke it from CPPUNIT, assert conditions, and obvious
debug it without message boxes.
There's a post about the appro
On 24-Aug-10 12:16, Chunlin Liu wrote:
> Without requiring Installer 4.5 or higher, is there any other way to support
> it?
See Pally's reply. I doubt the MSI team would have added it had there
been an easy workaround.
--
sig://boB
http://joyofsetup.com/
---
On 24-Aug-10 21:00, Dave DaveLists wrote:
> we expected to be able to reference XmlFile using util:XmlFile but
> this is failing at compile time.
It might help if you described how it was failing...
--
sig://boB
http://joyofsetup.com/
-
On 24-Aug-10 17:45, bdwain wrote:
> the case on the upgrade too. But when upgrading, I want the box to be
> checked by default if the user has the shortcut there already, and unchecked
> otherwise. I've been having trouble getting that to work. I've tried making
> the shortcuts in components in t
On 24-Aug-10 14:50, ldy...@vorum.com wrote:
> I now wish to run the just-installed application from the installation (at the
> end), but, owing to the above, the EXE is not available till it's been
> launched
> from the shortcut!
As long as it's installed to a per-machine path, it's available t
On 24-Aug-10 11:43, Alexander Kozlenko wrote:
> Is it possible to use MsiLaunchApp in my case?
MsiLaunchApp is a control event so it's used only in the UI.
--
sig://boB
http://joyofsetup.com/
--
Sell apps to millions
22 matches
Mail list logo
