You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
(72) |
May
(71) |
Jun
(30) |
Jul
(34) |
Aug
(52) |
Sep
(40) |
Oct
(72) |
Nov
(46) |
Dec
(93) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(67) |
Feb
(169) |
Mar
(147) |
Apr
(131) |
May
(169) |
Jun
(179) |
Jul
(292) |
Aug
(184) |
Sep
(212) |
Oct
(146) |
Nov
(138) |
Dec
(72) |
2006 |
Jan
(82) |
Feb
(183) |
Mar
(129) |
Apr
(237) |
May
(122) |
Jun
(125) |
Jul
(138) |
Aug
(173) |
Sep
(114) |
Oct
(251) |
Nov
(258) |
Dec
(212) |
2007 |
Jan
(270) |
Feb
(169) |
Mar
(179) |
Apr
(155) |
May
(159) |
Jun
(188) |
Jul
(225) |
Aug
(227) |
Sep
(146) |
Oct
(352) |
Nov
(145) |
Dec
(151) |
2008 |
Jan
(148) |
Feb
(147) |
Mar
(89) |
Apr
(426) |
May
(524) |
Jun
(4) |
Jul
(13) |
Aug
(11) |
Sep
(4) |
Oct
(23) |
Nov
(38) |
Dec
(28) |
2009 |
Jan
(48) |
Feb
(39) |
Mar
(30) |
Apr
(33) |
May
(28) |
Jun
(10) |
Jul
(4) |
Aug
(4) |
Sep
(7) |
Oct
(3) |
Nov
|
Dec
(27) |
2010 |
Jan
(11) |
Feb
(7) |
Mar
(15) |
Apr
(23) |
May
(41) |
Jun
(28) |
Jul
(27) |
Aug
(26) |
Sep
(38) |
Oct
(9) |
Nov
(14) |
Dec
(14) |
2011 |
Jan
(21) |
Feb
(7) |
Mar
(5) |
Apr
(9) |
May
(4) |
Jun
(11) |
Jul
(8) |
Aug
(10) |
Sep
(11) |
Oct
(9) |
Nov
(14) |
Dec
(1) |
2012 |
Jan
(27) |
Feb
(2) |
Mar
(1) |
Apr
(26) |
May
(23) |
Jun
(2) |
Jul
(17) |
Aug
(7) |
Sep
(5) |
Oct
(22) |
Nov
(33) |
Dec
(6) |
2013 |
Jan
(92) |
Feb
(119) |
Mar
(123) |
Apr
(90) |
May
(87) |
Jun
(58) |
Jul
(71) |
Aug
(88) |
Sep
(82) |
Oct
(152) |
Nov
(148) |
Dec
(77) |
2014 |
Jan
(130) |
Feb
(154) |
Mar
(108) |
Apr
(78) |
May
(104) |
Jun
(101) |
Jul
(156) |
Aug
(57) |
Sep
(51) |
Oct
(107) |
Nov
(130) |
Dec
(52) |
2015 |
Jan
(72) |
Feb
(20) |
Mar
(53) |
Apr
(38) |
May
(18) |
Jun
(13) |
Jul
(29) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
2022 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: SourceForge.net <no...@so...> - 2020-05-02 11:29:00
|
***************************************************************** Please confirm your subscription to wix-devs. ***************************************************************** Thank you for your interest in the wix-devs mailing list. We just need you to confirm that you made this request by clicking on the link below: https://sourceforge.net/projects/wix/lists/confirm?hash=e9598ec5-5a6b-47e2-98cb-4637a1c8793e By confirming your subscription, you are agreeing to the Terms of Service and the Privacy Policy: https://slashdotmedia.com/terms-of-use/ https://slashdotmedia.com/privacy-statement/ If you received this e-mail in error, feel free to simply delete it. Our apologies. ------------------------------------------------------------ Why do I need to confirm? ------------------------------------------------------------ If you're anything like us, it's probably safe to say that you hate spam. To ensure that you, and only you, requested updates, we ask that you confirm each subscription. ***************************************************************** This e-mail was intended for: wix...@li... Privacy policy: https://slashdotmedia.com/privacy-statement/ PO BOX 2452, La Jolla, CA 92038 |
From: johnpremi <joh...@li...> - 2018-06-26 03:28:41
|
Hi there I have used dark to decompile the installshield MSI and few observations I would like to bring forth here are that, deprecated APIs for XML generation prevents straightforward migration which is understandable. But the shortcuts don't get created if the shortcuts were created for USER PROFILE. Please let me know how to tweak that. regards JOhn -- Sent from: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-devs-f687561.html |
From: Rob M. <ro...@fi...> - 2018-06-07 21:12:03
|
This mailing list address is very dead. See the correct locations for the mailing lists at: http://wixtoolset.org/documentation/ Regards, Rob Mensching CEO FireGiant _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -----Original Message----- From: johnpremi <joh...@li...> Sent: Thursday, June 7, 2018 2:24 AM To: wix...@li... Subject: [wix-devs] (deprecated) Dark.exe has few deprecated tables Hi there I am migrating few Installshield projects into WiX and using a custom utility by making use of dark, candle and light. When Dark is decompling the tables it ignores few tables and also there are some deprecated components as well when dark is used. Is there a way to fix these issues in the decompliation process. Orca is what someone suggested we could use but I am not sure how? can some one please enlighten me what is the right approach to get the tables migrated into a WxS XML format, your help would be greatly appreciated. regards John -- Sent from: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-devs-f687561.html ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ WiX-devs mailing list WiX...@li... https://lists.sourceforge.net/lists/listinfo/wix-devs |
From: johnpremi <joh...@li...> - 2018-06-07 09:23:58
|
Hi there I am migrating few Installshield projects into WiX and using a custom utility by making use of dark, candle and light. When Dark is decompling the tables it ignores few tables and also there are some deprecated components as well when dark is used. Is there a way to fix these issues in the decompliation process. Orca is what someone suggested we could use but I am not sure how? can some one please enlighten me what is the right approach to get the tables migrated into a WxS XML format, your help would be greatly appreciated. regards John -- Sent from: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-devs-f687561.html |
From: Rob M. <ro...@fi...> - 2017-12-27 08:26:40
|
This mailing list is deprecated. Please see: http://wixtoolset.org/documentation/ for updated list of mailing lists. From: Manimala Kottha [mailto:man...@gm...] Sent: Tuesday, December 26, 2017 11:23 PM To: wix...@li... Subject: [wix-devs] (deprecated) Need help in Wix Bootstrpper Bundle project. Hi All, I am new to Wix and Wix bootstrapper concepts. In one of requirements, we need to use Wix bootstrapper. Currently the bootstrapper project installs 4 packages.(pacakge 1,package2,package3,package4). Requirement is when user stops the installation at step 2(while installing the pacakge 2), package 4 still needs to be installed.(Always irrespective of other packages installation success or fail). Could you please suggest how to perform this action? Thanks, Mani |
From: Manimala K. <man...@gm...> - 2017-12-27 07:23:19
|
Hi All, I am new to Wix and Wix bootstrapper concepts. In one of requirements, we need to use Wix bootstrapper. Currently the bootstrapper project installs 4 packages.(pacakge 1,package2,package3,package4). Requirement is when user stops the installation at step 2(while installing the pacakge 2), package 4 still needs to be installed.(Always irrespective of other packages installation success or fail). Could you please suggest how to perform this action? Thanks, Mani |
From: Bruce C. <br...@cr...> - 2015-12-19 20:52:34
|
On 12/19/15 1:07 PM, Nicolás Alvarez wrote: > 2015-12-18 16:44 GMT-03:00 Hoover, Jacob <Jac...@gr...>: >> Did Rob mess up the date in the last mail, or did I miss the meeting >> yesterday? (I ask because #92 isn't yet posted online.) >> >> ------------------------------------------------------------------------------ > > Isn't this the wrong mailing list? I see "(deprecated)" in the topic. Oh, so that's why I haven't been getting any WiX emails! Yes, according to http://wixtoolset.org/documentation/mailinglist/ the mailing lists have moved from lists.sourceforge.net to lists.wixtoolset.org. -- Bruce |
From: Nicolás A. <nic...@gm...> - 2015-12-19 20:08:19
|
2015-12-18 16:44 GMT-03:00 Hoover, Jacob <Jac...@gr...>: > Did Rob mess up the date in the last mail, or did I miss the meeting > yesterday? (I ask because #92 isn't yet posted online.) > > ------------------------------------------------------------------------------ Isn't this the wrong mailing list? I see "(deprecated)" in the topic. -- Nicolás |
From: Hoover, J. <Jac...@gr...> - 2015-12-18 19:57:11
|
Did Rob mess up the date in the last mail, or did I miss the meeting yesterday? (I ask because #92 isn't yet posted online.) |
From: Alessandro P. <api...@cl...> - 2015-07-27 12:07:23
|
Hi guys, Thanks for the replies! CAs only would be great for now, if we can get that to compile on x64 it’d be more tha enough. The toolset can still be x86 for quite some time IMO. More or less related: is there any discussion or plan to create a completely new toolset for NanoServer packages (aka life after MSI)? Alessandro On 16 Jul 2015, at 19:33, Bob Arnson <bo...@fi...<mailto:bo...@fi...>> wrote: CAs only or CAs+everything else? _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: Rob Mensching [mailto:ro...@fi...] Sent: Thursday, 16 July, 2015 12:19 To: WiX toolset developer mailing list <wix...@li...<mailto:wix...@li...>> Subject: Re: [WiX-devs] x64 extensions binaries for Windows Server 2016 without WoW64 This is just work (mostly build system work at that). It should be done. Just need someone to step up. <smile/> _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: Blair Murri [mailto:os...@li...] Sent: Thursday, July 16, 2015 12:55 AM To: wix...@li...<mailto:wix...@li...> Subject: Re: [WiX-devs] x64 extensions binaries for Windows Server 2016 without WoW64 The ability to remove WoW64 has been there since Server 2008. Almost nobody removes it, since almost all workloads seem to require it (at least on some level). In theory all of the current code should be able to be built 64-only (probably with some proj file changes), but some of the system DLLs that the packaging-time tools (light, etc) make use of are only supplied by MSFT in 32-bit form (even on 64-bit platforms), so creating MSIs requires the build machines, if 64-bit, to have WoW64 installed. Sent from Windows Mail From: Alessandro Pilotti<mailto:api...@cl...> Sent: Sunday, July 12, 2015 4:45 AM To: wix...@li...<mailto:wix...@li...> Hi guys, Being this is my first email to the ML, let me start with a big thank you for your great work developing and maintaining the WiX toolset! The upcoming Windows Server 2016 (Threshold) provides the option to avoid deploying the WoW64 32 bit subsystem, meaning that any x86 exe / dll won’t work. To remove WoW64 from e.g. a TP2 installation: Remove-WindowsFeature WoW64-Support WiX extension DLLs (WixUIExtension, WixUtilExtension, etc) are provided in x86 form only in binary downloads, meaning that any attempt to deploy an MSI that uses any of them in the above use case will fail. Do you guys plan to package x64 versions as well in upcoming releases? For Wix 3.9, is there a way to build the extensions targeting x64 skipping the rest of the WiX build? Thanks! Alessandro ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ 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 |
From: Rob M. <ro...@fi...> - 2015-07-22 16:43:22
|
This mailing list has moved. Please sign up for the wix...@li... mailing list. More information can be found here: https://www.firegiant.com/blog/2015/7/21/new-wix-mailing-lists/ |
From: Rob M. <ro...@fi...> - 2015-07-21 22:26:26
|
Next WiX Online meeting will be: July 20th, 2015 @14:30 PST Agenda items: * Triage ......................................................................................................................................... --> Join Skype Meeting<https://meet.lync.com/firegiant/rob/16SMN5ZW> This is an online meeting for Skype for Business, the professional meetings and communications app formerly known as Lync. Help<http://go.microsoft.com/fwlink/?LinkId=389737> [!OC([1033])!] ......................................................................................................................................... |
From: Bob A. <bo...@fi...> - 2015-07-16 16:34:44
|
CAs only or CAs+everything else? _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: Rob Mensching [mailto:ro...@fi...] Sent: Thursday, 16 July, 2015 12:19 To: WiX toolset developer mailing list <wix...@li...> Subject: Re: [WiX-devs] x64 extensions binaries for Windows Server 2016 without WoW64 This is just work (mostly build system work at that). It should be done. Just need someone to step up. <smile/> _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: Blair Murri [mailto:os...@li...] Sent: Thursday, July 16, 2015 12:55 AM To: wix...@li...<mailto:wix...@li...> Subject: Re: [WiX-devs] x64 extensions binaries for Windows Server 2016 without WoW64 The ability to remove WoW64 has been there since Server 2008. Almost nobody removes it, since almost all workloads seem to require it (at least on some level). In theory all of the current code should be able to be built 64-only (probably with some proj file changes), but some of the system DLLs that the packaging-time tools (light, etc) make use of are only supplied by MSFT in 32-bit form (even on 64-bit platforms), so creating MSIs requires the build machines, if 64-bit, to have WoW64 installed. Sent from Windows Mail From: Alessandro Pilotti<mailto:api...@cl...> Sent: Sunday, July 12, 2015 4:45 AM To: wix...@li...<mailto:wix...@li...> Hi guys, Being this is my first email to the ML, let me start with a big thank you for your great work developing and maintaining the WiX toolset! The upcoming Windows Server 2016 (Threshold) provides the option to avoid deploying the WoW64 32 bit subsystem, meaning that any x86 exe / dll won’t work. To remove WoW64 from e.g. a TP2 installation: Remove-WindowsFeature WoW64-Support WiX extension DLLs (WixUIExtension, WixUtilExtension, etc) are provided in x86 form only in binary downloads, meaning that any attempt to deploy an MSI that uses any of them in the above use case will fail. Do you guys plan to package x64 versions as well in upcoming releases? For Wix 3.9, is there a way to build the extensions targeting x64 skipping the rest of the WiX build? Thanks! Alessandro ------------------------------------------------------------------------------ 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 |
From: Rob M. <ro...@fi...> - 2015-07-16 16:19:45
|
This is just work (mostly build system work at that). It should be done. Just need someone to step up. <smile/> _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: Blair Murri [mailto:os...@li...] Sent: Thursday, July 16, 2015 12:55 AM To: wix...@li... Subject: Re: [WiX-devs] x64 extensions binaries for Windows Server 2016 without WoW64 The ability to remove WoW64 has been there since Server 2008. Almost nobody removes it, since almost all workloads seem to require it (at least on some level). In theory all of the current code should be able to be built 64-only (probably with some proj file changes), but some of the system DLLs that the packaging-time tools (light, etc) make use of are only supplied by MSFT in 32-bit form (even on 64-bit platforms), so creating MSIs requires the build machines, if 64-bit, to have WoW64 installed. Sent from Windows Mail From: Alessandro Pilotti<mailto:api...@cl...> Sent: Sunday, July 12, 2015 4:45 AM To: wix...@li...<mailto:wix...@li...> Hi guys, Being this is my first email to the ML, let me start with a big thank you for your great work developing and maintaining the WiX toolset! The upcoming Windows Server 2016 (Threshold) provides the option to avoid deploying the WoW64 32 bit subsystem, meaning that any x86 exe / dll won’t work. To remove WoW64 from e.g. a TP2 installation: Remove-WindowsFeature WoW64-Support WiX extension DLLs (WixUIExtension, WixUtilExtension, etc) are provided in x86 form only in binary downloads, meaning that any attempt to deploy an MSI that uses any of them in the above use case will fail. Do you guys plan to package x64 versions as well in upcoming releases? For Wix 3.9, is there a way to build the extensions targeting x64 skipping the rest of the WiX build? Thanks! Alessandro ------------------------------------------------------------------------------ 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 |
From: Blair M. <os...@li...> - 2015-07-16 08:00:01
|
The ability to remove WoW64 has been there since Server 2008. Almost nobody removes it, since almost all workloads seem to require it (at least on some level). In theory all of the current code should be able to be built 64-only (probably with some proj file changes), but some of the system DLLs that the packaging-time tools (light, etc) make use of are only supplied by MSFT in 32-bit form (even on 64-bit platforms), so creating MSIs requires the build machines, if 64-bit, to have WoW64 installed. Sent from Windows Mail From: Alessandro Pilotti Sent: Sunday, July 12, 2015 4:45 AM To: wix...@li... Hi guys, Being this is my first email to the ML, let me start with a big thank you for your great work developing and maintaining the WiX toolset! The upcoming Windows Server 2016 (Threshold) provides the option to avoid deploying the WoW64 32 bit subsystem, meaning that any x86 exe / dll won’t work. To remove WoW64 from e.g. a TP2 installation: Remove-WindowsFeature WoW64-Support WiX extension DLLs (WixUIExtension, WixUtilExtension, etc) are provided in x86 form only in binary downloads, meaning that any attempt to deploy an MSI that uses any of them in the above use case will fail. Do you guys plan to package x64 versions as well in upcoming releases? For Wix 3.9, is there a way to build the extensions targeting x64 skipping the rest of the WiX build? Thanks! Alessandro ------------------------------------------------------------------------------ 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 |
From: Rob M. <ro...@fi...> - 2015-07-14 18:19:55
|
Next WiX Online meeting will be: July 14th, 2015 @14:30 PST Agenda items: * Triage * New Logo Proposals ......................................................................................................................................... --> Join Skype Meeting<https://meet.lync.com/firegiant/rob/MGWPY6P0> This is an online meeting for Skype for Business, the professional meetings and communications app formerly known as Lync. Help<http://go.microsoft.com/fwlink/?LinkId=389737> [!OC([1033])!] ......................................................................................................................................... |
From: Rob M. <ro...@fi...> - 2015-07-13 05:48:58
|
We've known this has been coming and waiting for it to hit priority. A 64-bit Burn will be needed as well. Probably something for someone to do for v4.0 and, probably, v3.11. It isn't as easy as just building 64-bit DLLs. _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -----Original Message----- From: Alessandro Pilotti [mailto:api...@cl...] Sent: Sunday, July 12, 2015 4:40 AM To: WiX toolset developer mailing list Subject: [WiX-devs] x64 extensions binaries for Windows Server 2016 without WoW64 Hi guys, Being this is my first email to the ML, let me start with a big thank you for your great work developing and maintaining the WiX toolset! The upcoming Windows Server 2016 (Threshold) provides the option to avoid deploying the WoW64 32 bit subsystem, meaning that any x86 exe / dll won’t work. To remove WoW64 from e.g. a TP2 installation: Remove-WindowsFeature WoW64-Support WiX extension DLLs (WixUIExtension, WixUtilExtension, etc) are provided in x86 form only in binary downloads, meaning that any attempt to deploy an MSI that uses any of them in the above use case will fail. Do you guys plan to package x64 versions as well in upcoming releases? For Wix 3.9, is there a way to build the extensions targeting x64 skipping the rest of the WiX build? Thanks! Alessandro ------------------------------------------------------------------------------ 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 |
From: John C. <JoC...@ja...> - 2015-07-12 12:35:07
|
Found it. I was using the "Developer Command Prompt for VS 2015." It looks like some of the settings in there are still specific to .NET Framework 4.5.1. I switched to the "MSBuild Command Prompt for VS 2015" and, although SHFB gives me a fat warning, everything builds. -- 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: John Cooper Sent: Sunday, July 12, 2015 7:16 AM To: WiX toolset developer mailing list Subject: Re: [WiX-devs] Problem Building a Signed WiX 3.10 Build The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Ok, uninstalled Sandcastle and insured that %SHFBROOT% was undefined. even smoked the NuGet package in the package directory so it would be reinstalled just to make sure. Good news: BE0032 is gone. Bad news is that it is replaced by a BE0071: "c:\git\wix3-jmc\wix.proj" (default target) (1) -> "c:\git\wix3-jmc\src\dtf\dtf.proj" (default target) (14) -> "c:\git\wix3-jmc\src\dtf\Documents\Guide\dtfguide.helpproj" (default target) (39) -> "c:\git\wix3-jmc\src\dtf\Documents\Reference\dtfref.shfbproj" (default target) (40) -> (CoreBuildHelp target) -> SHFB : error BE0071: Unable to locate information for the project framework version 'v4.0.30319' or a suitable redirected version on this system. See error number help topic for details. [c:\git\wix3-jmc\src\dtf\Documents\Reference\dtfref.shfbproj] 1 Warning(s) 1 Error(s) -- 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: Rob Mensching [ro...@fi...] Sent: Sunday, July 12, 2015 3:13 AM To: WiX toolset developer mailing list Subject: Re: [WiX-devs] Problem Building a Signed WiX 3.10 Build The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Try uninstalling Sandcastle and make sure all of its environment variables are removed from your build cmd prompt. _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: John Cooper [mailto:JoC...@ja...] Sent: Saturday, July 11, 2015 10:22 PM To: WiX toolset developer mailing list (wix...@li...) Subject: Re: [WiX-devs] Problem Building a Signed WiX 3.10 Build Well, I’ve learned somethings. There is a .NETFramework 4.5.3 section in the Frameworks.xml file of both the package and the Sandcastle I installed. However, both 4.5.3 sections have a bug in them that keeps them from being useful for making an otherwise suitable template for .NETFramework 4.6: The FSharp.Core assembly has a typo in it’s AssemblyVersion field—it has a ‘,’ (comma) where it should have a ‘.’ (period). Replacing that allowed me to make a suitable section. I checked using ILDASM, and the AssemblyVersions and PublicKeys all look right. But even after regeneration, and tweaking the .NETFramework.config file, I can’t make the BE0032 go away. Also tried with the NuGet Package—same issue. I can regenerate, but I can’t make BE0032 go away. For now, I’m just suppressing Sandcastle documentation. -- 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: John Cooper Sent: Saturday, July 11, 2015 8:58 PM To: WiX toolset developer mailing list (wix...@li...<mailto:wix...@li...>) Subject: Problem Building a Signed WiX 3.10 Build 1) My first attempt gave me a cryptic error about not being able to determine the Framework in src\dtf\Documents\Reference\dtfref.shfbproj. After a little rummaging, it seemed it might me helpful to install the latest SandCastle on my WiX build machine, so I did. 2) Now, there is less red, but I am left with how to solve: SHFB : error BE0032. Reflection data files do not exist yet [D:\git\wix3-jmc\src\\dtf\Documents\Reference\dtfref.shfbproj] This actually makes sense because, with VS 2015 RC CTP 6 installed, I also have .NET 4.6 RC. Looking at the files in SandCastle, it appears the last version it has reflection data for is .NET 4.5.1. I think there’s a way to redirect Sandcastle, but I’m not currently familiar enough with the product—something that will probably change. Installed: VS 2010 VS 2010 SDK VS 2012 VS 2012 SDK VS 2013 VS 2013 SDK VS 2015 VS 2015 SDK Sandcastle Help File Builder 15.1.12.0. Anybody know how to fix this? -- 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. 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. 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. |
From: John C. <JoC...@ja...> - 2015-07-12 12:16:44
|
Ok, uninstalled Sandcastle and insured that %SHFBROOT% was undefined. even smoked the NuGet package in the package directory so it would be reinstalled just to make sure. Good news: BE0032 is gone. Bad news is that it is replaced by a BE0071: "c:\git\wix3-jmc\wix.proj" (default target) (1) -> "c:\git\wix3-jmc\src\dtf\dtf.proj" (default target) (14) -> "c:\git\wix3-jmc\src\dtf\Documents\Guide\dtfguide.helpproj" (default target) (39) -> "c:\git\wix3-jmc\src\dtf\Documents\Reference\dtfref.shfbproj" (default target) (40) -> (CoreBuildHelp target) -> SHFB : error BE0071: Unable to locate information for the project framework version 'v4.0.30319' or a suitable redirected version on this system. See error number help topic for details. [c:\git\wix3-jmc\src\dtf\Documents\Reference\dtfref.shfbproj] 1 Warning(s) 1 Error(s) -- 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: Rob Mensching [ro...@fi...] Sent: Sunday, July 12, 2015 3:13 AM To: WiX toolset developer mailing list Subject: Re: [WiX-devs] Problem Building a Signed WiX 3.10 Build The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Try uninstalling Sandcastle and make sure all of its environment variables are removed from your build cmd prompt. _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: John Cooper [mailto:JoC...@ja...] Sent: Saturday, July 11, 2015 10:22 PM To: WiX toolset developer mailing list (wix...@li...) Subject: Re: [WiX-devs] Problem Building a Signed WiX 3.10 Build Well, I’ve learned somethings. There is a .NETFramework 4.5.3 section in the Frameworks.xml file of both the package and the Sandcastle I installed. However, both 4.5.3 sections have a bug in them that keeps them from being useful for making an otherwise suitable template for .NETFramework 4.6: The FSharp.Core assembly has a typo in it’s AssemblyVersion field—it has a ‘,’ (comma) where it should have a ‘.’ (period). Replacing that allowed me to make a suitable section. I checked using ILDASM, and the AssemblyVersions and PublicKeys all look right. But even after regeneration, and tweaking the .NETFramework.config file, I can’t make the BE0032 go away. Also tried with the NuGet Package—same issue. I can regenerate, but I can’t make BE0032 go away. For now, I’m just suppressing Sandcastle documentation. -- 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: John Cooper Sent: Saturday, July 11, 2015 8:58 PM To: WiX toolset developer mailing list (wix...@li...<mailto:wix...@li...>) Subject: Problem Building a Signed WiX 3.10 Build 1) My first attempt gave me a cryptic error about not being able to determine the Framework in src\dtf\Documents\Reference\dtfref.shfbproj. After a little rummaging, it seemed it might me helpful to install the latest SandCastle on my WiX build machine, so I did. 2) Now, there is less red, but I am left with how to solve: SHFB : error BE0032. Reflection data files do not exist yet [D:\git\wix3-jmc\src\\dtf\Documents\Reference\dtfref.shfbproj] This actually makes sense because, with VS 2015 RC CTP 6 installed, I also have .NET 4.6 RC. Looking at the files in SandCastle, it appears the last version it has reflection data for is .NET 4.5.1. I think there’s a way to redirect Sandcastle, but I’m not currently familiar enough with the product—something that will probably change. Installed: VS 2010 VS 2010 SDK VS 2012 VS 2012 SDK VS 2013 VS 2013 SDK VS 2015 VS 2015 SDK Sandcastle Help File Builder 15.1.12.0. Anybody know how to fix this? -- 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. 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. |
From: Alessandro P. <api...@cl...> - 2015-07-12 11:40:44
|
Hi guys, Being this is my first email to the ML, let me start with a big thank you for your great work developing and maintaining the WiX toolset! The upcoming Windows Server 2016 (Threshold) provides the option to avoid deploying the WoW64 32 bit subsystem, meaning that any x86 exe / dll won’t work. To remove WoW64 from e.g. a TP2 installation: Remove-WindowsFeature WoW64-Support WiX extension DLLs (WixUIExtension, WixUtilExtension, etc) are provided in x86 form only in binary downloads, meaning that any attempt to deploy an MSI that uses any of them in the above use case will fail. Do you guys plan to package x64 versions as well in upcoming releases? For Wix 3.9, is there a way to build the extensions targeting x64 skipping the rest of the WiX build? Thanks! Alessandro |
From: Rob M. <ro...@fi...> - 2015-07-12 08:13:51
|
Try uninstalling Sandcastle and make sure all of its environment variables are removed from your build cmd prompt. _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: John Cooper [mailto:JoC...@ja...] Sent: Saturday, July 11, 2015 10:22 PM To: WiX toolset developer mailing list (wix...@li...) Subject: Re: [WiX-devs] Problem Building a Signed WiX 3.10 Build Well, I've learned somethings. There is a .NETFramework 4.5.3 section in the Frameworks.xml file of both the package and the Sandcastle I installed. However, both 4.5.3 sections have a bug in them that keeps them from being useful for making an otherwise suitable template for .NETFramework 4.6: The FSharp.Core assembly has a typo in it's AssemblyVersion field-it has a ',' (comma) where it should have a '.' (period). Replacing that allowed me to make a suitable section. I checked using ILDASM, and the AssemblyVersions and PublicKeys all look right. But even after regeneration, and tweaking the .NETFramework.config file, I can't make the BE0032 go away. Also tried with the NuGet Package-same issue. I can regenerate, but I can't make BE0032 go away. For now, I'm just suppressing Sandcastle documentation. -- 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...> From: John Cooper Sent: Saturday, July 11, 2015 8:58 PM To: WiX toolset developer mailing list (wix...@li...<mailto:wix...@li...>) Subject: Problem Building a Signed WiX 3.10 Build 1) My first attempt gave me a cryptic error about not being able to determine the Framework in src\dtf\Documents\Reference\dtfref.shfbproj. After a little rummaging, it seemed it might me helpful to install the latest SandCastle on my WiX build machine, so I did. 2) Now, there is less red, but I am left with how to solve: SHFB : error BE0032. Reflection data files do not exist yet [D:\git\wix3-jmc\src\\dtf\Documents\Reference\dtfref.shfbproj] This actually makes sense because, with VS 2015 RC CTP 6 installed, I also have .NET 4.6 RC. Looking at the files in SandCastle, it appears the last version it has reflection data for is .NET 4.5.1. I think there's a way to redirect Sandcastle, but I'm not currently familiar enough with the product-something that will probably change. Installed: VS 2010 VS 2010 SDK VS 2012 VS 2012 SDK VS 2013 VS 2013 SDK VS 2015 VS 2015 SDK Sandcastle Help File Builder 15.1.12.0. Anybody know how to fix this? -- 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. |
From: John C. <JoC...@ja...> - 2015-07-12 05:22:29
|
Well, I've learned somethings. There is a .NETFramework 4.5.3 section in the Frameworks.xml file of both the package and the Sandcastle I installed. However, both 4.5.3 sections have a bug in them that keeps them from being useful for making an otherwise suitable template for .NETFramework 4.6: The FSharp.Core assembly has a typo in it's AssemblyVersion field-it has a ',' (comma) where it should have a '.' (period). Replacing that allowed me to make a suitable section. I checked using ILDASM, and the AssemblyVersions and PublicKeys all look right. But even after regeneration, and tweaking the .NETFramework.config file, I can't make the BE0032 go away. Also tried with the NuGet Package-same issue. I can regenerate, but I can't make BE0032 go away. For now, I'm just suppressing Sandcastle documentation. -- 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...> From: John Cooper Sent: Saturday, July 11, 2015 8:58 PM To: WiX toolset developer mailing list (wix...@li...) Subject: Problem Building a Signed WiX 3.10 Build 1) My first attempt gave me a cryptic error about not being able to determine the Framework in src\dtf\Documents\Reference\dtfref.shfbproj. After a little rummaging, it seemed it might me helpful to install the latest SandCastle on my WiX build machine, so I did. 2) Now, there is less red, but I am left with how to solve: SHFB : error BE0032. Reflection data files do not exist yet [D:\git\wix3-jmc\src\\dtf\Documents\Reference\dtfref.shfbproj] This actually makes sense because, with VS 2015 RC CTP 6 installed, I also have .NET 4.6 RC. Looking at the files in SandCastle, it appears the last version it has reflection data for is .NET 4.5.1. I think there's a way to redirect Sandcastle, but I'm not currently familiar enough with the product-something that will probably change. Installed: VS 2010 VS 2010 SDK VS 2012 VS 2012 SDK VS 2013 VS 2013 SDK VS 2015 VS 2015 SDK Sandcastle Help File Builder 15.1.12.0. Anybody know how to fix this? -- 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. |
From: John C. <JoC...@ja...> - 2015-07-12 01:58:38
|
1) My first attempt gave me a cryptic error about not being able to determine the Framework in src\dtf\Documents\Reference\dtfref.shfbproj. After a little rummaging, it seemed it might me helpful to install the latest SandCastle on my WiX build machine, so I did. 2) Now, there is less red, but I am left with how to solve: SHFB : error BE0032. Reflection data files do not exist yet [D:\git\wix3-jmc\src\\dtf\Documents\Reference\dtfref.shfbproj] This actually makes sense because, with VS 2015 RC CTP 6 installed, I also have .NET 4.6 RC. Looking at the files in SandCastle, it appears the last version it has reflection data for is .NET 4.5.1. I think there's a way to redirect Sandcastle, but I'm not currently familiar enough with the product-something that will probably change. Installed: VS 2010 VS 2010 SDK VS 2012 VS 2012 SDK VS 2013 VS 2013 SDK VS 2015 VS 2015 SDK Sandcastle Help File Builder 15.1.12.0. Anybody know how to fix this? -- 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. |
From: Brian D. <bri...@ou...> - 2015-07-09 03:30:04
|
Hi all, This may sound like a silly question, but I'm trying to get started on working against some of the bugs list. I'm looking at the source code for the UpdateMediaOnOneDisk method (InstallPackage class), and the intellisense isn't working for some of the types. It's also not allowing me to view the definition. Is it just that the document cache hasn't been built yet? System details are Windows 8.1 Pro, and Visual Studio Professional 2013. Has anyone else experienced this problem before? Sorry if this is a bit of a newbie question. If there's a place that would be better suited for this sort of thing, please point me in the right direction. Regards, Brian |
From: Heath S. <Hea...@mi...> - 2015-07-09 00:45:42
|
That relies on the person deciding to merge the PR to not do so until after a certain date, while a branch that people base on would seem to help make that easier and less prone to mistakes, not to mention people can start piling on each other's commit history if they would happen to pull dependent work. It's a fairly common Git workflow when you have multiple trains. Heath Stewart Software Engineer Visual Studio Deployment Experience, Microsoft http://blogs.msdn.com/heaths From: Rob Mensching [mailto:ro...@fi...] Sent: Wednesday, July 8, 2015 4:34 PM To: WiX toolset developer mailing list <wix...@li...> Subject: Re: [WiX-devs] New branch for wix311? 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 |