Thanks for the verification of the current behavior.
I have added a feature request:
http://sourceforge.net/p/wix/feature-requests/725/
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Version-and-patching-tp7579655p7584964.html
Sent from
hey all
When you include a Msipackage in boostrapper you can specify cache and
cacheid. The documenation is sparse on what these attribtues do ? What is
the recommended value for these attributes ?
Thanks
Raj
--
Hello,
I have to fix a bug in a wix project but i don't know much about that
technology and there is no one to help me anymore in my team.
Here is the bug :
The asp.net framework in my default web site in iis is defined at 1.1.
When I'm creating a new virtual directory, I need it to be in 2.0
Ok I am not sure what I am doing wrong but following the guide and it
still will not create the keys, what am I doing wrong:
RegistryKey Root=HKLM
Key=SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\FIMAutomation
Action=create
RegistryValue Type=string
I have a WiX 3.6 install using burn to chain 5 packages plus a
pre-requisite of .net 4 which uses the short but sweet smile
PackageGroupRef Id=NetFx40Web/ reference. It's working pretty nicely,
but there is one area which needs tidying up.
Three of my packages (which are installed into their own
In my investigation I have found that if you have seldom changing
thirdparty components... give them their own msi's and tie down there
version/product code. The boostrapper that the thirdparty msi of the
required version is already installed and doesn't seem to download or
install it.
-Raj
If this is a 32-bit component then it will go in WoW6432Node in the registry
on a 64-bit machine, and you may not be looking there.
Phil W
-Original Message-
From: David Steadman [mailto:steadm...@gmail.com]
Sent: Monday, April 08, 2013 6:51 AM
To: General discussion for Windows
Hi All,
I am fairly new to Wix, and I am running into a strange issue that I can't seem
to figure out. I have a simple bootsrapper application that works fine until I
add a resource dictionary to the wpf component. These resource dictionaries
work fine on a normal wpf application, however
I don't do much with managed BA's, but there is a difference between a standard
WPF Exe project and a BA which is a DLL. You might want to have a look at the
Wix BA (src\Setup\WixBA) to see if there is an example to go by there.
-Original Message-
From: Nick Miller
Hi,
I have a Wix file where I'm using the SqlDatabase element to create a
database. I've omitted the User attribute, because I want it to use Windows
Authentication of the currently logged in user (as per the documentation).
The User attribute references credentials specified in a User
Hi,
I have a Wix file where I'm using the SqlDatabase element to create a
database. I've omitted the User attribute, because I want it to use Windows
Authentication of the currently logged in user (as per the documentation).
The User attribute references credentials specified in a User
How do you refere to the resource dictionary, perhaps do you have copied it to
the output folder?If you don't add any other item to the bundle paylod you have
only the WixBA.dll in the temp folder where it's a started, so you need to have
all the resources embedded on the dll.If you can, you
I had the same issue. The cause seem to be that for a regular WPF
application there is always an Application.Current
The boostrapper kinda fakes it so there is no application.Current and as a
consequence you cannot have any application level resources for a managed
boostrapper. What I ended up
Just a wild guess but is it possible that custom action is not being run as
user who is doing an install.
On Mon, Apr 8, 2013 at 12:01 PM, Miller, Nick (GE Intelligent Platforms)
nick.mil...@ge.com wrote:
Hi,
I have a Wix file where I'm using the SqlDatabase element to create a
database.
Recommended to leave them blank and let the toolset pick them for you.
On Mon, Apr 8, 2013 at 6:17 AM, ptr ptrajku...@gmail.com wrote:
hey all
When you include a Msipackage in boostrapper you can specify cache and
cacheid. The documenation is sparse on what these attribtues do ? What is
OK, but if I want to assign to a burn variable, the value of one of the builtin
variable in the Burn bootstrapper which is the right way for doing it?For
example to assign the value of [DesktopFolder] ?
From: r...@robmensching.com
Date: Sun, 7 Apr 2013 20:01:31 -0700
To:
Putting it in square brackets as you have. Don't be surprised if the log does
show the value, e.g. [05C8:130C][2013-04-07T13:34:17]i000: Initializing string
variable 'InstallFolderVariable' to value '[DesktopFolder]' when the install
phase runs the correct value will be inserted.
Neil
Thanks Rob, But what does these variables do ?
thanks
Raj
On Mon, Apr 8, 2013 at 1:28 PM, Rob Mensching r...@robmensching.com wrote:
Recommended to leave them blank and let the toolset pick them for you.
On Mon, Apr 8, 2013 at 6:17 AM, ptr ptrajku...@gmail.com wrote:
hey all
When
Cache indicates whether to cache the package or not (in the Package Cache).
CacheId is an implementation detail that really should be hidden. It
controls some of the internal of how the PackageCache works. It was exposed
early and someone took a dependency on it and we haven't worked out
Thanks for the reply. This looks like what I currently have but it still
doesn't work. Currently there is only one window in the installer. Am I
missing something?
Window x:Class=TestInstaller.Views.InstallView
xmlns=http://schemas.microsoft.com/winfx/2006/xaml/presentation;
Did you add the extra files as Payload elements under the
BootstrapperApplication element? If not, they are certainly missing from
where your BA is being run.
On Mon, Apr 8, 2013 at 12:51 PM, Nick Miller nmil...@livetechnology.comwrote:
Thanks for the reply. This looks like what I currently
I need to have the value resolved in the plan phase as I have to report it on
the Managed custom UI, to report it to the user and let the user change it. But
in this case the variable is not resolved but is written exacly as I wrote it
as [DesktopFolder] and not with the path
If you want the value of a Variable formatted call the Engine
FormatString() method. This is very similar to MSI API to format a property.
On Mon, Apr 8, 2013 at 1:26 PM, Marco Tognacci mark...@live.it wrote:
I need to have the value resolved in the plan phase as I have to report it
on the
I think if you call Bootstrapper.Engine.FormatString() it seems to evaluate
the variable
So if you have something like
Variable Name='MyInstallFolder'
Type='string'
Persisted='yes'
Value='[ProgramFiles6432Folder]Company\$(var.Current.ProductShortName)' /
and you pass
FWIW, I figured out my problem. I was actually trying to use the technique for
using SQL or Windows authentication found here.
http://stackoverflow.com/questions/14480837/wix-database-deployment-installation
However, the property I was using in my conditional was being set too late, so
it was
There are two resource files, and the ButtonStyles RD depends on the Resources
RD. I've added the payload entries as follows:
Payload SourceFile=c:\path\to\file\ButonStyles.xaml /
Payload SourceFile=c:\path\to\file\Resources.xaml /
BA still crashes on open...
-Original Message-
From:
Hi Nick,
Just a note, I used that same method for an installation project I worked on.
I discovered that if the user running your install does not have
Microsoft.SqlServer.Management.Smo and its dependencies in their GAC your
installer will crash. You may be better off with using
Are those files supposed to be in the same directory as the .dll or in
subdirectories like: Views\Style? If the latter, try adding a
Payload/@Name attribute that adds the relative path to the name of the
files.
On Mon, Apr 8, 2013 at 1:42 PM, Nick Miller nmil...@livetechnology.comwrote:
There
If I understand your problem correctly this has nothing to external
payload. The XAML files are usually embedded within managed assembly. If
you are using mutliple resource files you have to use the MergeDictionaries
construct http://msdn.microsoft.com/en-us/library/aa350178.aspx
Page.Resources
Yes, this is what I need, Thanks.
From: r...@robmensching.com
Date: Mon, 8 Apr 2013 13:39:48 -0700
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn 3.7.1224.0 Builtin Variable not working
If you want the value of a Variable formatted call the Engine
FormatString() method.
Would it be like this?
Payload
Name=ButtonStyles.xaml
SourceFile= c:\path\to\project\Views\Style\ButtonStyles.xaml /
Payload
Name=Resources.xaml
SourceFile= c:\path\to\project
\LiveServer_Installer_2.0\Views\Style\Resources.xaml /
Also, is there any way to
I am currently using the MergedDictionaries construct:
Window.Resources
ResourceDictionary
ResourceDictionary.MergedDictionaries
ResourceDictionary
Source=pack://application:,,,/Views/Style/ButtonStyles.xaml/
ResourceDictionary
Question,
In your build output folder (Debug or Release), do you have a Views/Styles
sub folder? If so, they are external and need to be referenced by a Payload
with a Payload SourceFile=c:\path\to\file\ButonStyles.xaml
Name=Views\Styles\ButtonStyles.xaml /
If there isn't a subfolder,
Hey Nick
I just looked at my boostrapper and it also needed a
Application.ResourceAssembly = typeof(MainWindow).Assembly;
Can you add it to your BS and see if it helps
Raj
On Mon, Apr 8, 2013 at 3:08 PM, Nick Miller nmil...@livetechnology.comwrote:
I am currently using the
With FormatString I can evaluate the variable but for using this value as
msiproperty to pass as installation path to the msi in the burn chain I have to
write back the value in the original variable using c# code.But is there any
way for doing this in the bundle code? Something like a
Raj, you're a genius, that worked! Thank you very much!
-Original Message-
From: ptr [mailto:ptrajku...@gmail.com]
Sent: Monday, April 08, 2013 5:40 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual Styles in Wix BA
Hey Nick
I just looked
I have my MsiPackage as
MsiPackage
SourceFile=$(var.Anark.MsiOutputFolder)\FLS$(var.Platform).msi
Id=CoreFloatingLicenseServerPackageId$(var.Platform)
Cache=yes
Visible=no
Vital=yes
MsiProperty
Hi there, I understand from Rob's blog entries that it is recommended to have a
single file per component. And if this recommendation was followed I wouldn't
be in the situation I am in. Also, having a file with the version number in
the filename as keypath (and is bound to change for the
Hi,
It appears that the issue still exists in the 408 build.
I've tried installing and doing a /layout, the log for the latter is below.
Cheers
Sean.
[159C:161C][2013-04-09T06:21:21]i001: Burn v3.8.408.0, Windows v6.1 (Build
7601: Service Pack 1), path: C:\work\wix toolset\wix38.exe, cmdline:
39 matches
Mail list logo
