[WiX-users] Writing a C++ Custom Action Project

I have written a C# Custom Action that is supposed to get the Values of Properties passed to the installer and create some config file. Since the C# Custom action was done, my installer depends upon .Net too. I want to avoid this dependency, thus I am opting to write the Custom action in C++.

Re: [WiX-users] Writing a C++ Custom Action Project

Your checks for an empty string are wrong - constructs like ip == L need to be *ip == 0 or similar. Check the documentation for the sprintf() implementation you're using. In Standard C %s is for a normal character string but you're using it for wide character strings - that would

Re: [WiX-users] Writing a C++ Custom Action Project

Hi Stephan, Thanks for your response. I have added the local variable above WcaInitialize. On Fri, Mar 13, 2015 at 11:30 PM, Tunney, Stephen stephen.tun...@nuance.com wrote: A general rule with C++ CAs that I follow: Put ALL of your local/stack variables above the WcaInitialize call. I run

Re: [WiX-users] Writing a C++ Custom Action Project

A general rule with C++ CAs that I follow: Put ALL of your local/stack variables above the WcaInitialize call. I run into weird behaviour (crashes, access violations, etc.) if I don't. This is true when running in VS2010 and VS2013 compilers. -Original Message- From: Sarvagya Pant

Re: [WiX-users] Replace files added in minor upgrade

Baseline is ver 1 yes. Also all patches 1.1, 1.2 and 1.3 are incremental patches of 1. So 1.1 is 1-1.1 1.2 is 1-1.2 1.3 is 1-1.3. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Replace-files-added-in-minor-upgrade-tp7599551p7599559.html Sent from

Re: [WiX-users] Writing a C++ Custom Action Project

In C++ to test the C# equivalent of string.IsNullOrEmpty() you should do: if(( p == NULL) || (*p == NULL)) To sprintf a wide string you should use %ls Note that creating a file during an immediate custom action is against Windows Installer methodology. The correct way should consist of 3 custom

[WiX-users] heat fragments go one directory too low

Hi, I'm harvesting (WiX3.8) a whole lot of dynamically generated documentation files, which are in a subdirectory NEWDOCS. I'm using the following command-line: heat dir ./newdoCs -gg -template fragment -out ./docs.wxs -sfrag -suid -cg HelpFiles -var wix.MySource -dr DOCFOLDER -directoryid

Re: [WiX-users] ConfirmCancelMessage can not localized

Searching the Wix source, “ConfirmCancelMessage” is localized into 23 locals in folders under: path to extracted wix source\src\ext\BalExtension\wixstdba\Resources String Id=ConfirmCancelMessage您確定要取消嗎?/String Is there another issue, or is your desired local not included? -- View this message

Re: [WiX-users] Implementing Microsoft Fixit - is Wix the right tool?

I certainly think that WiX is the way to go. WiX bundle.exe with a custom BA (or WixStdBA and possibly a bafuntions.dll) and external packages staged for web deployment, is a very flexible framework. A wix bundle can be an 'addon', 'upgrade', or 'patch' to an installed wix bundle (and the

Re: [WiX-users] After add reference WixNetFxExtension.dll to Setup Project, build failed‏

Are you sure that you want to use Wix 4.0? It is going through some development changes, which may be breaking, but which should be great additions in the future. Wix 3.9 is stable (and wix 3.10 has been reliable for me). -- View this message in context:

[WiX-users] Bundle upgrade removes msi package

Hi, I have a bundle setup containing two msi packages. I have problems with upgrades sometimes. One of the msi packages gets uninstalled during upgrade. My theory right now is that the msi version numbers are compared alphanumeric. Can anyone confirm this? Is this intended behavior or a bug?

[WiX-users] Replace files added in minor upgrade

I added a new component to existing product using a minor upgrade. But when in next minor upgrade I try to update this files the update fails. I get the following message in upgrade installation logs :- Component 'component Name' is added in both the superseded patch and superseding patch. No

Re: [WiX-users] Replace files added in minor upgrade

My question would be what is your baseline? If ver 1 is your RTM release, all patches should be based off of it for easy cumulative patching. If you are doing incremental patching, then 1.2 would require 1.1, and wouldn't supersede it. Note: My experience with patching is limited, but this

Re: [WiX-users] Error 1920. Service 'SomeService' failed to start

I’ve had success tracking down 1920 service-start errors by opening the exe in the dependency walker right after the error message is thrown (http://www.dependencywalker.com/). It’s not a perfectly reliable tool, but it will let you know if your binary is missing any static dependencies that

Re: [WiX-users] After add reference WixNetFxExtension.dll to Setup Project, build failed‏

Yes I already in use Wix 4.0 and actually I try to downgrade to Wix 3.9, but I failed, main problem is In Wix 3.9 you can not put a directory property to a component if component already in component group. that's important for me. Hopeful Wix 4.0 come to stable soon. thank you. Date: Fri, 13