Hi all,
I've created a bootstrapper using burn which works rather well.
One thing however: If I execute the bootstrapper multiple times, I always
get the Install sequence. The install phase will then run, but since all
chained products are already installed, the system is effectively not
Hi,
is it possible to update an InstallShield Installation with WIX???
Christoph
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also
With a major upgrade, yes.
With a patch... you probably shouldn't. When we made the conversion, we found
we could create patches with Wix for the InstallShield installers but they
would crash the Windows Installer service when they were applied. The Wix
boys have said before on this list that it's
Hi,
I'm trying the omit the license agreement in one of the standard UIs
(WixUI_FeatureTree). I succeed in skipping the license agreement, when I press
'Next' in the WelcomeDlg, but when I press 'Back' on the CustomizeDlg, it
always goes to the license agreement instead of the WelcomeDlg. What
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited.
Funny, I also remember them writing a blog talking about how you could use
WiX to author patches for installers that weren't authored in WiX.
http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-did
nt-build-with-wix-using-wix-.aspx
Otherwise I agree with you. I have no
Don't do it!!! I love the fact that validation is enabled by default!!
Get faster hardware smile/
From: Rob Mensching r...@robmensching.com
Sent: Wednesday, February 15, 2012 10:16 PM
To: General discussion for Windows Installer XML toolset.
Hi,
is it possible to Copy a Folder? I don´t know if it´s possible at all?
Christoph
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also
You should be able to do it with the CopyFile element. See the help.
-Original Message-
From: Christoph Goetz [mailto:christoph.go...@giepa.de]
Sent: 16 February 2012 16:01
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Copy Folder
Hi,
is it possible to
You'd have to use a CustomAction as MSI only has the DuplicateFile table that
can make copies of files that MSI is installing. There is no built-in folder
copying mechanism. You'd also have to handle your own overwrite rules and
rollback/commit processing.
It's usually a better idea to
Here is what I ended up with:
BundleHotfix.wxs:
Bundle Name=Bundle Name HotfixRollup Version=2.0.0.0
ParentName=original_bundle_name
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
RelatedBundle Id={ORIGINAL-BUNDLE-GUID} Action=Patch/
Chain
Directory Id=CopyTestDir...
Property Id=SOURCEDIRECTORY Value=c:\doc\bin\anolis /
Component Guid=A7C42303-1D77-4C70-8D5C-0FD0F9158EB4 Id=CopyComponent
CopyFile Id=SomeId SourceProperty=SOURCEDIRECTORY
DestinationDirectory=CopyTestDir SourceName=* /
/Component
It doesn't handle
To be specific, that's not Burn making the decision, it's the wixstdba. If
you look at the open bugs on SF, you'll see that the grand majority of
burn bugs are actually bugs in wixstdba. I think you could add this to
the list. smile/
On Thu, Feb 16, 2012 at 12:03 AM, Henning Krause
True, but to get an apples to apples comparison between v2.0 and v3.x, you
need to turn off validation. Once we confirm that validation is the
performance difference all is well in the world. Otherwise, we maybe should
be hunting a perf bug in WiX v3.6.
PS: There are some other features in WiX
You are both right. smile/
Patching should work if you use the same tool to create the target MSI that
you used to create the original MSI *and* that tool supports creating new
MSIs such that patching works.
For the same reason, we do not recommend switching versions of WiX when
creating the
There is an extension in the http://wixcontrib.codeplex.com/ project that
does a recursive remove folder. It might be interesting if someone wanted
to add code there to support recursive copy using the same principles.
On Thu, Feb 16, 2012 at 8:46 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:
Thanks Rob - the -sval switch did the trick - clean checkout test ran in 68s.
I'll try this with wix3.5 on our master build tonight.
I'm sure there is a way to run the validation separately (i.e. outside of
linking) - I'll check the documentation.
We'll want to run validation as a
AFAIK smoke.exe can be used to run MSI validation outside of light.exe as of
WiX v3.0 - http://installing.blogspot.com/2006/04/msi-validation-in-wix.html
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate +
Did you just say I was right?? smile/
BTW, you probably don't want to know about the not-a-patch-patch subverted
trojan of an MSI we created at my last job. We called it SPAKL because it
was like throwing mud on the wall.
It had certain limitations but actually did work very well serving the
Understood. FWIW, I used to maintain dozens of installers each with
hundreds of features and tens of thousands of files. When it was all done
in InstallShield it was next to impossible to maintain entropy with regards
to ICE validation errors. Factoring all of that out into hundreds of WiX
I am getting Light error 0103 when the full file name length is longer
than 195 characters.
This is the error (I replaced the real file name with [filename]):
error LGHT0103: The system cannot find the file '[filename]' with type
''.
No issue when I shorten the name of the build folder so
.NET limits paths to 260 characters (or something very similar). With a
filename that is 195 characters long you'll need to make sure the rest of the
path is short enough to not hit the path limit in .NET.
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Hi
I'm working on an installer that is supposed to install a Windows service
under a user account. The user account and the password for this user
account is prompted in a dialog box and is passed to the ServiceInstall
element in WIX. We use major upgrades to make it easy to install over a
The FULL file name (including the path) is 195 characters, which is
shorter than the .NET limit. Is there any WIx/Light limit on the full
file name (path+file name) ?
Thanks
Joe
On 17/02/2012 10:03 a.m., Castro, Edwin G. (Hillsboro) wrote:
.NET limits paths to 260 characters (or something very
The remember property pattern won't help you here since the password value
is encrypted. The best thing I can think of at the moment is to put
conditions on the DeleteServices and InstallServices standard action so
that they don't fire during major upgrade. This is a hack though because
if
This is exactly what you want.
On Thu, Feb 16, 2012 at 10:09 AM, Pally Sandher pally.sand...@iesve.comwrote:
AFAIK smoke.exe can be used to run MSI validation outside of light.exe as
of WiX v3.0 -
http://installing.blogspot.com/2006/04/msi-validation-in-wix.html
Palbinder Sandher
Software
Depending where the file is used/coming from it is possible that light
added additional characters before... but usually the max size is close to
MAX_PATH.
On Thu, Feb 16, 2012 at 1:56 PM, Joe Osman joe.os...@taitradio.com wrote:
The FULL file name (including the path) is 195 characters, which
27 matches
Mail list logo
