Sorry, for the short response. I have done it by setting conditions. x86 vs
x64.Per Rob's blog, check this out
http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/block_install_on_os.html
and (it is also linked) http://msdn.microsoft.com/library/aa370556.aspx
I
Defer it?
On Wed, Jan 7, 2015 at 8:49 PM, wixtester wrote:
>
> The CustomAction does not permit "Win64" attribute for a managed custom
> action
>
> BinaryKey='provisionCA' DllEntry='SearchJRE' Execute="immediate"
> Return="check" Win64="yes"/>
>
>
> Error message
>
> error
The CustomAction does not permit "Win64" attribute for a managed custom
action
Error message
error CNDL0037: The CustomAction/@Win64 attribute can only be specified
with one of the following attributes:Script, VBScriptCall, or JScriptCall
present.
Note: I am using mana
I think this is what you may be looking for.
http://stackoverflow.com/questions/1601186/sql-server-script-to-create-a-new-user
I don't think you want to use ContinueOnError="yes". That way you may be
able to see what is wrong if you use verbose logging and it might help.
J
On Wed, Jan 7, 2015 a
Oh and if SQL is clustered or has a named instance don't use "."
J
On Wed, Jan 7, 2015 at 2:23 AM, patrickpirzer
wrote:
> I have programmed a bootstrapper-project with WiX 3.8.
> While the installation i want to create a sql server login with
> sql-authentication.
> So i embedded in the Product
See the CustomAction/@Win64 attribute.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: wixtester [mailto:sangee...@hotmail.com]
Sent: Wednesday, January 7, 2015 1
Hi,
I have a managed custom action to read the registry. I want it to read
the 64-bit registry on a 64-bit Windows and 32-bit registry on x86 Windows.
When I build the custom action for AnyCPU, I expect it to work.
But when I run the msi (that invokes this custom action) on Win 2008 R2
which
http://wixtoolset.org/issues/
click 'New Issue'
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-WACK-unresolvable-warnings-tp7590378p7598753.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Can you send some screenshots of your MSI’s InstallUISequence and
InstallExecuteSequence and/or the declaration of your FixNetFramework45 custom
action.
> On Jan 6, 2015, at 6:02 AM, Yankulin, Leonid
> wrote:
>
> Hello,
> I have defined a custom action to be executed *BEFORE* the LaunchCondit
Where should I create the bug?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-WACK-unresolvable-warnings-tp7590378p7598751.html
Sent from the wix-users mailing list archive at Nabble.com.
-
I don't have very many ideas for you. I think some deeper debugging is
needed to sort the issues out. Are the computers where 'all is well' also
running German (or the culture where the failure is observed)? Are you
dealing with the fact that the built-in domain names for accounts are
localized
?Hi all,
Is there any way in wix to add password protection for the uninstall of a
software?
Thank you
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partn
Sorry Phill, i have made a copy-paste-error.
Of course i defined the bundle-variable like that (type=string):
And in my ViewModel i set the variable in the PropertySetter:
public string DbUser
{
get
{
return _dbUser;
}
Hello,
I declare a property in a merge module and mark it as Secure. However, when
the final MSI is built , i observe that the property is not appended to the
SecureCustomProperties in the Property table.
As per the following pages:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
I have programmed a bootstrapper-project with WiX 3.8.
While the installation i want to create a sql server login with
sql-authentication.
So i embedded in the Product.wxs of my MSI-Project the following component.
But when i take a loo
15 matches
Mail list logo
