Re: [WiX-users] wix mailing lists open to public = more spam
Rob: Signing up for a forum or mailing list is commonplace these days, and a trivial one-time inconvenience. If someone can't figure out how to join a mailing list, they're probably not going to have much success with Wix (or any type of programming for that matter). PLEASE require people to sign up for this list. I think you'd be hard pressed to find any list these days that doesn't require it. -- Don - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix mailing lists open to public = more spam
Rob: I've had a number of people suggest that finding the signup page via SourceForge is very painful. SourceForge is painful, period g. I signed up for this list because the SF interface to the list is absolutely horrible. Wix is free and the support graciously provided by you and others is free. A one-time signup isn't all that much to ask for all that in return, And it's a small price to pay to keep spam out of the list, where every last member has to waste time deleting it. -- Don - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Did WiX V3 projects break compatibility with earlier builds?
Scott: MPF stands for 'Managed Package Framework', an incomplete and buggy framework for building project systems that integrate into Visual Studio. It's part of the Visual Studio SDK. Consider yourself lucky that you don't have to deal with it. Don From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer Sent: Wednesday, May 14, 2008 9:43 PM To: Justin Rockwood Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Did WiX V3 projects break compatibility with earlier builds? It seems the real bug then is that there are two code paths... VB/C/C++ should be implemented via the MPF stuff as well... then this never would have happened. I say this still not knowing what MPF stands for or anything about it though. Scott On 14-May-08, at 10:45 AM, Justin Rockwood wrote: No, other projects that are not based on the MPF (which includes VB/C#/C++) do not lock because they do not have that bug. However, projects that are based on the MPF (IronPython, if I remember correctly) do exhibit the same bug that WiX has. This bug, in my mind, is one of the most annoying ones that should have higher priority (along with the other one that you pointed out - same line output). Thanks for the bug reports! Justin From: Scott Palmer Sent: Wednesday, May 14, 2008 7:14 AM To: Justin Rockwood Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Did WiX V3 projects break compatibility with earlier builds? On Tue, May 13, 2008 at 7:05 PM, Justin Rockwood wrote: I hate the locking as well. Unfortunately, this is a bug in the MPF (the Visual Studio SDK) that they have not fixed yet. We will have to just fix it on our own instead of waiting for a fix from them. Note that it's not a trivial fix either because it requires a separate thread to do the build. Are you saying that other tasks like compiling and linking C/C++ code lock things the same way.. but I assume for short enough periods of time that it isn't noticeable? I'm just wondering why I only notice this with WiX projects. ... - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integrating documentation with Visual Studio 2008
You mean there's actually a Html Help team? Wonder what they've been doing for the past 10 or 11 years? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Thursday, May 08, 2008 6:35 PM To: Don Caton; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Integrating documentation with Visual Studio 2008 Yeah, we've sent this type of feedback to the Html Help team before. Unfortunately, we (people who work on WiX) don't have control over the quality of the merge module. I'll send this one along again (just in case anyone over there thought things were good enough). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Caton Sent: Thursday, May 08, 2008 15:05 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Integrating documentation with Visual Studio 2008 Doug: I wasted days and days on this but was never able to get any of that to work, even in VS2005. The Wix docs for the tags in question are not helpful, and I couldn't find any examples on the web. Just questions, and a reference to a wix bug that may or may not be fixed (the sourceforge page for that bug id returns a blank page). If you want to save yourself a ton of grief, check out Helpware's H2Reg utility (www.helpware.net). I include this little exe in our installer and launch it from a custom action after I run devenv/setup. It works great. I think it's free for individual use, but the site license was inexpensive, and far less than the time I wasted trying to get it to work in Wix. -- Don From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Payne Sent: Thursday, May 08, 2008 2:20 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Integrating documentation with Visual Studio 2008 I am trying to integrate documentation for my product into the VS 2008 documentation, using HTML_Help_Registration__RTL_---_---.msm and VSIPCC_Collection_Files_RTL_---_---.msm included in the VS 2008 SDK. Has anyone successfully accomplished this? What changes did you make to the html help merge module to get it to work? I encounter an unexpected error while merging. The merge log includes the following: Merging Sequence Table: ModuleInstallExecuteSequence into Database Table: InstallExecuteSequence Base Action ProcessComponents in InstallExecuteSequence table already exists in MSI. Using MSI action. Base Action InstallFinalize in InstallExecuteSequence table already exists in MSI. Using MSI action. Placing action CA_UnRegisterMicrosoftHelp.3643236F_FC70_11D3_A536_0090278A1BB8 before StopServices . Warning: Changes were not saved to MSI Database. Closed MSI Database. I see a few other merging row lines but nothing which indicates an error. I can't remove ProcessComponents and InstallFinalize from the ModuleInstallExecuteSequence table because several entries refer to these as their BaseAction, and BaseActions must also have their own entries in this table. How have others worked around this? --Doug - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integrating documentation with Visual Studio 2008
Doug: I wasted days and days on this but was never able to get any of that to work, even in VS2005. The Wix docs for the tags in question are not helpful, and I couldn't find any examples on the web. Just questions, and a reference to a wix bug that may or may not be fixed (the sourceforge page for that bug id returns a blank page). If you want to save yourself a ton of grief, check out Helpware's H2Reg utility (www.helpware.net). I include this little exe in our installer and launch it from a custom action after I run devenv/setup. It works great. I think it's free for individual use, but the site license was inexpensive, and far less than the time I wasted trying to get it to work in Wix. -- Don From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Payne Sent: Thursday, May 08, 2008 2:20 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Integrating documentation with Visual Studio 2008 I am trying to integrate documentation for my product into the VS 2008 documentation, using HTML_Help_Registration__RTL_---_---.msm and VSIPCC_Collection_Files_RTL_---_---.msm included in the VS 2008 SDK. Has anyone successfully accomplished this? What changes did you make to the html help merge module to get it to work? I encounter an unexpected error while merging. The merge log includes the following: Merging Sequence Table: ModuleInstallExecuteSequence into Database Table: InstallExecuteSequence Base Action ProcessComponents in InstallExecuteSequence table already exists in MSI. Using MSI action. Base Action InstallFinalize in InstallExecuteSequence table already exists in MSI. Using MSI action. Placing action CA_UnRegisterMicrosoftHelp.3643236F_FC70_11D3_A536_0090278A1BB8 before StopServices . Warning: Changes were not saved to MSI Database. Closed MSI Database. I see a few other merging row lines but nothing which indicates an error. I can't remove ProcessComponents and InstallFinalize from the ModuleInstallExecuteSequence table because several entries refer to these as their BaseAction, and BaseActions must also have their own entries in this table. How have others worked around this? --Doug - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
