If you want to force a package to run during modify, change the requested
state in OnPlanPackageBegin(). The default will be a no-op.
On Wed, May 8, 2013 at 5:51 PM, Christopher West C <
christopher.c.w...@ericsson.com> wrote:
>
> I would like to have my custom bootstrapper allow for an installe
Following are my requirements
a) I need to check the .Net 3.5 prerequisites and if it is not present, must
install the .net
component followed by the instllation of my application which includes copying
the files to Programs files.
Can any one suggest is there any way to the do the same i
I would like to have my custom bootstrapper allow for an installed MSI to be
modified via the MSI's UI. If I install the .msi directly, I am able to do
this from the ARP via the change button.
I tried to accomplish this same behavior via my custom bootstrapper. In my
custom bootstrapper, I t
Why reinvent the wheel? MSI can handle starting a service for you.
Create a ServiceControl record and tie it to a component and put the
condition on the component. This way your CA doesn't have to worry about
starting the service, it'll get taken care of when StartServices runs.
---
I've had this happen to me on pre-WiX projects. What was wrong in my case is I
did not up the AssemblyKeyFileVersion-attribute (or what it's called again) in
the AssemblyInfo.cs of the project for the DLL that wasn't replaced. I'd
upgrade only the AssemblyVersion, and found out the Windows Insta
I have a deferred custom action that has Impersonate set to "yes" to execute
some SQL commands. Conditionally, it also needs to start a Windows Service.
Windows service fails to start because impersonate of "yes" lacks sufficient
privileges. Is there any way to change the impersonation within
Thanks Rob. Are there any other non-MSI based approaches that you feel may
be worthy of consideration?
I feel very confident in my ability to deliver an MSI based solution for
n-Tier ASP.NET solution, I just want to make sure I'm not ignoring other
reasonable solutions.
-
Thanks, but that's not what I am looking for. That is the
InstallExecuteSequence, what I am looking for is the sequence that Burn runs
through, like DetectBegin, DetectComplete, PlanBegin, PlanComplete and so on.
-Original Message-
From: Jeremiahf [mailto:jeremi...@gmail.com]
Sent: Wed
>
>
>
> The major upgrade pattern seems to be what you were trying to achieve and
> it's the tried and trusted way of getting what you want.
>
> Follow this http://wix.sourceforge.net/manual-wix3/major_upgrade.htm
that's exactly what we've been doing (as sais this scheme has worked for us
for a c
Classification: Public
Nope a repair would not have worked since you installed WIX before you
installed VS2012 so the bits for 2012 were not installed and the repair
wouldn't have installed them either :)
-Original Message-
From: Joe Barker [mailto:joeb...@gmail.com]
Sent: May-08-13 12:2
The setup I had was VS2010 and WiX, installed in that order.
I then installed VS2012, and I came across the issue described earlier.
To resolve that issue, I tried repairing the WiX install, to no avail, so I
uninstalled and reinstalled WiX, which resolved the issue.
I do agree, however, tha
http://wix.sourceforge.net/manual-wix3/wix_xsd_installexecutesequence.htm
Hope this is what you need.
Thanks,
J
On Wed, May 8, 2013 at 10:11 AM, Nick Miller wrote:
> Hi All,
>
> I was wondering if there is some documentation somewhere that details the
> execute sequence that burn goes through
I see you have this fixed but just for completeness did you install WiX and
then VS2012? If so that is the problem, WiX needs to register itself with VS
and if VS isn't there it can't - a repair of WiX should also have fix the
problem.
Neil
-Original Message-
From: Joe Barker [mailto:j
Thanks both, uninstalling and reinstalling did the trick.
Joe
On Wed, May 8, 2013 at 4:22 PM, Jeremiahf wrote:
> I had the same issue with 3.6. My solution was to completely uninstall WIX
> and re-install it.
> On Wed, May 8, 2013 at 10:05 AM, Joe Barker wrote:
>> Hi,
>>
>>
>> I have WiX 3.7
I had the same issue with 3.6. My solution was to completely uninstall WIX
and re-install it.
On Wed, May 8, 2013 at 10:05 AM, Joe Barker wrote:
> Hi,
>
>
> I have WiX 3.7 installed, and recently upgraded to VS2012; since the
> upgrade to 2012, I can't open the Installer solution I'm using. I t
WiX v3.7 works fine for me in VS2012. You will likely need to reinstall the
WiX toolset if you haven't done that already.
On Wed, May 8, 2013 at 8:05 AM, Joe Barker wrote:
> Hi,
>
>
> I have WiX 3.7 installed, and recently upgraded to VS2012; since the
> upgrade to 2012, I can't open the Instal
Hi All,
I was wondering if there is some documentation somewhere that details the
execute sequence that burn goes through on install?
Thanks,
Nick
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases"
Hi,
I have WiX 3.7 installed, and recently upgraded to VS2012; since the upgrade to
2012, I can't open the Installer solution I'm using. I tried running the WiX
installer again to repair the setup, but the project still won't open. Does
anybody have any idea why this might be, what with VS2012
. And the only thing I can think of that by design will not overwrite
according to file version rules is the NeverOverwrite flag in the Component.
If that was ever set for that guid on a system then it will be sticky on
that system. It can't be turned on or off in an MSI file to change the stat
I dislike WebDeploy for a number of reasons:
0. Fundamentally, WebDeploy operates using a "sync" concept. It tries to
make a machine look like other machines. You can package up a bunch of
these settings but it's still just applying settings to make the machine
look like another. That fundamental
I've never heard of threads having a bitness. MSI installs happen in the
Windows Installer process so it'll be done how they do it.
On Wed, May 8, 2013 at 6:58 AM, victorwhiskey wrote:
> So I guess once the BA detects a x64 system then it will kick off a 64 bit
> thread to launch the x64 MSI?
>
So I guess once the BA detects a x64 system then it will kick off a 64 bit
thread to launch the x64 MSI?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MBA-build-to-specific-platform-x86-or-x64-or-anycpu-tp7585672p7585731.html
Sent from the wix-us
Thanks Rob!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MBA-build-to-specific-platform-x86-or-x64-or-anycpu-tp7585672p7585730.html
Sent from the wix-users mailing list archive at Nabble.com.
The major upgrade pattern seems to be what you were trying to achieve and
it's the tried and trusted way of getting what you want.
Follow this http://wix.sourceforge.net/manual-wix3/major_upgrade.htm
Do not mess with reinstallmode in your bootstrapper, leave the defaults. You
could even use burn
http://www.wixtoolset.org/
-Original Message-
From: Markus Wehrle [mailto:mar...@laika42.com]
Sent: May 8, 2013 8:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] build a download manager installer?
Yes, i mean wix burn.
Am 08.05.2013 um 13:16 sch
Yes, i mean wix burn.
Am 08.05.2013 um 13:16 schrieb Yuliang li :
> thank you Wehrle!
> Do you mean WiX Burn? I have googled it and found some pieces of documents,
> However, I haven't found any official webpages for this.Where could I find
> the documents about it?
> I am building an application
Hi Rob,
I have prepared a msi installer in windows XP sp3 and trying to install
it in Windows 7
The package attaches the sql server 2008 database which is happening
perfectly fine in XP but in Windows 7 the database is getting attached
as READONLY
Please share your expertise.
Thanks and Regard
thank you Wehrle!
Do you mean WiX Burn? I have googled it and found some pieces of documents,
However, I haven't found any official webpages for this.Where could I find
the documents about it?
I am building an application using tideSDK and now I am trying to custom
the installation process by modif
Add a SKIPCONDITIONS property to each of your conditions and pass that in.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 08 May 2013 09:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Skip Bundle Condition
You could impl
hi all,
it's been a while, which means wix has worked great for us for a long time
now, but just recently we've hit a weird one:
we're providing regular upgrades packaged as msi's bootstrapped in an exe.
(the exe places the msi into windows temp, and invokes the lib equivalent
of msiexec /i blahb
Hi, you can achieve this using burn.
Am 08.05.2013 um 11:12 schrieb Yuliang li :
> hi
> does anyone here know how to build a installer with download manager? So
> the user would download a lightweight installer, select the components they
> want to install and the installer would download the nec
hi
does anyone here know how to build a installer with download manager? So
the user would download a lightweight installer, select the components they
want to install and the installer would download the necessary components
and install them.
thanks!
--
Okay, do you have a clue on this one:
-
Does Windows 7 (without servicepack) support .NET Framework 4.5?
This page tells it does:
http://msdn.microsoft.com/en-us/library/8z6watww.aspx
This page tells it does NOT:
http://www.microsoft.com/en-us/download/details.aspx?id=30653
You could implement that in a custom BA. The wixstdba doesn't have such a
concept.
On Wed, May 8, 2013 at 1:11 AM, Sam Boman wrote:
> Is there any way to do like this when installing an application when using
> Bundle bootstrapper:
> installer.exe /skip-conditions
>
> To make the installation r
Is there any way to do like this when installing an application when using
Bundle bootstrapper:
installer.exe /skip-conditions
To make the installation run without checking the conditions (VersionNT,
ServicePackLevel).
Best regards,
Sam Boman
--
I just found a very strange thing.
Microsoft is specifying bout Windows 7 (no SP) and Windows 7 SP1:
http://www.microsoft.com/en-us/download/details.aspx?id=30653
http://msdn.microsoft.com/sv-se/library/8z6watww.aspx
So the result is that before I added the launch condition
to prevent Windows 7 wi
36 matches
Mail list logo
