wix-devs — Windows Installer XML toolset developer mailing list

Re: [WiX-devs] New branch for wix311?

[Rob M. <ro...@fi...>]

You can submit pull requests against wix3/develop. That will become v3.11 after v3.10 moves to master.

_______________________________________________________________
FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

From: Heath Stewart [mailto:Hea...@mi...]
Sent: Wednesday, July 8, 2015 2:41 PM
To: WiX toolset developer mailing list
Subject: [WiX-devs] New branch for wix311?

Since we're trying to lock down 3.10, can we open a branch for proposed 3.11 work? I found a bug in DTF I'd like to fix in privates at least to unblock some automation. I can always rebase later, but figured if there's bugs we know aren't release-blocking for 3.10 we could start queueing them up for 3.11.

Heath Stewart
Software Engineer
Visual Studio Deployment Experience, Microsoft
http://blogs.msdn.com/heaths

[WiX-devs] New branch for wix311?

[Heath S. <Hea...@mi...>]

Since we're trying to lock down 3.10, can we open a branch for proposed 3.11 work? I found a bug in DTF I'd like to fix in privates at least to unblock some automation. I can always rebase later, but figured if there's bugs we know aren't release-blocking for 3.10 we could start queueing them up for 3.11.

Heath Stewart
Software Engineer
Visual Studio Deployment Experience, Microsoft
http://blogs.msdn.com/heaths

[WiX-devs] Comment on Meeting #72

[Phill H. <pho...@ri...>]

I missed the last couple of meeting doing volunteer work at a nursing home in
MI, but if 3.10 misses the proposed 8/10 date, then consider  this
<http://www.holidayinsights.com/other/lefthand.htm>  .  



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Comment-on-Meeting-72-tp7600842.html
Sent from the wix-devs mailing list archive at Nabble.com.

Re: [WiX-devs] Marking WIPs as Complete

[Heath S. <Hea...@mi...>]

Bob flagged 10 but I may port a couple more, so let's just say an even dozen.

Heath Stewart
Software Engineer
Visual Studio Deployment Experience, Microsoft
http://blogs.msdn.com/heaths

From: Rob Mensching [mailto:ro...@fi...]
Sent: Tuesday, July 7, 2015 10:05 AM
To: WiX toolset developer mailing list <wix...@li...>
Subject: Re: [WiX-devs] Marking WIPs as Complete


1.      If we were to add something to the frontmatter it'd probably be better to actually put the WiX release instead of just "completed". The current process means don't have to go back and update documents again... but <shrug/>

2.      Could do that. How many documents are there?

_______________________________________________________________
FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

From: Heath Stewart [mailto:Hea...@mi...]
Sent: Monday, July 6, 2015 4:29 PM
To: wix...@li...<mailto:wix...@li...>
Subject: [WiX-devs] Marking WIPs as Complete

Rob,

>From our convo at https://github.com/wixtoolset/site/pull/53, you mentioned that WIPs can be completed. I take it that's just by way of checking the issue ID against the release. What about adding a Complete: true|false YAML header as well for quick identification?

Along the same lines, should I create feature at http://wixtoolset.org/issues to track all the docs I'll be importing and just have them reference the same number?

Heath Stewart
Software Engineer
Visual Studio Deployment Experience, Microsoft
http://blogs.msdn.com/heaths

[WiX-devs] WiX Online Meeting #72

[Rob M. <ro...@fi...>]

Next WiX Online meeting will be: July 7th, 2015 @14:30 PST

Agenda items:

*       Triage

.........................................................................................................................................
--> Join Skype Meeting<https://meet.lync.com/firegiant/rob/8G5319FJ>

Help<http://go.microsoft.com/fwlink/?LinkId=389737>

[!OC([1033])!]
.........................................................................................................................................

Re: [WiX-devs] Marking WIPs as Complete

[Rob M. <ro...@fi...>]

1.       If we were to add something to the frontmatter it'd probably be better to actually put the WiX release instead of just "completed". The current process means don't have to go back and update documents again... but <shrug/>


2.       Could do that. How many documents are there?

_______________________________________________________________
FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

From: Heath Stewart [mailto:Hea...@mi...]
Sent: Monday, July 6, 2015 4:29 PM
To: wix...@li...
Subject: [WiX-devs] Marking WIPs as Complete

Rob,

>From our convo at https://github.com/wixtoolset/site/pull/53, you mentioned that WIPs can be completed. I take it that's just by way of checking the issue ID against the release. What about adding a Complete: true|false YAML header as well for quick identification?

Along the same lines, should I create feature at http://wixtoolset.org/issues to track all the docs I'll be importing and just have them reference the same number?

Heath Stewart
Software Engineer
Visual Studio Deployment Experience, Microsoft
http://blogs.msdn.com/heaths

Re: [WiX-devs] Issue Installing WiX 3.10 on Server with 4.5.2 DK Also Installed

[John C. <JoC...@ja...>]

Ah, that makes perfect sense.  I can work around that.

--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoC...@ja...<mailto:JoC...@ja...>



From: Sean Hall [mailto:r.s...@gm...]
Sent: Tuesday, July 7, 2015 9:42 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Issue Installing WiX 3.10 on Server with 4.5.2 DK Also Installed

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.

0x8013141a means strong name validation failed. When building WiX yourself, you have to do an official build or ignore validation on the machine you're installing it on.
On Jul 7, 2015 9:36 AM, "John Cooper" <JoC...@ja...<mailto:JoC...@ja...>> wrote:
I have been installing WiX 3.10 (plus my anti-race changes) on my four build servers.  On three of the four build servers, the install/upgrade is easy.  But on one build server, the only with 4.5.2 Developer’s Kit, the bootstrapper fails immediately after the small “W” dialog appears.  The log has:

[11EC:297C][2015-07-07T08:57:46]i001: Burn v3.10.0.1907, Windows v6.3 (Build 9600: Service Pack 0), path: C:\Users\JoCooper\Desktop\WiX310.exe
[11EC:297C][2015-07-07T08:57:46]i000: Initializing string variable 'InstallFolder' to value '[ProgramFilesFolder]WiX Toolset v3.10'
[11EC:297C][2015-07-07T08:57:46]i009: Command Line: '-burn.unelevated BurnPipe.{6F85AB40-6D6B-4408-B308-4701CF5EE0CC} {2C5BB603-A24C-478C-A996-6FCADAF8CDB5} 5168'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\JoCooper\AppData\Local\Temp\WiX Toolset_v3.10.0.1907_20150707085746.log'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\JoCooper\Desktop\WiX310.exe'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\JoCooper\Desktop\'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleName' to value 'WiX Toolset v3.10.0.1907'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleManufacturer' to value 'Outercurve Foundation'
[11EC:297C][2015-07-07T08:57:46]i000: Loading managed bootstrapper application.
[11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to create the managed bootstrapper application.
[11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to create UX.
[11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to load UX.
[11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed while running
[11EC:297C][2015-07-07T08:57:47]i410: Variable: InstallFolder = C:\Program Files (x86)\WiX Toolset v3.10
[11EC:297C][2015-07-07T08:57:47]i410: Variable: ProgramFilesFolder = C:\Program Files (x86)\
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleAction = 5
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleElevated = 1
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleLog = C:\Users\JoCooper\AppData\Local\Temp\WiX Toolset_v3.10.0.1907_20150707085746.log
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleManufacturer = Outercurve Foundation
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleName = WiX Toolset v3.10.0.1907
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleOriginalSource = C:\Users\JoCooper\Desktop\WiX310.exe
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleOriginalSourceFolder = C:\Users\JoCooper\Desktop\
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleProviderKey = {42ba47c8-4aa9-42f7-9170-5b6152df5c73}
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleTag =
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleVersion = 3.10.0.1907
[11EC:297C][2015-07-07T08:57:47]e000: Error 0x8013141a: Failed to run per-user mode.
[11EC:297C][2015-07-07T08:57:47]i007: Exit code: 0x8013141a, restarting: No

--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoC...@ja...<mailto:JoC...@ja...>


NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-devs mailing list
WiX...@li...<mailto:WiX...@li...>
https://lists.sourceforge.net/lists/listinfo/wix-devs
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

Re: [WiX-devs] Issue Installing WiX 3.10 on Server with 4.5.2 DK Also Installed

[Sean H. <r.s...@gm...>]

0x8013141a means strong name validation failed. When building WiX yourself,
you have to do an official build or ignore validation on the machine you're
installing it on.
On Jul 7, 2015 9:36 AM, "John Cooper" <JoC...@ja...> wrote:

>  I have been installing WiX 3.10 (plus my anti-race changes) on my four
> build servers.  On three of the four build servers, the install/upgrade is
> easy.  But on one build server, the only with 4.5.2 Developer’s Kit, the
> bootstrapper fails immediately after the small “W” dialog appears.  The log
> has:
>
>
>
> [11EC:297C][2015-07-07T08:57:46]i001: Burn v3.10.0.1907, Windows v6.3
> (Build 9600: Service Pack 0), path: C:\Users\JoCooper\Desktop\WiX310.exe
>
> [11EC:297C][2015-07-07T08:57:46]i000: Initializing string variable
> 'InstallFolder' to value '[ProgramFilesFolder]WiX Toolset v3.10'
>
> [11EC:297C][2015-07-07T08:57:46]i009: Command Line: '-burn.unelevated
> BurnPipe.{6F85AB40-6D6B-4408-B308-4701CF5EE0CC}
> {2C5BB603-A24C-478C-A996-6FCADAF8CDB5} 5168'
>
> [11EC:297C][2015-07-07T08:57:46]i000: Setting string variable
> 'WixBundleLog' to value 'C:\Users\JoCooper\AppData\Local\Temp\WiX
> Toolset_v3.10.0.1907_20150707085746.log'
>
> [11EC:297C][2015-07-07T08:57:46]i000: Setting string variable
> 'WixBundleOriginalSource' to value 'C:\Users\JoCooper\Desktop\WiX310.exe'
>
> [11EC:297C][2015-07-07T08:57:46]i000: Setting string variable
> 'WixBundleOriginalSourceFolder' to value 'C:\Users\JoCooper\Desktop\'
>
> [11EC:297C][2015-07-07T08:57:46]i000: Setting string variable
> 'WixBundleName' to value 'WiX Toolset v3.10.0.1907'
>
> [11EC:297C][2015-07-07T08:57:46]i000: Setting string variable
> 'WixBundleManufacturer' to value 'Outercurve Foundation'
>
> [11EC:297C][2015-07-07T08:57:46]i000: Loading managed bootstrapper
> application.
>
> [11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to create
> the managed bootstrapper application.
>
> [11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to create
> UX.
>
> [11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to load UX.
>
> [11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed while
> running
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: InstallFolder = C:\Program
> Files (x86)\WiX Toolset v3.10
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: ProgramFilesFolder =
> C:\Program Files (x86)\
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleAction = 5
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleElevated = 1
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleLog =
> C:\Users\JoCooper\AppData\Local\Temp\WiX
> Toolset_v3.10.0.1907_20150707085746.log
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleManufacturer =
> Outercurve Foundation
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleName = WiX
> Toolset v3.10.0.1907
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleOriginalSource =
> C:\Users\JoCooper\Desktop\WiX310.exe
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable:
> WixBundleOriginalSourceFolder = C:\Users\JoCooper\Desktop\
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleProviderKey =
> {42ba47c8-4aa9-42f7-9170-5b6152df5c73}
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleTag =
>
> [11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleVersion =
> 3.10.0.1907
>
> [11EC:297C][2015-07-07T08:57:47]e000: Error 0x8013141a: Failed to run
> per-user mode.
>
> [11EC:297C][2015-07-07T08:57:47]i007: Exit code: 0x8013141a, restarting: No
>
>
>
> --
>
> *John Merryweather Cooper*
>
> Senior Software Engineer | Integration Development Group | Enterprise
> Notification Service
>
> Jack Henry & Associates, Inc.*® *| Lenexa, KS  66214 | Ext:  431050 |*JoC...@ja...
> <JoC...@ja...>*
>
>
>
> NOTICE: This electronic mail message and any files transmitted with it are
> intended
> exclusively for the individual or entity to which it is addressed. The
> message,
> together with any attachment, may contain confidential and/or privileged
> information.
> Any unauthorized review, use, printing, saving, copying, disclosure or
> distribution
> is strictly prohibited. If you have received this message in error, please
> immediately advise the sender by reply email and delete all copies.
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> WiX-devs mailing list
> WiX...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>

[WiX-devs] Issue Installing WiX 3.10 on Server with 4.5.2 DK Also Installed

[John C. <JoC...@ja...>]

I have been installing WiX 3.10 (plus my anti-race changes) on my four build servers.  On three of the four build servers, the install/upgrade is easy.  But on one build server, the only with 4.5.2 Developer's Kit, the bootstrapper fails immediately after the small "W" dialog appears.  The log has:

[11EC:297C][2015-07-07T08:57:46]i001: Burn v3.10.0.1907, Windows v6.3 (Build 9600: Service Pack 0), path: C:\Users\JoCooper\Desktop\WiX310.exe
[11EC:297C][2015-07-07T08:57:46]i000: Initializing string variable 'InstallFolder' to value '[ProgramFilesFolder]WiX Toolset v3.10'
[11EC:297C][2015-07-07T08:57:46]i009: Command Line: '-burn.unelevated BurnPipe.{6F85AB40-6D6B-4408-B308-4701CF5EE0CC} {2C5BB603-A24C-478C-A996-6FCADAF8CDB5} 5168'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\JoCooper\AppData\Local\Temp\WiX Toolset_v3.10.0.1907_20150707085746.log'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\JoCooper\Desktop\WiX310.exe'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\JoCooper\Desktop\'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleName' to value 'WiX Toolset v3.10.0.1907'
[11EC:297C][2015-07-07T08:57:46]i000: Setting string variable 'WixBundleManufacturer' to value 'Outercurve Foundation'
[11EC:297C][2015-07-07T08:57:46]i000: Loading managed bootstrapper application.
[11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to create the managed bootstrapper application.
[11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to create UX.
[11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed to load UX.
[11EC:297C][2015-07-07T08:57:46]e000: Error 0x8013141a: Failed while running
[11EC:297C][2015-07-07T08:57:47]i410: Variable: InstallFolder = C:\Program Files (x86)\WiX Toolset v3.10
[11EC:297C][2015-07-07T08:57:47]i410: Variable: ProgramFilesFolder = C:\Program Files (x86)\
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleAction = 5
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleElevated = 1
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleLog = C:\Users\JoCooper\AppData\Local\Temp\WiX Toolset_v3.10.0.1907_20150707085746.log
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleManufacturer = Outercurve Foundation
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleName = WiX Toolset v3.10.0.1907
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleOriginalSource = C:\Users\JoCooper\Desktop\WiX310.exe
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleOriginalSourceFolder = C:\Users\JoCooper\Desktop\
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleProviderKey = {42ba47c8-4aa9-42f7-9170-5b6152df5c73}
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleTag =
[11EC:297C][2015-07-07T08:57:47]i410: Variable: WixBundleVersion = 3.10.0.1907
[11EC:297C][2015-07-07T08:57:47]e000: Error 0x8013141a: Failed to run per-user mode.
[11EC:297C][2015-07-07T08:57:47]i007: Exit code: 0x8013141a, restarting: No

--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.(r) | Lenexa, KS  66214 | Ext:  431050 |JoC...@ja...<mailto:JoC...@ja...>

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

[WiX-devs] Marking WIPs as Complete

[Heath S. <Hea...@mi...>]

Rob,

>From our convo at https://github.com/wixtoolset/site/pull/53, you mentioned that WIPs can be completed. I take it that's just by way of checking the issue ID against the release. What about adding a Complete: true|false YAML header as well for quick identification?

Along the same lines, should I create feature at http://wixtoolset.org/issues to track all the docs I'll be importing and just have them reference the same number?

Heath Stewart
Software Engineer
Visual Studio Deployment Experience, Microsoft
http://blogs.msdn.com/heaths

Re: [WiX-devs] MPF: Adding a wixlib project reference to a solution

[Hoover, J. <Jac...@gr...>]

Yeah,
  I found another reference to it here: https://social.msdn.microsoft.com/Forums/vstudio/en-US/65e51ac9-5395-4cb6-8112-7b3c599a7773/projectreferencenode-in-mpf-requires-guids-on-project-references?forum=vsx

I wonder why one shouldn't just modify MPF to load the referenced project and ask MSBuild for the value of the metadata it needs.

From: Rob Mensching [mailto:ro...@fi...]
Sent: Wednesday, July 01, 2015 1:03 PM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] MPF: Adding a wixlib project reference to a solution

Ahh, yes. Sorry, known MPF issue. I have a bad habit of whacking the Project metadata from project references even though MPF based projects require it... because... well, MPF bugs me. <smile/>

_______________________________________________________________
FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

From: Hoover, Jacob [mailto:Jac...@gr...]
Sent: Wednesday, July 1, 2015 10:57 AM
To: WiX toolset developer mailing list
Subject: [WiX-devs] MPF: Adding a wixlib project reference to a solution

FYI,
  I've diagnosed the "issue" I found yesterday.  When referencing an external project via MPF, a <Project>{GUID}</Project> element is required.  When adding these via the IDE, it does populate them.  I wrote my extension using an existing one as a reference, which did not have them. The problem was the wixlib project had a reference to the C++ ca project.  When attempting to add the wixlib to the solution Votive/MPF parses for the ProjectReference elements and it requires the GUID to be set.

Thanks,
Jacob

Re: [WiX-devs] MPF: Adding a wixlib project reference to a solution

[Rob M. <ro...@fi...>]

Ahh, yes. Sorry, known MPF issue. I have a bad habit of whacking the Project metadata from project references even though MPF based projects require it... because... well, MPF bugs me. <smile/>

_______________________________________________________________
FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

From: Hoover, Jacob [mailto:Jac...@gr...]
Sent: Wednesday, July 1, 2015 10:57 AM
To: WiX toolset developer mailing list
Subject: [WiX-devs] MPF: Adding a wixlib project reference to a solution

FYI,
  I've diagnosed the "issue" I found yesterday.  When referencing an external project via MPF, a <Project>{GUID}</Project> element is required.  When adding these via the IDE, it does populate them.  I wrote my extension using an existing one as a reference, which did not have them. The problem was the wixlib project had a reference to the C++ ca project.  When attempting to add the wixlib to the solution Votive/MPF parses for the ProjectReference elements and it requires the GUID to be set.

Thanks,
Jacob

[WiX-devs] MPF: Adding a wixlib project reference to a solution

[Hoover, J. <Jac...@gr...>]

FYI,
  I've diagnosed the "issue" I found yesterday.  When referencing an external project via MPF, a <Project>{GUID}</Project> element is required.  When adding these via the IDE, it does populate them.  I wrote my extension using an existing one as a reference, which did not have them. The problem was the wixlib project had a reference to the C++ ca project.  When attempting to add the wixlib to the solution Votive/MPF parses for the ProjectReference elements and it requires the GUID to be set.

Thanks,
Jacob

Re: [WiX-devs] IniFieSearchEx: Reading from an arbitrary ini file

[Rob M. <ro...@fi...>]

I'd let Bob speak to v3.x but totally reasonable for v4.x. Not sure separate extension is the way to go or if it should get dumped in with all the Util stuff... but either way, seems more than reasonable.

_______________________________________________________________
FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

From: Hoover, Jacob [mailto:Jac...@gr...]
Sent: Monday, June 29, 2015 7:00 PM
To: WiX toolset developer mailing list
Subject: [WiX-devs] IniFieSearchEx: Reading from an arbitrary ini file

I'm a bit confused why IniFileSearch only allows for searching ini files in the Windows folder, yet IniFile allows to write INI files in any location.  I've written an extension in 3.10 which allows for an IniFileSearch and I was wondering if there would be any interest in adding the extension to the toolset.

Thanks,
Jacob

[WiX-devs] IniFieSearchEx: Reading from an arbitrary ini file

[Hoover, J. <Jac...@gr...>]

I'm a bit confused why IniFileSearch only allows for searching ini files in the Windows folder, yet IniFile allows to write INI files in any location.  I've written an extension in 3.10 which allows for an IniFileSearch and I was wondering if there would be any interest in adding the extension to the toolset.

Thanks,
Jacob

[WiX-devs] WiX Online Meeting #71

[Rob M. <ro...@fi...>]

Next WiX Online meeting will be: June 30th, 2015 @14:30 PST

Agenda items:

*       Triage

.........................................................................................................................................
--> Join Skype Meeting<https://meet.lync.com/firegiant/rob/3K7G71K5>


Help<http://go.microsoft.com/fwlink/?LinkId=389737>
[!OC([1033])!]
.........................................................................................................................................

[WiX-devs] No meeting today

[Bob A. <bo...@fi...>]

We don't have any new bugs to look at (just some old ones). WiX v3.10 RC build should come out today - stay tuned to blogs, Twitter, and http://wixtoolset.org/.

_______________________________________________________________
FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

[WiX-devs] WiX Online Meeting #70

[Rob M. <ro...@fi...>]

Next WiX Online meeting will be: June 16th, 2015 @14:30 PST

Agenda items:

*       Triage


.........................................................................................................................................
--> Join Skype Meeting<https://meet.lync.com/firegiant/rob/GS74G2TJ>



Help<http://go.microsoft.com/fwlink/?LinkId=389737>

[!OC([1033])!]
.........................................................................................................................................

[WiX-devs] Structuring Pull Request(s) for Bug 4791

[John C. <JoC...@ja...>]

I've got some working code I'm trying to break right now, so I'll be submitting pull requests as soon as testing is completed.

I think it may be desirable to divide up into multiple pull requests.  I would like to discuss/recommend breaking up my changes as follows:


1)      CompareFiles method in BinderFileManager.cs

2)      Adding a WixSharingViolationException

3)      LayoutMedia() in WixBinder.cs and MoveFIle() and CopyFile in BinderFileManager.cs

4)      (Optional) Add .NET Trace Logger Support to lit and light app.config files, etc.

--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.(r) | Lenexa, KS  66214 | Ext:  431050 |JoC...@ja...<mailto:JoC...@ja...>

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

[WiX-devs] WiX Online Meeting #69

[Rob M. <ro...@fi...>]

Next WiX Online meeting will be: June 9th, 2015 @14:30 PST

Agenda items:

*       Triage


.........................................................................................................................................
--> Join Skype Meeting<https://meet.lync.com/firegiant/rob/R6MF09T8>



Help<http://go.microsoft.com/fwlink/?LinkId=389737>

[!OC([1033])!]
.........................................................................................................................................

Re: [WiX-devs] WiX Working Group #68

[Phill H. <pho...@ri...>]

Thanks Sean.  I should have checked firegiant rather than googling directly
for the video feed.

Also thanks for all your work/support on SecureStrings.  So far it has been
very simple to implement my wpf mba (to get user input of a password for
service configuration) and pass it securely to the engine/msi without any
clear text/C# String objects.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Working-Group-68-tp7600511p7600517.html
Sent from the wix-devs mailing list archive at Nabble.com.

Re: [WiX-devs] WiX Working Group #68

[Sean H. <r.s...@gm...>]

https://www.firegiant.com/blog/2015/6/2/wix-online-meeting-68-highlights/

On Wed, Jun 3, 2015 at 8:30 AM, Phill Hogland <pho...@ri...> wrote:

> Is there a way that I can do a search of the wixtoolset Issues page and
> find
> those issues which were changed last evening after the #68 meeting?
>
> I appreciate that last evening's video is a best effort to recover from not
> being able to present a desktop, but since the untriaged bug list does not
> display the discussed issues anymore, and since the audio does not announce
> the issue number prior to discussing each issue (in many cases), would it
> be
> possible to post a list of which issue numbers were being discussed so that
> a person can follow the audio?
>
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Working-Group-68-tp7600511p7600514.html
> Sent from the wix-devs mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-devs mailing list
> WiX...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>

Re: [WiX-devs] WiX Working Group #68

[Phill H. <pho...@ri...>]

Is there a way that I can do a search of the wixtoolset Issues page and find
those issues which were changed last evening after the #68 meeting?

I appreciate that last evening's video is a best effort to recover from not
being able to present a desktop, but since the untriaged bug list does not
display the discussed issues anymore, and since the audio does not announce
the issue number prior to discussing each issue (in many cases), would it be
possible to post a list of which issue numbers were being discussed so that
a person can follow the audio?




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Working-Group-68-tp7600511p7600514.html
Sent from the wix-devs mailing list archive at Nabble.com.

[WiX-devs] WiX Working Group #68

[Rob M. <ro...@fi...>]

Next WiX Online meeting will be: June 2nd, 2015 @14:30 PST

Agenda items:

*       Triage


.........................................................................................................................................
--> Join Skype Meeting<https://meet.lync.com/firegiant/rob/5HR5272C>

Help<http://go.microsoft.com/fwlink/?LinkId=389737>

[!OC([1033])!]
.........................................................................................................................................

[WiX-devs] WITEMP directory can't be deleted after call on UpdateFilesInOneMediaDisk

[Flamme, D. <dav...@ru...>]

Dear WiX-Tools developers,

I just created  the issue http://wixtoolset.org/issues/4785/ which more or less reopens an older issue(referenced in the report).

It causes that temporary files created by WindowsInstaller.Package.InstallPackage.UpdateFilesInOneMediaDisk(..) can't be deleted after the method is finished. This is caused by the allocation of Record streamRec = new Record(1); in line 537.

Wrapping the allocation into a using block would solve that Issue.

I already got my Assignment Agreement and would like to get pull requests for v3.x and v4.x through into the reospitories.

With kind regards,
   David Flamme