Re: [WiX-users] Add Domain Group to Local Group
I'd love to help my career path never took me down the Win32 C++ route. I did ANSI C on Solaris for awhile in the mid 1990's and then moved onto RAD languages like PowerBuilder, VB, Delphi and then C#. At my day job in mid-tier engineering (The Home Depot) my "production" is all server 2008 R2 so I use C#/DTF custom actions with impuginty. From: "Rob Mensching" Sent: Saturday, January 07, 2012 4:00 PM To: "General discussion for Windows Installer XML toolset." , chr...@iswix.com Subject: Re: [WiX-users] Add Domain Group to Local Group Didn't know the User element could find groups. That's probably some accidental side effect. Creating groups is another thing that would be nice if someone implemented. Rollback on it is really, really hard, IIRC. On Sat, Jan 7, 2012 at 1:26 PM, Christopher Painter wrote: FWIW, I'd consider a doco note saying that it can find groups to be good enough. What I've actually needed even more in the past was the ability to create groups. The Group element has a note saying that it can't create groups. I've always resorted to custom actions to do this. From: "Christopher Painter" Sent: Saturday, January 07, 2012 11:28 AM To: "Rob Mensching" , "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Add Domain Group to Local Group It seems that despite being called the util:User element that it was actually able to locate an ActiveDirectory Group. I just left many of the attributes blank and told it to not create or update the user. I don't have the C++ chops to extend these but there is another thread about creating interfaces for DTF classes to enable unit test mocking. I'd be willing to contribute that if you would like. From: "Rob Mensching" Sent: Saturday, January 07, 2012 11:17 AM To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Add Domain Group to Local Group That's all that is supported today. It would be fantastic if you wanted to contribute the code to do more. On Tue, Jan 3, 2012 at 2:18 PM, Christopher Painter wrote: I work in an enterprise environment and I have a request to add an Active Directory Group to a Local Group. Problem is I see the util::GroupRef element only allows util::User as a parent and not util::Group as a parent. I'd like to be able to run this MSI through SCCM and pass Domain/Name in as secure custom properties and use them as formatted attributes in the Group Element. Does anyone know why this is? I'm sure I can write a DTF custom action but I'm trying not to. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] add files during minor upgrade
Check out: http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upgrade-in-MSI-Use . That usually finds the problem. On Sat, Jan 7, 2012 at 9:42 AM, wrote: > Hi! > > I want to add files to my installed program with a minor upgrade. > I’ve got an msi installer, works fine. > > Now I’ve created an upgrade msi, it only contains 1 file i want to add to > the existing installation, > but it doesn’t work, the upgrade runs without error, but the file is > missing. > > Thanks in advance: > Imre Horvath > > -- > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add Domain Group to Local Group
Didn't know the User element could find groups. That's probably some accidental side effect. Creating groups is another thing that would be nice if someone implemented. Rollback on it is really, really hard, IIRC. On Sat, Jan 7, 2012 at 1:26 PM, Christopher Painter wrote: > FWIW, I'd consider a doco note saying that it can find groups to be good > enough. What I've actually needed even more in the past was the ability > to create groups. The Group element has a note saying that it can't create > groups. I've always resorted to custom actions to do this. > > -- > *From*: "Christopher Painter" > *Sent*: Saturday, January 07, 2012 11:28 AM > *To*: "Rob Mensching" , "General discussion for > Windows Installer XML toolset." > > *Subject*: Re: [WiX-users] Add Domain Group to Local Group > > > > > It seems that despite being called the util:User element that it was > actually able to locate an ActiveDirectory Group. I just left many of the > attributes blank and told it to not create or update the user. > > > I don't have the C++ chops to extend these but there is another thread > about creating interfaces for DTF classes to enable unit test mocking. I'd > be willing to contribute that if you would like. > > > > From: "Rob Mensching" > > Sent: Saturday, January 07, 2012 11:17 AM > > To: chr...@iswix.com, "General discussion for Windows Installer XML > toolset." > > Subject: Re: [WiX-users] Add Domain Group to Local Group > > > That's all that is supported today. It would be fantastic if you wanted to > contribute the code to do more. > > > On Tue, Jan 3, 2012 at 2:18 PM, Christopher Painter > wrote: > > I work in an enterprise environment and I have a request to add an Active > > Directory Group to a Local Group. Problem is I see the util::GroupRef > > element only allows util::User as a parent and not util::Group as a > parent. > > I'd like to be able to run this MSI through SCCM and pass Domain/Name in > > as secure custom properties and use them as formatted attributes in the > > Group Element. > > > Does anyone know why this is? I'm sure I can write a DTF custom action > but > > I'm trying not to. > > > > > -- > > Write once. Port to many. > > Get the SDK and tools to simplify cross-platform app development. Create > > new or port existing apps to sell to consumers worldwide. Explore the > > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > > http://p.sf.net/sfu/intel-appdev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > > virtually, Rob Mensching - http://RobMensching.com LLC > > > > -- > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add Domain Group to Local Group
FWIW, I'd consider a doco note saying that it can find groups to be good enough. What I've actually needed even more in the past was the ability to create groups. The Group element has a note saying that it can't create groups. I've always resorted to custom actions to do this. From: "Christopher Painter" Sent: Saturday, January 07, 2012 11:28 AM To: "Rob Mensching" , "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Add Domain Group to Local Group It seems that despite being called the util:User element that it was actually able to locate an ActiveDirectory Group. I just left many of the attributes blank and told it to not create or update the user. I don't have the C++ chops to extend these but there is another thread about creating interfaces for DTF classes to enable unit test mocking. I'd be willing to contribute that if you would like. From: "Rob Mensching" Sent: Saturday, January 07, 2012 11:17 AM To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Add Domain Group to Local Group That's all that is supported today. It would be fantastic if you wanted to contribute the code to do more. On Tue, Jan 3, 2012 at 2:18 PM, Christopher Painter wrote: I work in an enterprise environment and I have a request to add an Active Directory Group to a Local Group. Problem is I see the util::GroupRef element only allows util::User as a parent and not util::Group as a parent. I'd like to be able to run this MSI through SCCM and pass Domain/Name in as secure custom properties and use them as formatted attributes in the Group Element. Does anyone know why this is? I'm sure I can write a DTF custom action but I'm trying not to. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add Domain Group to Local Group
It seems that despite being called the util:User element that it was actually able to locate an ActiveDirectory Group. I just left many of the attributes blank and told it to not create or update the user. I don't have the C++ chops to extend these but there is another thread about creating interfaces for DTF classes to enable unit test mocking. I'd be willing to contribute that if you would like. From: "Rob Mensching" Sent: Saturday, January 07, 2012 11:17 AM To: chr...@iswix.com, "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Add Domain Group to Local Group That's all that is supported today. It would be fantastic if you wanted to contribute the code to do more. On Tue, Jan 3, 2012 at 2:18 PM, Christopher Painter wrote: I work in an enterprise environment and I have a request to add an Active Directory Group to a Local Group. Problem is I see the util::GroupRef element only allows util::User as a parent and not util::Group as a parent. I'd like to be able to run this MSI through SCCM and pass Domain/Name in as secure custom properties and use them as formatted attributes in the Group Element. Does anyone know why this is? I'm sure I can write a DTF custom action but I'm trying not to. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Cascading Merge Modules
IMO, in certain situations, merge modules are not quite dead. Here's my opinion: http://blog.iswix.com/2010/09/in-defense-of-merge-modules.html If you are staying in a WiX world, yes, wixlibs and fragments are a better solution. If you are using a combination of tools such as WiX and InstallShield then those aren't available. If you are taking a component from a third party then frequently bootstrapping/chaining is a better solution. After that deploying privately as your own component is a good solution and taking a dependency on a third party merge module is usually asking for trouble down the road. Authoring and using your own in house merge modules are quiet safe. That all said, I've created massive frameworks that supported distributed setup development in a product line development environment. With the rule that we only suport major upgrades with the occasional limited patch, it worked out very, very well. We had hundreds of developers with a good many of them contributing to the installation development and only a couple MSI experts to guide them along the way. From: "Rob Mensching" Sent: Saturday, January 07, 2012 10:58 AM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Cascading Merge Modules Merge Modules are a build time concept only. The Windows Installer does not undersstand them at all. This fact is a large part of the reason Merge Modules are dying. One key issue is that Merge Modules make things very difficult to patch (because patching was implemented after Merge Modules but didn't take Merge Modules into account). Your final conclusion is exactly how I feel about Merge Modules: http://www.robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why- would-you-use-them On Sat, Dec 24, 2011 at 1:54 AM, Andreas wrote: > David, > > Thanks for your reply. I always thought that MSM is used for a "common > component" that can be installed from different MSI installers. The > "common component" should be uninstalled when the last MSI is unstalled > using a kind of reference management. > > Your proposal uses a different approach. The wixlib adds some components > to the MSI that are installed as like it is a part of the product > itself. I gave it a try and it works. Obviously the reference management > is performed on component level not on any kind of merge module level. > - Can you confirm this? > - Is the MSM completely integrated in the MSI file and does it give no > kind of "grouping", "isolation of any kind" or so? > > So I assume I would only use MSM when I have to cooperate with an > installer tool other that WiX. > > Andy > > Am 23.12.2011 15:10, schrieb David Watson: > > Hi, > > You only need to use merge modules if you want to supply them to third > > parties for use in their installations that do not use wix. > > If you do not have this requirement then you can split your installer up > to > > use a Base and tool wixlib when then can be linked into the tool and > product > > MSIs. Think of a wixlib as a c static linked library, you would have two > > separate ones and link them both into the resultant MSI. > > > > You can also have several wix fragments and build each MSI from > combining the > > appropriate source files without bothering with a wixlib. > > > > Dave > > > > -Original Message- > > From: Andreas [mailto:andreassand...@gmx.net] > > Sent: 23 December 2011 13:42 > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] Cascading Merg Modules > > > > I have a question about design of installer and merge modules. > > I have a COM server as base component. This is reusable and must be used > > a by a tool. Further this tool may be part of a product. > > > > BaseComponent + Tool -> ToolInstaller > > BaseComponent + Tool + Application -> ProductInstaller > > > > I want to design the best set of WiX projects. Since the base component > > is reusable it should be implemented with a merge module, shouldn't it? > > When I build the tool installer I will use a WiX product project to > > generate a MSI file. But how should I integrate the tool installation in > > the product? One solution would be a tool merge module. But does the > > product always have to add the tool merge module and the base component > > merge module. Or can I design the tool merge module to "include" the > > base component? > > > > How can a wix library help here? > > > > > > > - > > - > > Write once. Port to many. > > Get the SDK and tools to simplify cross-platform app development. Create > > new or port existing apps to sell to consumers worldwide. Explore the > > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > > http://p.sf.net/sfu/intel-appdev > > __
[WiX-users] add files during minor upgrade
Hi! I want to add files to my installed program with a minor upgrade. I’ve got an msi installer, works fine. Now I’ve created an upgrade msi, it only contains 1 file i want to add to the existing installation, but it doesn’t work, the upgrade runs without error, but the file is missing. Thanks in advance: Imre Horvath -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] "Add/Remove Programs" doesn't refresh sometimes
On 05-Jan-12 09:05, Bruce Cran wrote: > From a verbose install log I see that MainEngineThread is returning > ERROR_SUCCESS_REBOOT_REQUIRED (3010) - I wonder if WI only checks for > ERROR_SUCCESS when determining if it should refresh the list, or not > the other ERROR_SUCCESS_* values? If so, would that be a bug? Sure. Good luck getting the Windows Shell team to change it. -- sig://boB http://joyofsetup.com/ -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Assembiles FROM the GAC
On 06-Jan-12 16:58, Daniel Sniderman wrote: > These are SQL Server related DLL's - so I can't assume they will be on the > GAC of the target machine - and I'd like to simply continue to include them > as files in the MSI - i.e. I don't want to GAC them on the target machine. You probably don't have a choice: Check your SQL EULA to determine what the rules are about redistributing their files. -- sig://boB http://joyofsetup.com/ -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Minor Upgrade Patching - Preventing Downgrade
On 05-Jan-12 16:33, Hoover, Jacob wrote: >Is there a way of informing an end user that a patch is not valid (due > to a newer patch all ready being applied)? Check patch applicability. That's what Burn does. The 1.0.2 MSP won't be applicable to a 1.0.3 product. -- sig://boB http://joyofsetup.com/ -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Cascading Merge Modules
Merge Modules are a build time concept only. The Windows Installer does not undersstand them at all. This fact is a large part of the reason Merge Modules are dying. One key issue is that Merge Modules make things very difficult to patch (because patching was implemented after Merge Modules but didn't take Merge Modules into account). Your final conclusion is exactly how I feel about Merge Modules: http://www.robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why-would-you-use-them On Sat, Dec 24, 2011 at 1:54 AM, Andreas wrote: > David, > > Thanks for your reply. I always thought that MSM is used for a "common > component" that can be installed from different MSI installers. The > "common component" should be uninstalled when the last MSI is unstalled > using a kind of reference management. > > Your proposal uses a different approach. The wixlib adds some components > to the MSI that are installed as like it is a part of the product > itself. I gave it a try and it works. Obviously the reference management > is performed on component level not on any kind of merge module level. > - Can you confirm this? > - Is the MSM completely integrated in the MSI file and does it give no > kind of "grouping", "isolation of any kind" or so? > > So I assume I would only use MSM when I have to cooperate with an > installer tool other that WiX. > > Andy > > Am 23.12.2011 15:10, schrieb David Watson: > > Hi, > > You only need to use merge modules if you want to supply them to third > > parties for use in their installations that do not use wix. > > If you do not have this requirement then you can split your installer up > to > > use a Base and tool wixlib when then can be linked into the tool and > product > > MSIs. Think of a wixlib as a c static linked library, you would have two > > separate ones and link them both into the resultant MSI. > > > > You can also have several wix fragments and build each MSI from > combining the > > appropriate source files without bothering with a wixlib. > > > > Dave > > > > -Original Message- > > From: Andreas [mailto:andreassand...@gmx.net] > > Sent: 23 December 2011 13:42 > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] Cascading Merg Modules > > > > I have a question about design of installer and merge modules. > > I have a COM server as base component. This is reusable and must be used > > a by a tool. Further this tool may be part of a product. > > > > BaseComponent + Tool -> ToolInstaller > > BaseComponent + Tool + Application -> ProductInstaller > > > > I want to design the best set of WiX projects. Since the base component > > is reusable it should be implemented with a merge module, shouldn't it? > > When I build the tool installer I will use a WiX product project to > > generate a MSI file. But how should I integrate the tool installation in > > the product? One solution would be a tool merge module. But does the > > product always have to add the tool merge module and the base component > > merge module. Or can I design the tool merge module to "include" the > > base component? > > > > How can a wix library help here? > > > > > > > - > > - > > Write once. Port to many. > > Get the SDK and tools to simplify cross-platform app development. Create > > new or port existing apps to sell to consumers worldwide. Explore the > > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > > http://p.sf.net/sfu/intel-appdev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > SDL PLC confidential, all rights reserved. > > If you are not the intended recipient of this mail SDL requests and > requires that you delete it without acting upon or copying any of its > contents, and we further request that you advise us. > > SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207. > > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire > SL6 7DY, UK. > > > > > > > -- > > Write once. Port to many. > > Get the SDK and tools to simplify cross-platform app development. Create > > new or port existing apps to sell to consumers worldwide. Explore the > > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > > http://p.sf.net/sfu/intel-appdev > > > > > -- > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > ___ > WiX-users mailing list > WiX-users
Re: [WiX-users] WIX Progress bar repeats twice during installation/uninstallation
MSI SDK. On Tue, Jan 3, 2012 at 9:41 AM, shanmukha sainath addepalli < sainath.addepa...@gmail.com> wrote: > Thanks for the reply Rob. > > I never used Burn. Is there any documentation explaining about creating > external UI handler? > can you please provide me any documentation related to that. > > Thanks, > Sainath A. > > On Tue, Jan 3, 2012 at 2:13 PM, Rob Mensching > wrote: > > > What you are seeing is the default behavior of the Windows installer UI. > It > > actually goes by 3 times typically, but the last one can be really fast > so > > you might not have noticed it. It might go by more than 3 times as well. > > > > The only way to change that behavior is to create an external UI handler. > > Burn (in WiX v3.6) provides a nice abstraction away from all that junk so > > that you can show a single progress bar. > > > > On Mon, Jan 2, 2012 at 11:35 AM, shanmukha sainath addepalli < > > sainath.addepa...@gmail.com> wrote: > > > > > Hi, > > > > > > I am using WIX 3.5. Here is my problem.. > > > > > > During installation, Progress bar repeats twice before completion. > Means, > > > Progress bar starts from 0 and reaches 100%, and then resets back and > > > starts again. I am not sure that this is the issue with WIX or Windows > > > Installer. > > > > > > Is there any way that we can fix this, such that it won't reset during > > > install/uninstall. > > > > > > If it is not possible to fix this, is there any chance to add another > > > progress bar which we can control its status from custom actions, so > that > > > the original one(or the first one) can be treated as component status > and > > > second one can be treated as Overall status. > > > > > > As we update the progress from the custom action, we can make sure that > > its > > > progress value will not reach 100% prior to installation completion. > > > > > > > > > Sainath > > > > > > > > > -- > > > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a > complex > > > infrastructure or vast IT resources to deliver seamless, secure access > to > > > virtual desktops. With this all-in-one solution, easily deploy virtual > > > desktops for less than the cost of PCs and save 60% on VDI > infrastructure > > > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > > > ___ > > > WiX-users mailing list > > > WiX-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > > > > -- > > virtually, Rob Mensching - http://RobMensching.com LLC > > > > > -- > > Write once. Port to many. > > Get the SDK and tools to simplify cross-platform app development. Create > > new or port existing apps to sell to consumers worldwide. Explore the > > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > > http://p.sf.net/sfu/intel-appdev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > -- > Regards > Sainath > DeskStream > > -- > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add Domain Group to Local Group
That's all that is supported today. It would be fantastic if you wanted to contribute the code to do more. On Tue, Jan 3, 2012 at 2:18 PM, Christopher Painter wrote: > I work in an enterprise environment and I have a request to add an Active > Directory Group to a Local Group. Problem is I see the util::GroupRef > element only allows util::User as a parent and not util::Group as a parent. > I'd like to be able to run this MSI through SCCM and pass Domain/Name in > as secure custom properties and use them as formatted attributes in the > Group Element. > > > Does anyone know why this is? I'm sure I can write a DTF custom action but > I'm trying not to. > > > -- > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Globalized Bundle?
The wixstdba will automatically search for a .wxl file of the system language (i.e. look in 1033 directory for english and 1041 for german and 1044 for japanese, or are those last two switched?). Failing to find a matching .wxl file will cause wixstdba to fall back to a .wxl in the root. There are a few bugs about localization open that need to be fixed before this works well but you can see the beginnings. On Thu, Jan 5, 2012 at 2:59 PM, Ian Williams wrote: > I'm trying to investigate the viability of making my bundle installer > "globalized" - that is, it is one installer that will look at the language > of the system in order to choose how to present itself to the user (and > perhaps what to install). I thought that was one of the advantages of using > a bundle, but I'm realizing now that that doesn't seem to be part of the > intent. > > For starters, I wanted to do something like > > Value="...[SystemLanguageId]...license.rtf" /> > > But I can't have a PropertyRef in a bundle. There are more issues that > leave me to believe that bundles are not designed to be able to > intelligently choose a language to present themselves in... at least with > WixStdBA (been trying to avoid writing my own BA). > > Does anyone have any advice on what direction I should be going here? If > this doesn't work I guess users must choose what language the installer > will be in when the download it (so I need to make a different version of > the .exe for each language using the !(loc.X) stuff). > > Thanks, > Ian > > > -- > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: check for MSI existence and validity
1. If a package cannot be found, you will get a source resolution callback. 2. At the very least Burn does a SHA1 hash of the files to verify they are correct before installing them for security reasons. If you digitally sign your payloads, Burn will verify the signatures instead of hashing (which ends up being the same thing basically). On Fri, Jan 6, 2012 at 7:04 AM, Kryschan < christian.hennig@wincor-nixdorf.com> wrote: > Hi, > > We created several bootstrapper projects, which include some MSI packages > with option Compressed='no'. As a result the MSIs have to be: > 1) available on the file system at the right location (relative to the > bootstrapper) and > 2) available in the right version (which means it has to be exactly the > same > file which was used when the bootstrapper was built). > Otherwise the bootstrapper fails to install. > > Is there a possibility to check those prerequisites from the managed > bootstrapper UX library? > 1) For checking the existence of the MSIs one would need the expected > location of the packages relative to the bootstrapper. But in events like > BootstrapperApplication.DetectPackageComplete there is no such information. > 2) Here it would be useful to know what burn does to check if the MSI file > is the one which was used during build. Is it a CRC check? > > Best regards > Kryschan > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-check-for-MSI-existence-and-validity-tp7158657p7158657.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] APPCRASH cancleing install in vi burn UI
I think there is a bug about Cancel during progress in the wixstdba failing
already. Yes, it needs to be fixed.
On Fri, Jan 6, 2012 at 8:59 AM, Michael_A wrote:
> I'm re-posting this as I never got an answer.
>
> Canceling Installing burn generated install results in the following. If
> additional information is needed please let me know as I can reproduce this
> at ANY time.
>
> Faulting application name: BootStrapper.exe, version: 1.0.0.0, time stamp:
> 0x4ea1ab8c
> Faulting module name: wixstdba.dll, version: 3.6.2221.0, time stamp:
> 0x4ea1aeb1
> Exception code: 0xc005
> Fault offset: 0x00012a9b
> Faulting process id: 0x72c
> Faulting application start time: 0x019195389ea5
> Faulting application path: \\Dev_tt-01\c\Builds\1234\BootStrapper.exe
> Faulting module path:
>
> C:\Users\std_user\AppData\Local\Temp\{38fa7123-9621-4c8c-8920-7d3971a3e9cd}\.ba1\wixstdba.dll
> Report Id: e1b04bcf-3884-11e1-a168-000c29364574
>
> Fault bucket , type 0
> Event Name: APPCRASH
> Response: Not available
> Cab Id: 0
>
> Problem signature:
> P1: BootStrapperr.exe
> P2: 1.0.0.0
> P3: 4ea1ab8c
> P4: wixstdba.dll
> P5: 3.6.2221.0
> P6: 4ea1aeb1
> P7: c005
> P8: 00012a9b
> P9:
> P10:
>
> Attached files:
>
> These files may be available here:
>
> C:\Users\std_user\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_BootStrapper_32cfc73515b9b83dde85dda819cf8cddcf4255b_0a115913
>
> Analysis symbol:
> Rechecking for solution: 0
> Report Id: e1b04bcf-3884-11e1-a168-000c29364574
> Report Status: 0
>
>
> -Michael Clark
> clark_mich...@live.com
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/APPCRASH-cancleing-install-in-vi-burn-UI-tp7159047p7159047.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
virtually, Rob Mensching - http://RobMensching.com LLC
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Framework 4.0 LINK instead of bootstrapper
Burn supports that. WiX v3.6 does this exact thing for NETFX 4. On Thu, Jan 5, 2012 at 6:22 PM, Bruce Gombrelli (Experis) < v-bru...@microsoft.com> wrote: > I'd like to check and install Framework 4.0 from a **LINK** rather than > having to include the entire framework 4.1 (and Windows installer 3.1) in > my distribution package. > > I'm currently doing it using an bootstrapper but have to package up the > Framework 4.0 and windows installer 3.1 in my download package (I rather > hefty requirement for the download). > > Thanks in Advance, > >Bruce Gombrelli > > > > -- > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
