Hi All,
I have created MSI/EXE using Wix based on OS (Operating System).
Used VersionNT property values for creating MSI/EXE.
Installation is not working for Windows Server 2008/Windows Server 2012.
How can I check the conditional installation for Windows Server
2008/Windows Server 2012.
Hello,
Reading the http://wixtoolset.org/documentation/manual/v3/xsd/wix/custom.html
docs. Would it be possible to specify the legal values for attribute before and
after, and inner value?
Using google I found the state 'InstallInitialize' and 'InstallFinalize' which
solved two issues.
Thanks Blair for your suggestion, I will revisit the code.
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: 26 August 2013 20:15
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] FW: Custom installation in Wix Patch
I finally got a chance to look, and it
Did you try restarting the machine so that all the background processes
that are running behind is killed.
-Original Message-
From: Shaun Greenfield [mailto:sgreenfi...@tradestation.com]
Sent: 26 August 2013 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] The Last Error
If you are intending to use the 32-bit registry in a 64-bit platform in
RegEdit, you need to start from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
(which is the 32-bit HKEY_LOCAL_MACHINE\SOFTWARE key).
You make TARGETDIR conditional by setting a property by that name to the full
path
Looks to me like a really good thing to include in WiX. Would you be willing to
contribute it?
Date: Tue, 27 Aug 2013 17:08:37 +1200
From: benjamins...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] DCOM Launch and Access permissions
Cool, thanks Phil. I was
Is there any way to modify burn to only show the Msi dialogs? I would like
to use burn to install .Net Framework but don't like the two dialogs being
shown and have tried to play around with the HyperLinkTheme.xml but cannot
figure out if it can be done so that it is silent and to fire the Msi
This is interesting to me:The last files being compared were RegistASM.exe. The
Comparing bytes message is from the comparison of the files in the Comparing
Files message just previous.
The error is being reported on TSResourceDllChs.dll. That isn't the same file.
This suggests that it was done
This has been discussed on this list. The two proposed solutions were 1)
command-line, and 2) a custom BA.
It has also been suggested on this same list that that isn't the best user
experience (think repair and removal where the MSI UI is NOT available at all
via Burn). Burn isn't intended as a
That page in the docs is part of the reference, and the reference pages assume
that you know how you wish to configure your custom action and simply give the
syntax required to express it in WiX.
The tutorial and the book are both great places to get more beginners
information on Windows
I'm not understanding your request. VersionNT is a property indicating the
platform version of windows, expressed (in the case of MSI) as an integer.
If you tell us what you are trying to do with VersionNT and what you want your
package to do between different platforms, we could help more. An
Which UI are you using in your bundle?
From: afor...@cmu.edu
To: wix-users@lists.sourceforge.net
Date: Mon, 26 Aug 2013 18:55:39 -0400
Subject: [WiX-users] Add text to final window in burn bootstrapper/installer
Hi all,
Our installer bundled with burn currently posts a simple Setup
You could try looking at the msbuild files supplied with WiX, but the go/no-go
data for linking depends on what compile did, so in reality it won't be
straightforward to determine pre-compile what the decision will be at link.
AfterCompileAndLink fires after all cultures have been linked.
Thank you for your feeback.
I forget what the DropBox install experience was, but when I look at
those shell extensions they are all in HKCU, so they are per-user and
not per-system. That might work for you too.
I run Regshot on my computer and looked at the changes in registry. A lot
of the
My understanding is that Heat should produce the same result (on a clean
machine) that regasm produces (unless the binary is 64-bit only or if it is an
EXE instead of a DLL). If the machine heat is running on already had the binary
registered then most of the time it won't work (you have to
Hi Blair,
Thank you for the information.
I am checking windows version to install the MSI/EXE file.
Ex: In my code, I have used for Windows XP 32 bit,
Condition ![CDATA[Installed OR (VersionNT = 501)]] /Condition
So, installer will installs only Windows XP 32 bit machine.
Same like, I
I have Config.ini file which is having Model Information.
If this Config.ini file is existing in Windows folder before running MSI
file, I can able to read Model information in INI file.
Is there any way to copy INI file and read that while installing MSI.
Regards,
Dileep
On Tue, Aug 27,
Good question. I'm not sure exactly, but here’s some code snippets that what
I'm guessing are UI-related:
Wix
xmlns='http://schemas.microsoft.com/wix/2006/wi'
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
http://robmensching.com/blog/posts/2008/11/3/how-to-determine-if-you-are-installing-on-windows-client
should help.
Tom Porterfield
-Original Message-
From: dileep s [mailto:dileep.sanamp...@gmail.com]
Sent: Tuesday, August 27, 2013 6:51 AM
To: General discussion for Windows Installer
This still seems to be the case in 3.7.1224.0
I'd like to be able to use MSBuild variables in the output name as
everything else works with my current project expect this. Currently I
either have to duplicate my project wixproj file and 'hard code' the name in
the UI or bypass the UI and edit the
It'd be great if you could contribute what you learned or maybe go in and
understand how the documentation is created for the WiX toolset to help
enhance it. The guys on wix-devs mailing list are very supportive of people
wanting to help improve.
Feature suggestions here are welcome but I always
I know there is probably a posting somewhere out on the web describing the
issue I am having, but I am not able to find it at the present moment.
The problem I am current having is that the 64 bit version of MS build does not
properly evaluate the build variables and is not able to find WIX
If the INI file is in your MSI, whatever is in that INI file could be added to
your MSI when your MSI is built, right? If not, please explain why not.
If the INI file is not in the MSI, how does your MSI know where the INI file is
in order to copy it to the Windows folder? Could that action in
Please file a feature request. Even better, contributing a fix would be much
appreciated.
Date: Tue, 27 Aug 2013 07:18:38 -0700
From: techsupport...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name
This still seems to
Which version of WiX are you running? There was a bug a ways back about that.
From: mathew.skil...@aspect.com
To: wix-users@lists.sourceforge.net
Date: Tue, 27 Aug 2013 14:54:30 +
Subject: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
I know there is probably a
I am using WIX 3.8 (build 3.8.708). The build system is using the GA version
of WIX 3.7.
I am havine issues on both systems.
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, August 27, 2013 10:37 AM
To: General discussion for Windows Installer XML toolset.
How far back do you wixproj files go? Modern ones should have something like:
lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND
'$(MSBuildExtensionsPath32)' != ''
gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;
lt;WixTargetsPath Condition=
All of the WIX projects in question have those lines in place:
WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND
'$(MSBuildExtensionsPath32)' != ''
$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath
WixTargetsPath Condition= '$(WixTargetsPath)' == ''
MSBuild 4.0 x64 uses the 32-bit path for both $(MSBuildExtensionsPath32) and
$(MSBuildExtensionsPath), so it should be picking up the right file.
What are the specific errors you are getting?
From: mathew.skil...@aspect.com
To: wix-users@lists.sourceforge.net
Date: Tue, 27 Aug 2013 16:38:03
Ok. So the proj files are modern. What is the path of WiX on the build server
and how was it installed there? What is the specific message from the build
logs?
--
John Merryweather Cooper
Build Install Engineer -- ESA
Jack Henry Associates, Inc.(r)
Shawnee Mission, KS 66227
Office:
WIX was installed through the released installed and the installation path is
C:\Program Files (x86)\WiX Toolset v3.7.
Here is an example of the build errors:
CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment'
does not exist in the namespace 'Microsoft' (are you
The original registry search you posted doesn't have Win64=yes so it
will be a 32-bit registry search if you have an x86 platform install (and
it looks like you do).
Phil Wilson
On Tue, Aug 27, 2013 at 2:29 AM, Blair Murri os...@live.com wrote:
If you are intending to use the 32-bit registry
You have broken references in your custom action project to
Microsoft.Deployment.WindowsInstaller.dll. It should be in C:\Program Files
(x86)\WiX Toolset v3.7\bin\.
--
John Merryweather Cooper
Build Install Engineer -- ESA
Jack Henry Associates, Inc.(r)
Shawnee Mission, KS 66227
Office:
On 8/27/13 10:05 AM, Skildum, Mathew wrote:
Here is an example of the build errors:
CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment'
does not exist in the namespace 'Microsoft' (are you missing an assembly
refere
nce?)
CustomAction.cs(12,58): error CS0246:
All hint paths are correct as everything build correctly in Visual Studio (2010
and 2012). The only time it fails is when I use the 64 bit version of MS Build.
Mat Skildum
-Original Message-
From: Edwin Castro [mailto:0ptikgh...@gmx.us]
Sent: Tuesday, August 27, 2013 12:54 PM
To:
Building correctly on VS 2010 or 2012 doesn't tell you much as both of the
those cache references.
Where is the Microsoft.Deployment.WindowsInstaller assembly on your build
server, and what does the HintPath look like on the failing custom action
project?
--
John Merryweather Cooper
Build
On 8/27/13 11:03 AM, Skildum, Mathew wrote:
All hint paths are correct as everything build correctly in Visual Studio
(2010 and 2012). The only time it fails is when I use the 64 bit version of
MS Build.
Can you provide the reference XML from the project file? I assume you
have not modified
When trying to uninstall a WiX Burn Bundle (WiX 3.6) I get these errors from
the log file:
[0F90:0F94][2013-08-27T11:55:28]: Applying execute package: AI_MsiInstaller,
action: Uninstall, path: C:\Documents and Settings\All Users\Application
Data\Package
Hello,
I am new to Wix and have a question regarding wix and reading settings from an
xml file when running the installer. I have an xml file with database
connectionstrings that are different for my test and production environment:
The Microsoft.Deployment.WindowsInstaller assembly is located in the default
installation location. No customization has been done to the system or the
projects.
Here is the project file section that lists the above assembly refference:
ItemGroup
Reference Include=System /
Reference
That doesn't look right. Bearing in mind that we're still using WiX 3.6 RTM,
my HintPath looks like:
lt;Reference Include=Microsoft.Deployment.WindowsInstaller, Version=3.0.0.0,
Culture=neutral, PublicKeyToken=ce35f76fcda82bad,
processorArchitecture=MSILgt;
MSBuild uses the AssemblySearchPaths property to determine the locations
where it searches for assembly references. See
http://msdn.microsoft.com/en-us/library/vstudio/bb629394.aspx
You could either set the HintPath for the reference OR you could add the
location of
You would need an immediate custom action to read the .config file, find
the appropriate connection string, and set its value to a property.
CustomAction Id=MyAction
ExeCommand=cmd.exe /C MyDatabaseInstaller [CONNSTR]
Execute=deferred
Return=check /
If
I think you can test for
Command.Resume == ResumeType.RebootPending
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Pending-Reboot-tp7588050p7588495.html
Sent from the wix-users mailing list archive at Nabble.com.
That error is Another installation is already in progress. Complete that
installation before proceeding with this install. .
Does that make sense?
Phil Wilson
On Tue, Aug 27, 2013 at 11:13 AM, thejohno jherm...@ualberta.ca wrote:
When trying to uninstall a WiX Burn Bundle (WiX 3.6) I get
Yes I think that was it. Thanks Phil.
*John Hermary *
*Software Developer
Green's Publishing*
Phone: +1 (780) 484-5550
Toll Free: +1 (866) 463-6968
jherm...@ualberta.ca
WordMemoryTest.com http://www.wordmemorytest.com
**
On Tue, Aug 27, 2013 at 3:13 PM, Phil Wilson phildgwil...@gmail.com
I've noticed that in the RtfTheme-Custom.xml, there is this which I'm guessing
represents the Setup Successful page:
Page Name=Success
Text X=11 Y=80 Width=-11 Height=30 FontId=2
DisablePrefix=yes#(loc.SuccessHeader)/Text
Button Name=LaunchButton X=-91 Y=-11 Width=75 Height=23
Mark Sanchez
Systems Developer
SPEC Services, Inc.
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your
No.
Go here to unsubscribe yourself:
https://lists.sourceforge.net/lists/listinfo/wix-users
-Original Message-
From: msanc...@specservices.com [mailto:msanc...@specservices.com]
Sent: Tuesday, August 27, 2013 18:26
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] UNSUBSCRIBE
My company is blocking that site.
I didn't really need to unsubscribe but it seems as though I get an email for
every entry added there. It's as though I have been registered on a thread to
receive replies, which I have never even posted anything. How can this be
turned off?
Mark Sanchez
Your company blocks sourceforge.net? Huh.
There, I've just unsubscribed you. You should receive a confirmation e-mail
probably asking you to click a link to confirm that hopefully your company
doesn't block. If your company does block it, well then unless you can make a
rule to route WiX-users
There's an issue open requesting WiX to write the AssemblySearchPaths in
64-bit hive. That isn't done today.
On Tue, Aug 27, 2013 at 12:27 PM, Edwin Castro 0ptikgh...@gmx.us wrote:
MSBuild uses the AssemblySearchPaths property to determine the locations
where it searches for assembly
As I understand it, page Success will be shown whenever the result of bundle
application is successful but not when a failure occurs (when instead the
Failure page will be shown). So, successful install, successful removal,
successful modification, etc.
If you can set bundle properties you can
53 matches
Mail list logo
