I am trying to customize the WixUI_Minimal sequence. Following this:
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
And this:
http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3/
My first step was to just copy WixUI_Minimal.wxs, rename it to
For a while patching errors like:
MSI (s) (28:48) [13:52:25:298]: Product: MyProduct -- Error 1328. Error
applying patch to file C:\Config.Msi\PTCCC8.tmp. It has probably been updated
by other means, and can no longer be modified by this patch. For more
information contact your patch vendor.
Thanks Rob,
I'd like to avoid having to upgrade all our projects at this time. Is
there a version at http://wix.sf.net/releases that will work with my
\Microsoft\WiX\v3.5\Wix2010.targets style wix projects?
-Eric
On Wed, Jan 5, 2011 at 2:31 AM, Rob Mensching wrote:
> And to answer the actual
On 05/01/2011 17:15, Andy Clugston wrote:
> Yes, that was it!
>
I am glad it worked.
note: extern "C" is not needed.
> I guess I have been out of native development too long... Thanks for the
> reminder on the function export.
>
> Thanks again!
>
> On Wed, Jan 5, 2011 at 10:50 AM, Leonidas Spyrop
Yes, that was it!
I guess I have been out of native development too long... Thanks for the
reminder on the function export.
Thanks again!
On Wed, Jan 5, 2011 at 10:50 AM, Leonidas Spyropoulos <
leonidas.spyropou...@formicary.net> wrote:
> On 05/01/2011 15:30, Andy Clugston wrote:
> > Hi Users,
Yeah, pretty much all teams at Microsoft use the WiX toolset to create their
MSI files.
And yes, both Office and Visual Studio (and Expression and SQL Server and
Windows Live Essentials) have built their own bootstrapper/chainers. All of
those served as input into (and a few were influenced by) th
VS Setup is only one part of my team. Over the holiday's, I think I've just
decided to go spend more time there.
Yes, patching in the Windows Installer is truly horrid. There are also
business decisions made at VS SP time frames that stress patching even
further. It's not a great situation right
On 05/01/2011 15:30, Andy Clugston wrote:
> Hi Users,
Hey Andy,
>
> I am running into a bit of an issue while attempting to hook a C++ dll
> custom action into my installer. From all my research and debugging it
> appears that I have things setup properly. I have some tracing (message
> boxes) to
Well summed up Rob!
Am I right in thinking that both Office and Visual Studio use WiX for creation
of MSI's, or at least some of them, with an additional proprietary UI that
handles the installation experience? A while back I took a good dig into the
Office installer and was very impressed at
Hi Users,
I am running into a bit of an issue while attempting to hook a C++ dll
custom action into my installer. From all my research and debugging it
appears that I have things setup properly. I have some tracing (message
boxes) to indicate when DLLMain is entered/exited as well as my CA functio
Heh, I was hinting at my opinion of VS Install but I didn't want you to feel
attacked since that's now your team.
Personally, my biggest complaint is having to install VS then VS SP1.
It always takes longer to install the service pack then it does the MSI.
Typically the SP seems to
Sorry, I haven't been following Burn enough. I thought it was using WPF, my
mistake.
I don't remember the last time I wrote an installer for a non-managed
application so I'm not sure what that type of longevity buys me.
Chris
Christopher Painter, Author of Deployment Engineering Blog
Have
Hi,
I'm using Wix version 3.0.5419.0.
The project I'm working on is a fairly plain single featured installer.
The bulk of the installer is made up of several large (30MB+) zip files.
I've found that the patches between versions end up very large as a
result, and have determined that the zip fi
Many months ago, Mike did a lot of clean up to remove unnecessary
dependencies causing more custom actions to be included in MSI packages than
should have been. That fix caused the SchedXmlConfig to move to its most
natural position, after InstallFiles.
The action should be overridable, so you can
1. Burn doesn't require NETFX. A bootstrapper application for Burn may
require NETFX (for example, I wrote the WiX Bootstrapper Application against
NETFX4 to show how it could be done) but it doesn't have to. A pure native
solution (wixstdba.dll) is provided that runs on WinXP SP2 straight up. It
p
15 matches
Mail list logo