I created a executable of my msi using setupbld.exe and setup.exe stub tool
of wix 3.0.
I installed the executable created, everything worked fine.
but when i double click the exe again (after the installation)it shows me
resume dialogbox with 'back' button(disabled), install button, cancel
butto
Hello,
I am getting errors when building the same wix scripts for 64
bit which builds fine for 32 bit:
D:\src\clean\out\ABC\Winx64\delivery\install\ECCE\BCEV.msi : error SMOK0204
: ICE80: This 32BitComponent RegistryValues uses 64BitDirectory INSTALLDIR
D:\src\clean\out\ABC\Winx64\delivery\instal
Hi,
I have to check for the presence of a product. If the product is absent I need
to use a warning msg and then continue the installation without exiting.
what I have done is using upgrade code I'm detecting if the product is present
and am setting a property based on that. later I show a dial
Hi Ahmad,
You are using a folder that's for 64 bits files and are installing files that
are marked as 32 bits. You can fix this by either using a 32 bits folder, or
change the component to 64 bits.
Cheers,
Jeffrey Bindinga
Software Developer at CyberTech International
-Original Message--
Hi Bijay,
You can use the SpawnDialog event to show a modal dialog, add a condition to
this action to show it conditionally. In the warning dialog you can add the
EndDialog event to the ok button to close the dialog.
Regards,
Jeffrey Bindinga
Software Developer at CyberTech International.
You're trying to put Components marked as 32-bit into 64-bit only
locations.
For "RegistryValues" and "EulaPdf" I'm guessing all you need to do is
remove the Win64="no" attribute.
For the Visual C++ 8.0 Merge Modules, simply put them under TARGETDIR
(see -> http://wix.sourceforge.net/manual-wix3/i
Hi there,
I'm getting started with WiX and I want to create just some simple icons on the
desktop and the startmenu but I'm getting:
Error 1 Unresolved reference to symbol 'Directory:ProgramMenuDir' in section
'Product:{21303116-42B5-4428-9ED1-A20CDBDE2168}'.
Error 2 Unresolved reference to s
Hello,
Error 1: You mention "" where
PFiles is the name of the link to the programfiles folder, further, you mention
"Directory=ProgramMenuDir". Replace the last with the first and you're done.
Error 2: You have to include a reference to the icon itself (it is not native).
Add this statement a
Setup.exe is running your MSI with some parameters which double clicking
the MSI itself isn't (sounds like it's trying to do either Repair or
Reinstall by default). Find out what they are & then find out how to
remove them.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 9
Error 1 - Author a ProgramMenuDir. You can't link to something which
doesn't exist. See ->
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm
Error 2 - Author an Icon Element. You can't link to something which
doesn't exist. See ->
http://wix.sourceforge.net/manual-wix3/wix_xsd_i
Hi,
WixUI_FeatureTree is almost exactly what I need. I just want to change 2
things:
1) Add a Readme.rtf file at the end of the install. This can either be
in a dialog similar to EULA (that's what Visual Studio setup projects
do), or a checkbox to execute the RTF when the installer closes. Give
1 -
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
However from looking at the sources WiXUI_FeatureTree already has
LicenseAgreementDlg after the WelcomeDlg. If you want a second one
showing a different RTF you'll need to write it (or copy & paste from
the LicenseAgreement
Personally we're using VMWare ESXi 4.0 for my QA teams & my own testing
purposes. It really is pretty damn good. Hyper-V Server is Microsoft's
response to VMWare making ESXi free. Any machine you can run Hyper-V
Server on you can run ESXi on & from my experience it's a much better
choice overall.
>> 2) Currently when I upgrade from one version to the next I get a popup
>> from the Restart Manager asking to restart the programs that use my DLL.
>> That's good. But during uninstall I only get a simple message box saying
>> "Some files are in use, you should reboot afterwards". I want to use t
Not if you use the Windows Installer integration with ARP. You would have to
use the "Legacy" ARP interface, which requires using the ARPSYSTEMCOMPONENT
property AND programming the uninstall registry key yourself. This has been
discussed on this list before.
However, I don't believe that is what
The ARPSYSTEMCOMPONENT route seems treacherous. Can't I just modify the
summary information on the cached msi in c:\windows\installer? The code
signing signature doesn't work from add/remove programs anyway, due to MSKB
929467. The trick here would be to find out when the cached msi is writte
> "Basic UI or Reduced UI level installations give the user the option of
> using the Restart Manager to reduce system restarts even if the
> MsiRMFilesInUse dialog box is not present. Silent UI level installations
> always shut down applications and services, and on Windows Vista, always use
> Re
Hi ALL,
I wrote a custom action to create a scheduled task after install.
I do not want the Custom Action to run when the user does not want to create
the schedule task. During installation even if I select " Feature will be
unAvailable" the schtask is getting created. How do i prevent the Custom
Hi Pally,
I wrote a custom action to create a scheduled task after
install.
I do not want the Custom Action to run when the user does not want to create
the schedule task. During installation even if I select " Feature will be
unAvailable" the schtask is getting creat
You can condition your custom actions based on the action-state of your
feature, like so.
&SWUSchedTaskFeature=3
&SWUSchedTaskFeature=2
More info...
http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx
--
View this message in context:
http://windows-installer-xml-w
With CloseApplication you can shutdown any arbitrary application (not just ones
you are installing) but you have to determine which ones some other way.
I just did a quick scan of the custom action code associated with
CloseApplication and it doesn't currently tie into MSIs integration with
Res
Code signing works putting the program in in the first place.
Yes, you could alter the MSI directly using the Summary Info APIs. That
should work.
-Original Message-
From: Matt Johnson [mailto:ma...@timeamerica.com]
Sent: Monday, June 21, 2010 12:22 PM
To: General discussion for Windows
> If you have some budget, I can be hired to provide a CA that performs that
> task for you. It would be up to you if you wished that to be contributed back
> to the community or to have it licensed to you. Email me directly if you are
> interested.
Sorry, no budget here :) This is an open sour
Since we're at this topic (and forgive me for shameless advertising) we use
http://remoteinstall.codeplex.com to drive installer test automation with
VMWare. The largest test bed runs 130+ install/upgrade scenarios every day -
all we do is throw more hardware for more snapshots at the problem as
I just tried some manual testing before writing a full-blown CA. It seems
changing the summary info on the cached msi does nothing. I can see the change
when I examine the msi in Orca, but it does not change the product name in
add/remove programs.
I found something else that seems more promi
Now, the configurations are working.
Thanks!
Carolina Zuqueto.
-Original Message-
From: Alexander Shevchuk (Volt) [mailto:a-ale...@microsoft.com]
Sent: quinta-feira, 17 de junho de 2010 20:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile
Add
> Hmm... I see a problem. I don't want my bootstrapper to run as admin, so it
> won't have access to the protected areas like Program Files. The reason I
> don't want to run as admin is because then it won't be able to launch stuff on
> behalf of the logged in user (which may be different from the
"Castro wrote:
> > Hmm... I see a problem. I don't want my bootstrapper to run as admin, so it
> > won't have access to the protected areas like Program Files. The reason I
> > don't want to run as admin is because then it won't be able to launch stuff
> > on
> > behalf of the logged in use
I feel silly...
None of this was necessary. Turns out that setting the ProductName property
already takes care of updating the name in ARP. HOWEVER - you have to set it
in the InstallExecuteSequence. I was just setting it in the UI phase.
Thanks anyway! It was a fun exercise... lol.
Matt
Yes. However, if the bootsrapper (A) runs silently any prerequisite
installations that are not launched with ShellExecute or that are
incorrectly manifested for elevation or that are MSI they may fail if as a
result the UAC prompt for them never appears.
I don't know enough about the bootstrapper
On 6/20/2010 4:04 PM, Sajo Jacob wrote:
> Can someone please guide us from a WiX perspective how this can
> be done?
>
Not supported.
--
sig://boB
http://joyofsetup.com/
--
ThinkGeek and WIRED's GeekDad team up for
On 6/19/2010 4:06 AM, Stefan Kuhr wrote:
> is it possible to use the DefaultVersion attribute for unversioned files?
No. DefaultVersion just sets the File.Version column. See the MSI SDK
doc for the File table for limitations.
--
sig://boB
http://joyofsetup.com/
--
On 6/21/2010 5:49 PM, Matt Johnson wrote:
> Is this a safe approach?
No. It's undocumented internal MSI data. Every time somebody mucks with
it, there's one more reason the MSI team has to waste time supporting
broken apps instead of moving the platform forward.
--
sig://boB
http://joyofsetup.
On 6/21/2010 5:36 AM, Bijay Agarwal wrote:
> I have to check for the presence of a product. If the product is absent I
> need to use a warning msg and then continue the installation without exiting.
>
Check the WiX setup source code; it has a warning dialog like you're
describing.
--
sig:/
Blair wrote:
> Yes. However, if the bootsrapper (A) runs silently any prerequisite
> installations that are not launched with ShellExecute or that are
> incorrectly manifested for elevation or that are MSI they may fail if as a
> result the UAC prompt for them never appears.
Yeah, I see no
>> 1) Add a Readme.rtf file at the end of the install. This can either be
>> in a dialog similar to EULA (that's what Visual Studio setup projects
>> do), or a checkbox to execute the RTF when the installer closes. Given
>> the choice between the two I would prefer the first option (embed the
>> Re
You set your ReadmeDlg the way that ExitDialog is currently invoked, then
have ReadmeDlg's Next button go to ExitDialog. You can then enable/add back
in ExitDialog's Back button and set it to return to ReadmeDlg.
-Original Message-
From: i...@roadrunner.com [mailto:i...@roadrunner.com]
Se
Two problems with that:
- the ExitDialog is part of the UI_FeatureTree set, so I can't change it from
my project alone. I'll have to either modify the UI_FeatureTree set and rebuild
WiX, or copy the whole set into my project and modify the copy
- after looking at the source for ExitDialog I'm sti
I'm using WiX 3.0.5419.0.
I have a WixLib with a handful of shared infrastructure for our installers.
Because this WixLib is shared among a number of projects I need to build the
WixLib separately. One of the pieces of infrastructure is a nearly complete
Product section. Mostly it is missing a
My installer must be run on Windows7 and Windows 2008 (and r2). One of the
prerequisite is service MSMQ, which must be installed on this computer. But
how to check it? On windows XP and Windows 2003 I checked registry value
"HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OC
Manager\Subcompone
it might be. I'll try it both ways.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, June 18, 2010 4:46 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Password showing in text when installing custom user
for AppPool
It doesn't
> I'm talking about the bootstrapper, not the installer. Correct me if I'm
> wrong:
> If the bootstrapper A runs as admin, then the installer B (as a child process)
> will run as admin.
> If the installer B runs as admin, then it won't be able to launch my
> application C as non-admin.
> So I want
42 matches
Mail list logo
