[WiX-users] Disable Features in Feature tree

Hi All, I have server, client and developers based installation and also have different features under each installation server, client and developers. I have screen before to customize dialog where user can select installation type from server, client or developers.

[WiX-users] Environment Variable disappears after installing a Patch

Hello, I created a patch with pyro. After installing the patch the environment variables disappear. I defined those variables like this: Environment Id=EnvUnitType Name=UnitType Action=set System=yes Value=[UNITTYPENAME] Permanent=yes / I wonder why it disappears since I set the

[WiX-users] (no subject)

-- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list

Re: [WiX-users] Reg: Uninstall Other Packages using WIX

Add additional Upgrade / elements referencing the old upgrade codes. Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com mailto:n...@x2systems.com From: Natarajan, Thangaraj (MLITS) [mailto:thangaraj_natara...@ml.com] Sent: Mon 19/01/2009 07:21 To:

[WiX-users] clickThrough in production software

Helloo What is the status of Clickthrough as of now? Can we use it in production softwares?? - Andy MSI Developer Schneider Electric:working: -- View this message in context: http://n2.nabble.com/clickThrough-in-production-software-tp2181242p2181242.html Sent from the wix-users mailing

[WiX-users] (no subject)

I'm trying to ship sql express with my setup but it always wants to download the package instead. The options ComponentsLocation=Realtive and CopyComponents=True should do the trick but sqlepr32.exe isn't being copied anywhere. I'm using the latest wix 3 build and studio 2005. Below is my

[WiX-users] CustomAction accessing CustomTable

Hello all, I am writing my first complex setup using wix and managed custom actions using c#. During the setup the user enters some settings. I have created an immediate customaction which saves those settings as rows in a CustomTable when the user clicks next. When I debug this customaction it

[WiX-users] issue with Cancelling installation when custom action is running.

Hi, any help on this is appriciated. _ We are executing a CustomAction to start the Sharepoint Administration and Sharepoint Timer services. This customaction is executed after performing all the install action and just before the *InstallFinalize* action of the installer. This

[WiX-users] Prevent WiX MSBuild script from deleting priviously compiled MSI?

When compiling multiple MSIs with different names from the same MSBuild script, only the last compiled MSI survives. Is there something I can do in my main MSBuild script to prevent the WiX MSBuild script from deleting the previously build MSI file? A comment in wix.targets says:

Re: [WiX-users] (no subject)

Try this, I have able to get it working for SQLExpress 2008 with VS2008. It copies to local folder. Project DefaultTargets=Build xmlns=http://schemas.microsoft.com/developer/msbuild/2003; ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.3.5.SP1 ProductName.NET Framework

[WiX-users] RadioButtons and Feature

I am confused on how to set a feature to a Radiobutton selection. I have 4 Features 1. Feature1 2. Feature2 3. Feature3 4. Feature4 I copied WixUI_Mondo and modified to include my custom Dialog which has 4 radiobuttons and one checkbox. Now, I can compile and run and even see the dialog

Re: [WiX-users] Getting the version from the Assembly file

I'm not sure why you say that this is rare or dangerous. Isn't it, in fact, common practice to have the version number as part of the .msi package name? It's how a user can know which version they're installing. Is this a frowned upon procedure in WiX? On Sat, Jan 17, 2009 at 1:47 PM, Bob

[WiX-users] ServiceControl element question

Hi All, I posted this last week and didn't hear back from anyone...please if anyone has any ideas, it would be great to hear them. I have an install which stops and starts the ReportingServicesService.exe service during the course of the installation. The problem I am running into is

Re: [WiX-users] Getting the version from the Assembly file

Colin Fox wrote: I'm not sure why you say that this is rare or dangerous. Because MSI doesn't support changing the .msi package name except by major upgrade. -- sig://boB http://joyofsetup.com/ -- This SF.net

Re: [WiX-users] Environment Variable disappears after installing a Patch

Gremlin wrote: I created a patch with pyro. After installing the patch the environment variables disappear. Check a verbose log. -- sig://boB http://joyofsetup.com/ -- This SF.net email is sponsored by:

Re: [WiX-users] My MSI is checking for .Net prerequisites when uninstalling?

Bob Lim wrote: How do I fix my code in such that MSI doesn't check the install pre-requisites when uninstalling? Use Installed OR as part of your launch condition, so it's always true. See also

Re: [WiX-users] Disable Features in Feature tree

Jagdish Sakhiya wrote: I want to show only one feature tree in customize dialog. Disable the features you don't want to show, using feature conditions or Remove control events. -- sig://boB http://joyofsetup.com/

Re: [WiX-users] Why Usernames get deleted during minor update?

Joe Osman wrote: My original wix install creates two user names during the installation. I am currently testing a minor update that I've created and I've noticed that it deletes the two user names. I have no idea why it does it and I will thank you for your help. Check a verbose log.

Re: [WiX-users] Getting the version from the Assembly file

And no, it isn't common (in my experience). -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Monday, January 19, 2009 09:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Getting the version from the Assembly file Colin Fox wrote:

Re: [WiX-users] Getting the version from the Assembly file

Every release of our software *is* a major upgrade, so it meets that criteria. I still don't understand why the filename would be an issue. There are GUIDs all over the place for tracking things - why would msi care what I called the file? On Mon, Jan 19, 2009 at 9:25 AM, Bob Arnson

Re: [WiX-users] Getting the version from the Assembly file

Let's take the release of Wix 3 as an example. I'm actually the first in my company to start using it. I want to make sure that everyone is on the same version. But if the msi file is called wix3.msi - how do they know whether or not that is the version they need to install? Regardless - the way

Re: [WiX-users] Getting the version from the Assembly file

Ok, I've tried this but I can't determine where this is supposed to go. I can't find any complete examples that actually use this. Here's what I tried, which doesn't work: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;

Re: [WiX-users] Getting the version from the Assembly file

Colin Fox wrote: I still don't understand why the filename would be an issue. There are GUIDs all over the place for tracking things - why would msi care what I called the file? For whatever reason, it does. See the MSI SDK topic Changing the Product Code. -- sig://boB

Re: [WiX-users] ServiceControl element question

Amy Rosewater wrote: In this scenario, is it possible to specific which exact service I want to restart using the ServiceControl element? The ServiceControl table uses a formatted string for the Name, so you can use SetProperty custom actions to construct a property with the right name

[WiX-users] ServiceInstall failing with newly created user

this is my Wix file (in part): util:User CreateUser=yes Id=id_NewUser Name=NewUser Password=password Domain=[ComputerName] FailIfExists=no PasswordNeverExpires=yes LogonAsService=yes RemoveOnUninstall=yes /util:User ServiceInstall Id=newservice Name=newservice DisplayName=New

Re: [WiX-users] clickThrough in production software

No. ClickThrough was essentially been punted to WiX v4 due to the goal of stabilizing WiX v3 in the very short term. -Original Message- From: Andy2k8 [mailto:appr...@gmail.com] Sent: Monday, January 19, 2009 05:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] clickThrough in

Re: [WiX-users] issue with Cancelling installation when custom action is running.

Is the CustomAction deferred? Also, there isn't a lot of time just before InstallFinalize. Unless your CustomAction is long running and handles cancel progress well, there might not be enough time to click on it before the installer is finalized. -Original Message- From: Monish C

Re: [WiX-users] Getting the version from the Assembly file

0. Probably aren't a lot of examples out there. It is relatively new functionality. 1. the !(bind.Xxx) means binder variable while $(var.Xxx) means preprocessor variable. Preprocessing is the very first process run in the WiX toolset (in candle) and binding is the very last (in light).

[WiX-users] Votive Fails to compile

Hi All, I wonder if anybody has the solution to an issue I have whilst compiling WIX? I have followed Neil Sleightholm's blog entry on creating a Wix build machine, which is a pretty good article. Therefore I *should* have all the prerequisites in place to build WIX, however, my build is still

Re: [WiX-users] Getting the version from the Assembly file

0. ARP shows you the version of the product installed and the directory name provides a quick glimpse of the version since opening the MSI can take more time. 1. WiX does support you naming your MSI whatever you want. You may just have to do more work on your end if it isn't something that

Re: [WiX-users] Getting the version from the Assembly file

Not our rule. Windows Installer named the game: http://blogs.msdn.com/robmen/archive/2004/12/08/278746.aspx -Original Message- From: Colin Fox [mailto:greenene...@gmail.com] Sent: Monday, January 19, 2009 09:36 To: General discussion for Windows Installer XML toolset. Subject: Re:

Re: [WiX-users] Votive Fails to compile

The latest WiX toolset was just built on Saturday. Your deep in Votive and MSBuild territory. Neither place I'm strong. It is also some of the more dark and twisty places. -Original Message- From: Oliver Wickham [mailto:oliver.wick...@skinkers.com] Sent: Monday, January 19, 2009

Re: [WiX-users] Votive Fails to compile

Oliver Wickham wrote: C:\code\sharedlibs\upstream\Wix\cvs\wix\src\votive\SDK_VS2008\Tools\Buil d\Microsoft.VsSDK.Build.Tasks.dll. Could not load file or assembly 'Microsoft.VsSDK.Build.Tasks, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access

Re: [WiX-users] Getting the version from the Assembly file

On Mon, Jan 19, 2009 at 10:22 AM, Rob Mensching rob.mensch...@microsoft.com wrote: 0. Probably aren't a lot of examples out there. It is relatively new functionality. I would be happy with one example. :) 1. the !(bind.Xxx) means binder variable while $(var.Xxx) means preprocessor

Re: [WiX-users] Getting the version from the Assembly file

On Mon, Jan 19, 2009 at 10:26 AM, Rob Mensching rob.mensch...@microsoft.com wrote: 0. ARP shows you the version of the product installed and the directory name provides a quick glimpse of the version since opening the MSI can take more time. What is ARP? (I'm sure you don't mean Address

Re: [WiX-users] Votive Fails to compile

Hi Bob. Thanks for coming back to me. The tree is not being virus scanned and reflector seems perfectly happy with the dll. I think it's more to do with the version conflict aspect of the original message: warning MSB3247: Found conflicts between different versions of the same dependent assembly

Re: [WiX-users] Votive Fails to compile

Thanks for coming back to me so quickly. Can you point me the direction of somebody who is able to illuminate some of the darker places in WIX? Also, can you describe your build environment? Maybe that would help me understand what I have different to you. BTW, I love the idea of WIX. Can you

Re: [WiX-users] Getting the version from the Assembly file

0. Almost always, ARP around here means Add/Remove Programs which was renamed Products and Features in Vista but everyone still calls it ARP. 1. That's all MSBuild goo. I'm not really strong with MSBuild goo so you'd be better off asking someone else. The name of your MSI is controlled by

Re: [WiX-users] Votive Fails to compile

1. For these types of problems it just takes digging into the specific error message. I've been extremely disappointed with the complexity of creating Visual Studio Packages (like our Votive), especially stuff that tries to work on VS2005 and VS2008. We have tons of software on the build

Re: [WiX-users] Getting the version from the Assembly file

I would be happy with one example. I use ?define Version = !(bind.fileVersion.MyFile.exe) ? in several installs. I would also point out the file version that MSI uses for replacing files and what you see when you right click on a file and look at its properties is not the Assembly version

Re: [WiX-users] Getting the version from the Assembly file

.2. My understanding of the .NET Framework documentation does not recommend setting the fileVersion in the assembly identity. They recommend SxS semantics by upgrading the assembly's version only. You can drive your product version off of an assembly's version using

[WiX-users] 64-bit vs. 32-bit Vista Registry writing trouble

I am using WiX to build installers that is working very well for 32-bit and for some 64-bit platforms. I have two WiX projects in my solution, one that targets the 32-bit installation and one that targets the 64-bit installation. The payload contains a couple of .NET assemblies and a registry

Re: [WiX-users] Verification of user account

I didn't see a response to this does anyone have a sample of this? -Original Message- From: Anupama Nair [mailto:an0032...@techmahindra.com] Sent: Friday, December 12, 2008 1:05 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Verification of user account Hi, Can somebody

Re: [WiX-users] Getting the version from the Assembly file

That did the trick - Thanks neil! On Mon, Jan 19, 2009 at 1:18 PM, Neil Sleightholm n...@x2systems.comwrote: I would be happy with one example. I use ?define Version = !(bind.fileVersion.MyFile.exe) ? in several installs. I would also point out the file version that MSI uses for replacing

Re: [WiX-users] 64-bit vs. 32-bit Vista Registry writing trouble

Skip Sailors wrote: Component Id=ComponentRegistry Guid=yada-yada-blah-blah-blah RegistryKey Id=RegistrationFile Root=HKLM Key=Software\Classes\Wow6432Node\CLSID\{ yada-yada-blah-blah-blah } Action=createAndRemoveOnUninstall It's not normally necessary to

Re: [WiX-users] Votive Fails to compile

Oliver Wickham wrote: Hi Bob. Thanks for coming back to me. The tree is not being virus scanned and reflector seems perfectly happy with the dll. I think it's more to do with the version conflict aspect of the original message: warning MSB3247: Found conflicts between different versions of

[WiX-users] Radio Button Both Evaluating to pass condition

Hey everyone, I am implementing a custom UI where I would like the user to either accept or decline a radio button. I want the next button to be disabled until they select EITHER option. I don't care if it is yes or no, I just want them to make a decision. Here is the snippet and I can't seem

Re: [WiX-users] Why Usernames get deleted during minor update? - howto skip ConfigureUsers action?

Nothing much in the verbose log - ConfigureUsers action starts and it removes the users but it doesn't explain why the users are removed. Is there a way to skip the ConfigureUsers action during a product upgrade? Thanks Bob Arnson wrote: Joe Osman wrote: My original wix install creates

Re: [WiX-users] clickThrough in production software

Ok. In that case what is the best way to add automatic update feature to a WiX 2/ WiX 3 based MSI ? Rob Mensching-2 wrote: No. ClickThrough was essentially been punted to WiX v4 due to the goal of stabilizing WiX v3 in the very short term. -Original Message- From: Andy2k8

Re: [WiX-users] RadioButtons and Feature

Hi Here is my solution to this. I don't know if there is something easier or better. The radiobuttongroup controls some property RadioButtonGroup Property=PROPERTY RadioButton Text=Feature1 Value=Feature1 X=5 Y=0 Width=140 Height=15 / RadioButton Text=Feature2

Re: [WiX-users] Getting the version from the Assembly file

2. My understanding of the .NET Framework documentation does not recommend setting the fileVersion in the assembly identity. They recommend SxS semantics by upgrading the assembly's version only. Apologies for going off topic but... I think this is true but rarely practical, in reality you

Re: [WiX-users] Getting the version from the Assembly file

Just a thought, you might was to consider a simple bootstrapper that wraps up the msi. You could then keep the msi filename the same but change the name of the bootstrapper exe, that way you don't break the msi rule. Neil -Original Message- From: Colin Fox [mailto:greenene...@gmail.com]