Thank you Thomas for sharing your thought.
I agree with you to separate the database deployment with the client
application installation.
In my situation however, we plan to put database deployment together with the
server-side deployment. The client-side application deployment doesn't perform
STILL bad.
Any idea how complicatd it can be in companies to get admin rights on sql
server for installing a server application? It can be living hell.
At least allow using an EXISTING empty database - so the dba's can set up the
database, then you use the given username and password to
I have two SELMGR entries, both for FEAT_Main, none for FEAT_NewSql, so I
assume they are for the two files updated in the MSP.
This is true regardless of wether I run with REINSTALL=ALL or have the SQL
component referenced in the patchfamily.
However, looking through the verbose log, I found
I have a working wix install. The application has a number of localization
folders of the form .\en-US, .\it-it etc
Each with a couple of files.
Is it possible to create a Wix install that automatically includes all the
localization folders and files?
In other words if I add a new local, Wix will
Hi everyone,
We have a shared library for all our products we include during compilation.
Now I would like to stop and start IIS during installation because running
iis applications can get in the way of updates. This is very easily done
with the fragment below.
Fragment
Component
Yes, the component will be reference counted. The component rules allow the
same component to be installed to several directories simultaneously. The
service control is performed only when installing or removing the component
so it won't behave as you require.
I've never used them myself but
How about a ComponentSearch instead of a FileSearch?
On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze coolbreeze...@googlemail.comwrote:
Thanks for the reply Chad. I've tried increasing the Depth to say 4 as well
as providing and absolute path to the assembly and when I compile, I get
the
I have a wxs here that has a Property / DirectorySearch / FileSearch nesting
where I'm using Directory@Path=[%WINDIR]\assembly Depth=3 and doing a
search
for an assembly name with a specific Min Version. We used this to detect
that a product we integrate with has it's .NET interop libraries
You could dynamically generate the group of files to be included. This is how I
do it.
C:\Program Files (x86)\Windows Installer XML v3\bin\heat dir
l:\bin\templates -var var.binDir -indent 2 -gg -g1 -scom -sreg -sfrag -dr bin
-cg bin -o $(ProjectDir)bin.wxs
Michael
Ext 243
-Original
Thanks for the suggestion Rob. The only problem is that this is a older
version of CSLA we use 3.6.2 and on Rockford's website he no longer provides
an installer. This should not be much of a road block, because you can get
the source and within the Setup Project find the GUID. I've done this and
Yes I do. Following is the function call to get the data from session.
public static string[] GetCustomActionDataArguments(Session session)
{
string[] keys = new string[session.CustomActionData.Keys.Count];
session.CustomActionData.Keys.CopyTo(keys, 0);
That will only work for a deferred custom action because MSI maps the property
with the name of the CA to a property called CustomActionData which is what
that
implementations constructor uses to populate the dictionary. You need to look
at the CustomActionData constructors and methods (
CustomActionData customActionData = new CustomActionData( session[PROPERTY] );
Also if one custom action is in the UI and one is in the Execute sequence, make
sure you mark PROPERTY as a SecureCustomProperty other wise it won't pass from
one process to the other in an elevated / managed
I have WiX integrated with Visual Studio so the installer is built when the
solution is built. Right now I consistently run into the error from light:
Error 1 Exception of type 'System.OutOfMemoryException' was
thrown.light.exe 0 1
Thanks Chris.
can you give me an example of how to work with SecureCustomProperty, please?
thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Passing-values-to-CA-not-working-tp6216967p6220094.html
Sent from the wix-users mailing list archive
Windows Installer has a property called SecureCustomProperties which is just a
;
delimited list of property names. In WiX, the Property element has an attribute
called Secure which is tells the compiler to put the property in the
SecureCustomPropertiesProperty.
Thanks Chris, its working now. But following code to check a property value
is not working
My CA is setting the value of a property SOLUTIONEXISTS and its setting is
correctly based on conditions.
But in my wix code, my condition element is not working as expected.
Following message is displayed
Try BootstrapperItems=@(BootstrapperFile) instead of
BootstrapperItems=$(BootstrapperFile) in project file:
GenerateBootstrapper ApplicationFile=$(TargetFileName)
ApplicationName=Network Configurator
BootstrapperItems=@(BootstrapperFile) ComponentsLocation=Relative
CopyComponents=True
Thanks for everyone's help. I still haven't resolved why this is not working
for me after trying numerous suggestions, but the more I work with Wix the
more I learn.
Thanks again everyone.
On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze coolbreeze...@googlemail.comwrote:
Thanks for the suggestion
19 matches
Mail list logo
