Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap.
That all sounds fine to me personally, as long as I can start investing my time in refactoring all of our installers with WiX v4 (and its bootstrapper!) sometime around the time you would said it would be available. Joel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, June 06, 2008 9:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap. To provide a bit more detail on what Bob said, the biggest difference between the planned WiX bootstrapper and the other bootstrappers discussed here is to create something with built in layers so that you can use only the functionality that you want. Additionally, the hope is to make the binary very tiny (definitely 500K, and I personally want to come in 120K) with very few dependencies. No earth shattering patentable functionality just very tight C/C++ code. Also, Bob pointed out that this is the same struggle I had when we forked WiX v3 off of WiX v2. There was feature creep affecting the WiX v2 schedule so we just had to cut the new stuff free. Thus WiX v3 was born. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Friday, June 06, 2008 09:08 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Proposed adjustments the WiX v2 and WiX v3 roadmap. Evans, Jim wrote: This is sorely disappointing to me personally. Quite frankly, I need the bootstrapper. I hate that I'll be waiting for WiX v4 to get it. It's unlikely to change the date when the bootstrapper becomes available. Working on it in the v4 branch gives us the flexibility to ship it in stages and not be forced to do a more limited release just to ship v3. Also note that there's nothing that ties the bootstrapper to a particular build of WiX; you can easily use v3 to build your setups and v4 for the bootstrapper. In an earlier email, Rob, you mentioned that your team had the design pretty well nailed down, though the code has a long way to go. Is there any chance that the community could get a peek at that design? What aspects of the design are you interested in? The biggest piece is all internal: e.g., how the worker thread handles installations and communicates progress with the UX thread. -- sig://boB http://joyofsetup.com/ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
We -- those who are currently developing with WiX, those who are stuck in purgatory with Windows Installer but InstallShield's interpretation of it, and those who will be writing an installer in the near future -- are in dire need of a decent bootstrapper. I see shining examples of good bootstrappers (Office 2007, SQL 2005, Visual Studio 2008), but there are no frameworks available that make that development process as easy as it should be. It's held back my adoption of WiX for most projects, and I do not look forward to writing a bootstrapper with one of the very limited tools that are out there. If I had to spend $100 on WiX v3 features, $80-$90 would go into a bootstrapper framework, but maybe I want too much. Is the feature set shown in the bootstrappers I listed just too difficult to roll into a decent framework? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, May 27, 2008 12:50 PM To: dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX 3.0 release date Fair. Of course, I don't think we should be looking to take over the world with the WiX toolset (we probably need more people answering questions and improving the overall documentation before getting thousands and thousands more users smile/) but I'm always open to suggestions about what we should do. What do other people think about purely fixing the bugs in the WiX toolset and adding no more functionality? That means there will be no bootstrapper in WiX v3 and no improvement to the IIS CustomActions to better handle IIS7. Basically, imagine the WiX v3 toolset functionality of today plus fixing ~150 bugs. Thoughts? -Original Message- From: dB. [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 12:44 To: Rob Mensching; Daniel Hughes; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WIX 3.0 release date Rob, I think you completely nailed it when you say We could cut the bootstrapper (again) to focus solely on bugs and probably finish WiX v3 sooner but I believe the bootstrapper is more important than that. This is a typical dilemma of any software project. If Wix cost 100$ you could make 100'000$ by the end of the year if you were to ship in October. Or you could delay that revenue into 2009 with the risk of losing market share (people using InstallShield, etc.). I fought several arguments where people were trying to use wix 2.0 + very nasty custom actions vs. wix 3.0 with built-in extensions just because wix 3.0 hasn't shipped yet. I bet many people are having similar arguments in the real world. cheers -dB. -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 2:22 PM To: dB.; Daniel Hughes; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WIX 3.0 release date Interesting. Let's go back and look at the things that are driving the WiX v3 release. 1. Bugs. WiX v2 was marked stable by pushing a number of bugs to WiX v3 (especially Votive bugs). There are still a lot of bugs open that need to be fixed. I do not just want to push a bunch of WiX v2 bugs to WiX v4. 2. Patching. Patching is hard with MSI and the new tools in WiX v3 can help a lot. Those tools are basically done and we're just running down the bug tail now. 3. Votive. Votive was *very* rough in WiX v2. It had years to go before it was going to truly useable. In WiX v3, Justin and a lot of help from members of the VS team have made Votive far more usable. There are still a lot of bugs to fix and the only reason I think it can be done this year is because of the VS help. Otherwise, I'm quite certain we'd *still* have a very crippled VS story. 4. Bootstrapper. Every other day or so there is another request for chaining/bootstrapping. Some of the solutions out there meet some people's needs but IMHO none of them have all of the features that are needed to meet the majority of bootstrapping needs. This part of the WiX toolset is about 2 years late and I think it is a big mistake to go into 2009 without a useable bootstrap story. 5. DTF. After finally deciding that the MSI team was not going to do it, I asked Jason Ginchereau if he would like to add DTF to WiX v3. This codebase was pretty stable so my expectation was that this wouldn't affect our bug count much. Now let's talk about who's doing all of this work. I'm driving the bug count overall with help from the area owners. Peter Marcu (http://blogs.msdn.com/pmarcu) is driving the patching support backed up by Heath Stewart (http://blogs.msdn.com/heaths). Votive is lead by Justin Rockwood (http://blogs.msdn.com/jrock/) and Jason Ginchereau (http://blogs.msdn.com/jasongin)'s team from VS. The bootstrapper code base is being developed by Fredrik Grohn (http://fredrikgrohn.com) and hopefully will be added to WiX soon. DTF is, of course, Jason's baby. Bob Arnson (http://www.joyofsetup.com) basically helps out everywhere. With the
Re: [WiX-users] wix mailing lists open to public = more spam
With no spam filtering on the list, it's sometimes half of all email. Joel -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Tuesday, April 22, 2008 12:48 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] wix mailing lists open to public = more spam I feel this has got worse recently, I think I have a pretty good spam filter but I am seeing about 10% spam now. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan O'Neill Sent: 22 April 2008 18:48 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] wix mailing lists open to public = more spam At the current levels it is a minor annoyance for me, but we all know it will get a lot worse at which point I will have a problem with it. Is there nothing that SourceForge can do? I would have hoped that they would be working on reducing the levels of spam. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: 22 April 2008 18:29 To: Rob Hamflett; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] wix mailing lists open to public = more spam If anyone has any other opinions on this topic, please do make your voice heard. I'm still following this thread and trying to figure out if I should lock non-members out of the list. I'm still very hesitant to do that since it raises the bar for people just starting to get involved with WiX (and we don't need to make anything *harder* smile/). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Tuesday, April 22, 2008 03:58 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] wix mailing lists open to public = more spam There's still a problem if you prefer to use the newsgroup interface (I'm using Thnderbird). You can't delete messages, and the best I think I can do is move them into a separate folder. That might have to suffice if we can't filter them out before they hit the list. Rob DEÁK JAHN, Gábor wrote: On Mon, 21 Apr 2008 15:22:35 +0100, Martin MacPherson wrote: Martin, I have been thinking the same. I found a post who suggested the following if you use gmail: Instead of web-based mail services, just use a good, traditional e-mail client with proper Bayesian spam filter (eg. Thunderbird) and it will eliminate 98-99% of the spam after the initial learning period. It will also adapt to languages other than English, it might take slightly more time (a couple of dozen additional messages) but it will be just fine. You can manually handle the small number of false positives and negatives. Bye, Gábor --- DEÁK JAHN, Gábor -- Budapest, Hungary E-mail: [EMAIL PROTECTED] - 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/javao ne ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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/javao ne ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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/javao ne ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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] MSI's and unknown publisher
Wait, are you saying it's possible to add that entry? I was under the impression that the way Windows Installer caches MSIs, it can no longer authenticate the digital signature of the file as it has been changed. Joel Peterson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Tuesday, April 01, 2008 9:59 PM To: Ryan Elliott Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] MSI's and unknown publisher Ryan Elliott wrote: I have noticed that when I run an MSI that I have developed via WIX, I get a UAC prompt as expected to install the files. However, in the UAC prompt, it states that the MSI is from an Unknown Publisher. Does anyone know if I need to specify anything within my WIX file to populate this entry? No, it comes from an Authenticode digital signature. -- sig://boB http://joyofsetup.com/ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WriteMetabaseChanges: failed to open '/LM/W3SVC/4/'key, retrying 0 time(s)...
http://wix.sourceforge.net/downloadv2.html Joel Peterson [EMAIL PROTECTED] Quality Assurance Engineer Direct: 408-852-8051 Fax: 408-852-8151 Castelle (CSTL) www.castelle.com http://www.castelle.com/ The All-in-One Fax Solution for Business and Enterprise Celebrating 20 Years, 1987 - 2007 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Surendra Katari Sent: Thursday, August 16, 2007 12:47 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WriteMetabaseChanges: failed to open '/LM/W3SVC/4/'key, retrying 0 time(s)... Can you point me to latest build? From: Rob Mensching Sent: Thursday, August 16, 2007 12:46 PM To: Surendra Katari; wix-users@lists.sourceforge.net Cc: Marc McClure Subject: RE: [WiX-users] WriteMetabaseChanges: failed to open '/LM/W3SVC/4/' key, retrying 0 time(s)... There were bugs that were fixed in the last couple months around this sort of thing. I highly recommend you get the latest stable build. From: Surendra Katari Sent: Thursday, August 16, 2007 12:44 PM To: Rob Mensching; wix-users@lists.sourceforge.net Cc: Marc McClure Subject: RE: [WiX-users] WriteMetabaseChanges: failed to open '/LM/W3SVC/4/' key, retrying 0 time(s)... 2.0.5210.0 From: Rob Mensching Sent: Thursday, August 16, 2007 12:44 PM To: Surendra Katari; wix-users@lists.sourceforge.net Cc: Marc McClure Subject: RE: [WiX-users] WriteMetabaseChanges: failed to open '/LM/W3SVC/4/' key, retrying 0 time(s)... What version of the WiX toolset are you using? From: Surendra Katari Sent: Thursday, August 16, 2007 9:38 AM To: Rob Mensching; wix-users@lists.sourceforge.net Cc: Marc McClure Subject: RE: [WiX-users] WriteMetabaseChanges: failed to open '/LM/W3SVC/4/' key, retrying 0 time(s)... When every we see these messages, most of the times, the web sites are not created. But install completes successfully. When we try to uninstall of the product it fail because the sites are not present. Any work around to avoid this situation? Thanks, Surendra From: Rob Mensching Sent: Thursday, August 16, 2007 7:24 AM To: Surendra Katari; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WriteMetabaseChanges: failed to open '/LM/W3SVC/4/' key, retrying 0 time(s)... IIS has this strange locking behavior on Metabase keys that would often mess with deployment (since we often touch so many different keys). What you're seeing is an informational message that a retry was necessary and if things proceeded without failure then that last retry was successful. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Surendra Katari Sent: Wednesday, August 15, 2007 4:17 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WriteMetabaseChanges: failed to open '/LM/W3SVC/4/' key, retrying 0 time(s)... Hi all, We create a MSI which configures couple of websites and application pools. Some time the installer fail to create the Websites without any errors. But we see the following messages in the MSI log when this happens, but setup completes successfully. WriteMetabaseChanges: failed to open '/LM/W3SVC/4/' key, retrying 0 time(s)... Are there any specific reasons for this error messages? Why setup fail or rollback in this when WriteMetabaseChanges: failed to open '/LM/W3SVC/4/' key? Thanks, Surendra [EMAIL PROTECTED] Office: 425-705-5079 Mobile: 425-830-1917 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building a setup.exe
Hi Rob. I can't begin to tell you how much any work in this regard means to a lot of us. I'm waiting until I find a decent, customizable bootstrapper solution before switching all of our installations to WiX. I'd love to see more information on where you're going with it. I've put quite a lot of thought on what I'd like to see. Joel Peterson Quality Engineer [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Friday, July 27, 2007 1:21 AM To: Jim Hewes; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Building a setup.exe I'm slowly making progress on a new tool for the WiX toolset called burn (see: http://robmensching.com/blog/archive/2007/04/10/WiX-v3-Roadmap-Draft.asp x). It is a generic bootstrapper that will eventually handle the things you list below. It's slow going and not really anything in a state to share yet. If only I could sleep less... smile/ Anyway, that's where I'm moving towards. The existing setupexe project is as limited as you point out. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Hewes Sent: Thursday, July 26, 2007 1:36 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Building a setup.exe I've been working on building an installer using Wix. Building an msi seems to work well and I have no major problem. But where I'm getting bogged down is in the things surrounding it, such as the setup.exe program. I have a couple of questions. 1. I've noticed the setupbld.exe utility and I've tried it. It seems to create a setup.exe with all files packed into a single EXE, which are then extracted at runtime. That's good. But in addition to that, I also need a setup.exe that will launch loose, uncompressed files for installation from a CD. Can it currently do that as well? 2. This isn't so much a question as a feature request. I need for to the setup.exe to show a language selection dialog to allow the user to select an installation language (like Installshield does). I think I will probably try to add it myself to the setupexe project if it never gets added by the Wix guys. 3. I read about chaining as a way of handling more than one installation. I currently have this requirement, since I need to install a driver and also an application that works with the product. For various reasons, it's better for us not to package these in the same installer. But chaining doesn't seem like an ideal solution either---I think that automatically launching one installer after another can be confusing to the end user. I think a better solution, at least for CD installation, is to begin with a menu. The menu allows the user to choose what to install; that is, which installer to run. The menu can list the device installer and the application installer. It can also allow users to optionally install things like Adobe Reader if your documentation is in PDF form. I've seen some products that do this and they have graphically pretty menu programs. Unfortunately, in doing a search, I didn't find any decent existing software for developing such a menu program. Can anyone recommend something? Sure, perhaps it's really just a dialog with buttons, so you can probably write one yourself (I'm a C++ programmer). But I was hoping to find something that included some pre-designed fancy graphics, and allowed you to slap together a menu launcher in an hour or so with no programming. Does this make sense? Or am I thinking in the wrong direction? Although I like the feeling of working close to the metal with Wix as compared to some commercial product like InstallShield, I also seem to be getting slowed by the setup.exe issues outside of the actual msi more than anything. Thanks for any comments. Jim - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] msi to exe
It needs something called a bootstrapper wrapped around it. Joel Peterson Quality Engineer [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Afshin Sepehri Sent: Friday, June 22, 2007 1:53 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] msi to exe Hi, How can I convert an .msi file to .exe? Afshin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] upgradable merge modules
Couple comments. 1. I really wish http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/ was more of a how-to. It isn't really intuitive on how to use all of this tooling in Visual Studio 2005, or where to find it. 2. WiX really needs a better bootstrapper as a part of what it offers. If it were to have a framework to make a bootstrapper ranging from what you see with the Visual Studio 2005, SQL Server 2005, Exchange Server 2007, and Office 2007 installers, it'd be golden. 3. I can't believe a company hasn't come up with a Visual Studio 2005 SDK for building highly customizable and interactive bootstrappers. Joel Peterson Quality Engineer [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, May 31, 2007 8:42 AM To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] upgradable merge modules Jerome, There are several readily available bootstrappers. If you are developing using Visual Studio 2005, this article may be helpful: http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/ For other open source options (like dotNetInstaller - see http://www.codeproject.com/install/dotNetInstaller.asp) check the archives of this mailing list. To answer the question of what the bootstrapper is, as you correctly surmised it is a small application (which you certainly could code yourself, but don't have to) which handles installation of any prerequisites (such as the .NET runtimes) that cannot be encapsulated within your MSI file due to licensing or other issues. Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerome Haltom Sent: Thursday, May 31, 2007 11:31 AM To: Bob Arnson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] upgradable merge modules That doesn't really explain what the bootstrapper is. What is this bootstrapper thing? How do I build one? * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Vista unknown publisher
Just want to point out that even if you sign your MSI, you will still get a Unknown Publisher on uninstallation. It's sort of a sad limitation that is explained here: http://blogs.msdn.com/windows_installer_team/archive/2006/10/19/new-wind ows-installer-4-0-webcast-scheduled-and-q-a-from-lua-webcast.aspx Question: When I uninstall my signed msi, I get a UAC prompt that says Unknown publisher. All of the UAC prompts during the install display my signed information fine. Is this a Vista problem, or a problem with my msi. Answer: We have a KB pending for this behavior and are considering this for a fix. The reason this happens is that when we cache the MSI we strip out some data, making the certificate invalid. We're looking at mitigations but we do not have a solution at this time. Nothing is wrong with the package. Joel Peterson Quality Engineer [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, May 29, 2007 8:47 AM To: Pseudonymic Wannabe; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Vista unknown publisher Sign your MSI. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pseudonymic Wannabe Sent: Tuesday, May 29, 2007 6:05 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Vista unknown publisher When running our MSI package on Vista midway under the installation a dialog pops up (UAC) and complains about Unknown Publisher on our package.MSI file and asks for permission to continue. Is there anyway to author our package in such a way that the user won't be bothered with such interference? _ Like the way Microsoft Office Outlook works? You'll love Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-usocid=TXT_TAGHM_migr ation_HM_mini_outlook_0507 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX at TechEd 2007?
Is there any place in particular where I should be making noise in regards to getting a BOF or breakout session going? Joel Peterson Quality Engineer [EMAIL PROTECTED] From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Sunday, March 11, 2007 12:19 PM To: Peterson, Joel; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WiX at TechEd 2007? Heh, funny you should ask. http://robmensching.com/blog/archive/2007/03/11/WiX-at-TechEd-2007--Surv ey-says.aspx From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peterson, Joel Sent: Friday, March 09, 2007 11:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX at TechEd 2007? This is more for Rob and Bob, but if anyone else has any details I'd love to hear them. It actually crossed my mind to ask this as I was reading Rob's blog on the Designed for Operations Workshop. Is there any details for WiX-related breakout sessions, Birds of a Feather sessions, and/or Technical Learning Center developer availability at TechEd 2007? Thank you. Joel Peterson Quality Engineer [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX at TechEd 2007?
This is more for Rob and Bob, but if anyone else has any details I'd love to hear them. It actually crossed my mind to ask this as I was reading Rob's blog on the Designed for Operations Workshop. Is there any details for WiX-related breakout sessions, Birds of a Feather sessions, and/or Technical Learning Center developer availability at TechEd 2007? Thank you. Joel Peterson Quality Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows 98 and ALLUSERS
I know... but I still have people out there that haven't for some reason. Do us all a favor and drop support for them so we don't have to support them as well. :) Joel Peterson Quality Engineer [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Robertson Sent: Friday, March 02, 2007 2:37 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Windows 98 and ALLUSERS Well, Microsoft has given up on 9x... I know... but I still have people out there that haven't for some reason. ALLUSERS behaves very strangely on 9x. From the documentation: If I run the install with logging enabled I see ALLUSERS=1 and Privileged=1 which kind of implies that I should have taken the per-machine route in the fragment I posted? And my HKMU registry addressing got me to HKLM rather than HKCU which points in the same direction? What does %CommonAppData% and %LocalAppData% resolve to? They work OK on Vista :-) On earlier platforms the app has code to pull in appropriate folders when the enviroment variable doesn't exist. -- View this message in context: http://www.nabble.com/Windows-98-and-ALLUSERS-tf3332569.html#a9267349 Sent from the wix-users mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDE V ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What happened to Tallow.exe
Kudos again on that name. It's just about 100 times better. Tallow hasn't been used in making candles in a long, long time. Joel Peterson Quality Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Thursday, January 04, 2007 1:33 PM To: Dan Hoeger; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] What happened to Tallow.exe Heat replaced tallow in v3. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger Sent: Thursday, January 04, 2007 1:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] What happened to Tallow.exe I'm having trouble with this on Vista so I thought I would download v3.0.2420.0 and it doesn't have this exe. Without this tool what is the recommended way to extract the registration information for a DLL? Thanks, Dan - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] help with Tallow.exe error on Vista
I've had all sorts of issues getting OCX to self-register on Vista, and
eventually beat them out by making sure the installer was running
elevated. You're most likely correct, Mike. I bet tallow.exe needs that
manifest.
Joel Peterson
Quality Engineer
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Dimmick
Sent: Thursday, December 21, 2006 8:38 AM
To: 'Dan Hoeger'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] help with Tallow.exe error on Vista
Have you tried running it from an elevated command prompt? That
sometimes helps with COM registrations (despite the fact that the
'canary' keys that HKCR, etc, are redirected to should be editable by a
non-admin user, I found that a low-privileged account didn't always work
under XP).
I wonder if Vista's own registry redirection feature for legacy
applications gets in the way here. Does tallow have a manifest to
specify asInvoker privilege level?
--
Mike Dimmick
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger
Sent: 21 December 2006 16:07
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] help with Tallow.exe error on Vista
Does anyone know off hand why this would fail on Vista?
This same call works fine on 2003 server.
Thanks,
Dan
Source\Common\CrmFileListtallow.exe -s Drop2Ctrl.ocx
Microsoft (R) Windows Installer Xml Tool version 2.0.3929.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi;
Fragment
DirectoryRef Id=TARGETDIR
Component Id=component0 DiskId=1 Guid=PUT-GUID-HERE
File Id=file0 Name=DROP2C_1.OCX LongName=Drop2Ctrl.ocx
src=d:\enlistment\fwm3\Source\Common\CrmFileList\Drop2Ctrl.ocx
/Failed to SelfReg: Drop2Ctrl.ocx
System.Reflection.TargetInvocationException: Exception has been thrown
by the target of an invocation. ---
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT
E_FAIL has been returned from a call to a COM component.
at DllRegisterServer()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target,
Object[] arguments, SignatureStruct sig, MethodAttributes
methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target,
Object[] arguments, Signature sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture)
at
Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain.DynamicPInvo
ke(String dll, String entryPoint, Type returnType, Type[]
parameterTypes, Object[] parameterValues)
at
Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain..ctor(String
[] args)
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731} Value=VBPropertyBag
Type=string /
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Value=C:\Windows\system32\MSVBVM60.DLL Type=string /
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Name=ThreadingModel Value=Apartment Type=string /
/Component
/DirectoryRef
/Fragment
/Wix
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Comparing two MSIs
Orca is a fair good tool and will allow you to eyeball compare the tables, not sure it has any automatic comparison feature. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Wednesday, December 06, 2006 3:28 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Comparing two MSIs Is there a tool out there to compare two MSIs? I'm moving our MSIs to wixv3, and I want to verify that the built MSIs are the same as previously. Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need recomendation - including .NET redist
Get some examples from the Office, Exchange, and Visual Studio teams, and you're set. Their bootstrappers are awesome. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, December 05, 2006 11:04 AM To: David Thielen; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Need recomendation - including .NET redist On my todo list. You can see the beginnings of a bootstrapper in WiX v3. I've actually taken a detour away from that project for a month or so to get the v2 CustomActions stable so that we can stick a fork in WiX v2 and call it done. Then I'll go back to the WiX v3 bootstrapper. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen Sent: Tuesday, December 05, 2006 09:25 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Need recomendation - including .NET redist I take it I would have to use the VS installer instead of WIX? We can't do that as we use a lot of WIX functionality that does not exist in the VS installer. I wish WIX had this capability... Thanks - dave David Thielen www.windwardreports.com 303-499-2544 x1185 Cubicle Wars - http://www.windwardreports.com/film.htm From: Erv Walter [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 05, 2006 10:12 AM To: David Thielen; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Need recomendation - including .NET redist Visual Studio also includes a bootstrapper that can install your prerequisites and then launch your setup. It can get the prereqs from your local CD, or if you are mostly a downloaded product, it can download the prereqs from the official microsoft site when/if they are needed. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Osmond Sent: Monday, December 04, 2006 8:33 PM To: David Thielen; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Need recomendation - including .NET redist Dave, You could have a look at the Microsoft Component Installer (PSetup). It provides a bootstrap that will install your redistributables and then your app. The redistributables can be got from local source or the web. http://msdn2.microsoft.com/en-us/library/ms994369.aspx Michael From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen Sent: Tuesday, 5 December 2006 12:03 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Need recomendation - including .NET redist Hi; We have had feedback from 4 potential customers that having .NET 2.0 as a prerequisite with the message taking them to the download made our installer too difficult and too complicated (and note - these are programmers!) So we need to have installing the .NET framework (and J# redist) as an automatic part of our install. So my questions are: 1) Is it better to have the redist in our install, or have it that when they click Next it downloads it and runs it automatically? 2a) If it's include it, anything special we have to do to have this in our installer? 2b) If it's download and run, how do we set that up to go? thanks - dave - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need recomendation - including .NET redist
In the underlying complexity, I'm sure SQL 2005 is more complex than Exchange 2007. The prerequisite detection, user interface, and installation customization (and how they pass information on to the MSIs) of all of these Microsoft bootstrappers are amazing. It'd be nice to have generic forms of each, for sure. We're looking to wrap all of our products and add-ons into individual WiX-based MSIs, with an Exchange 2007-style localized bootstrapper as the CD autorun for installation. I've done some research into companies that might offer toolkits to do this, but there really are none. It'd make WiX, and Windows Installer in general, all the better if this sort of thing was available. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 05, 2006 12:21 PM To: Peterson, Joel; David Thielen; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Need recomendation - including .NET redist I talk to those teams regularly (SQL is more interesting than Exchange, IMHO). The trick is how to take their very specialized solutions and make them generic enough to solve all of the different problems we all face here. That, and often their solutions need to be scaled (down) such to be more useful by smaller applications. From: Peterson, Joel [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 05, 2006 11:58 To: Rob Mensching; David Thielen; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Need recomendation - including .NET redist Get some examples from the Office, Exchange, and Visual Studio teams, and you're set. Their bootstrappers are awesome. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, December 05, 2006 11:04 AM To: David Thielen; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Need recomendation - including .NET redist On my todo list. You can see the beginnings of a bootstrapper in WiX v3. I've actually taken a detour away from that project for a month or so to get the v2 CustomActions stable so that we can stick a fork in WiX v2 and call it done. Then I'll go back to the WiX v3 bootstrapper. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen Sent: Tuesday, December 05, 2006 09:25 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Need recomendation - including .NET redist I take it I would have to use the VS installer instead of WIX? We can't do that as we use a lot of WIX functionality that does not exist in the VS installer. I wish WIX had this capability... Thanks - dave David Thielen www.windwardreports.com 303-499-2544 x1185 Cubicle Wars - http://www.windwardreports.com/film.htm From: Erv Walter [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 05, 2006 10:12 AM To: David Thielen; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Need recomendation - including .NET redist Visual Studio also includes a bootstrapper that can install your prerequisites and then launch your setup. It can get the prereqs from your local CD, or if you are mostly a downloaded product, it can download the prereqs from the official microsoft site when/if they are needed. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Osmond Sent: Monday, December 04, 2006 8:33 PM To: David Thielen; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Need recomendation - including .NET redist Dave, You could have a look at the Microsoft Component Installer (PSetup). It provides a bootstrap that will install your redistributables and then your app. The redistributables can be got from local source or the web. http://msdn2.microsoft.com/en-us/library/ms994369.aspx Michael From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Thielen Sent: Tuesday, 5 December 2006 12:03 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Need recomendation - including .NET redist Hi; We have had feedback from 4 potential customers that having .NET 2.0 as a prerequisite with the message taking them to the download made our installer too difficult and too complicated (and note - these are programmers!) So we need to have installing the .NET framework (and J# redist) as an automatic part of our install. So my questions are: 1) Is it better to have the redist in our install, or have it that when they click Next it downloads it and runs it automatically? 2a) If it's include it, anything special we have to do to have this in our installer? 2b) If it's download and run, how do we set that up to go? thanks - dave - Take Surveys. Earn Cash
Re: [WiX-users] ConfigureSQL Bug
I figure I might as well add to this discussion. I'm a daily WinDbg with GFlags user/addict, to the point where I can go from a vanilla system to a full debug system in a few minutes (it'd be faster if it weren't for the delay of downloading symbols from the Microsoft Symbol Server). Following is a tutorial I've passed around our Engineering department a few times. I thought I'd add a little with how we use WinDbg (commonly referred to as windbag by Windows developers). The latest version can always be downloaded from http://www.microsoft.com/whdc/devtools/debugging/default.mspx. The default installation options are best, and are used in paths in these instructions. Pageheap and GFlags http://support.microsoft.com/default.aspx?scid=kb;en-us;286470 While these settings can help you in configuring a process to start in the debugger with options to catch exceptions earlier, we have an easier way to do that. This page is an excellent resource on what the debugger does to your process with these options. Our easier way of enabling these options comes in form of the attached .REG file. As you can see, this will merge settings into the registry for our service, SomeService.exe. I'd do this for every process you want to run in the debugger. It instructs Windows to start this process in the debugger with full pageheap and gflag options. If you're doing this for a service running under the Local System account, you must go in to the Service Control Manager and set the service properties to Interact with the desktop. For services that run as a specific user, you cannot use the Service Control Manager. Start those types of services by opening Windbg and navigating to File - Open Executable. Be aware of services that depend on other services or make RPC calls into services, as these will start them up when you might not want them to. Once Windbg is open for any process, you should enter g in the WinDbg command line to get the process going. If you wait too long to do this for services, they will time-out. Non-service processes don't need to worry about any of this, other than pressing g once you want to begin. The first thing I do on a new system is download that system's Windows symbols from the Microsoft Symbol Server to the C:\websymbols directory so I don't have to dynamically download each symbol when its image is referenced. This can be done with symchk.exe, which comes with Debugging Tools for Windows. I point it at the system32 (or equivalent) directory recursively, and go about configuring and debugging as it can take an hour: symchk /r c:\windows\system32 /s SRV*c:\websymbols\*http://msdl.microsoft.com/download/symbols If you are using a process in WinDbg for the first time, you need to configure the Workspace and save it. I do the following for each process: 1. Navigate to File - Symbol File Path. 2. Add c:\SomeProcess;c:\websymbols;SRV*c:\websymbols*http://msdl.microsoft.co m/download/symbols, where c:\SomeProcess represents the path where you've added the symbols of your process. 3. Press OK. 4. Navigate to File - Image File Path. 5. Add c:\SomeProcess;c:\windows\system32, where c:\SomeProcess represents the path where your process is located. 6. Press OK. 7. Navigate to File - Save Workspace. Once you've saved the workspace, each time you start this process from its location, all of these settings will be loaded. When an unhandled exception occurs, the analyze -v commad is every developer's best friend. It'll give you a very robust stack trace and line information where your problem is (if symbols are properly loaded). The lm command will show you loaded symbols and the ld * command will force all symbols to be loaded. You can save a dump file for later by using the .dump /mfa c:\mydump.dmp command. Almost everything else you'd want to know can be found in the help file for Debugging Tools for Windows. It has a lot of useful information. Enjoy. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, December 05, 2006 12:27 PM To: Michael Osmond; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] ConfigureSQL Bug You might try running the install under a debugger after using GFlags ( http://technet2.microsoft.com/WindowsServer/en/library/b6af1963-3b75-42f 2-860f-aff9354aefde1033.mspx?mfr=true) to turn on PageHeap. PageHeap might be able to catch the memory corruption when it happens instead of waiting for the second corruption to hit. I would also suggest try using the command-line debuggers instead of VS. The command-line debuggers are a lot less invasive (and insanely more difficult to use smile/). I've had much more luck catching these kinds of problems with the command-line debuggers + PageHeap. It sounds like you have a SQL Script in
[WiX-users] New Official Installation Technology? CBS? What?
I saw this while doing some digging as to why PowerShell RTM isn't available for Vista: http://blogs.msdn.com/powershell/archive/2006/11/15/windows-powershell-w indows-vista.aspx So what's the difference between the Vista and XP/Server release of PowerShell? Is it just the installer? Why does it take 2 more months? Yes - the only difference is the installer. Being an official Windows component means you use the official windows installation technology and on Vista that is the new CBS technology. There is exactly one team in the world that can build this and that team has been a tad busy (While I sometimes think that PowerShell is more important that Vista - I just can't seem to ever convince other people of that. :-) ). PowerShell is the world's first Vista OutOfBand release. There are a few pain points that come with that honor. Nothing serious but there are just some things that are different and need a bit of time to work out. They are a great team and are doing great work, they just need a bit of time. Cheers! Jeffrey Snover [MSFT] Windows PowerShell/MMC Architect What? Isn't the Windows Installer the latest and greatest installation technology? Joel Peterson Quality Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to prompt to terminate process on uninstall
Hi Jeff. The custom needs be placed in the proper sequence, such as before RemoveAllFiles. WiX, or more accurately MSI, isnt organized towards stages of installation, but allows you to schedule events based on those stages. Joel Peterson [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff MacDuff Sent: Monday, November 06, 2006 8:16 AM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to prompt to terminate process on uninstall Ok a follow up question, Where do I put the uninstall custom action at in the Wix file? My wix file doesnt contain any kind of remove / uninstall sections from what I can tell? -JEff From: Rob Mensching Sent: Thursday, October 26, 2006 1:02 PM To: Jeff MacDuff; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] How to prompt to terminate process on uninstall wix\ src\ca\wixca\dll\CloseApps.cpp From: Jeff MacDuff Sent: Thursday, October 26, 2006 12:58 To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] How to prompt to terminate process on uninstall Ahh ok.. I understand. Can you tell me more about this CloseApps CA ? Is this an existing item I can just hook into? From: Rob Mensching Sent: Thursday, October 26, 2006 12:58 PM To: Jeff MacDuff; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] How to prompt to terminate process on uninstall Youd have to use a CustomAction like CloseApps to kill off more than just those files that are held in use by a process with a visible window. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff MacDuff Sent: Thursday, October 26, 2006 12:53 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to prompt to terminate process on uninstall What is the correct method in the WIX file to list the process names that should / need to be killed before uninstall occurs? What we are seeing is that if process A is running the MSI at uninstall time will uninstall all of the other files ( dlls / xmls / etc ) and then prompt the user to reboot. At reboot the process A is removed. The bug is that if the user chooses not to reboot.. and clicks on the process A systray icon this will cause process A to crash since its dependent files are now gone. How do I tell the MSI uninstall process to kill process A ? Thanks, Jeff - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fragments, Cabinets, and Light, Oh My!
Doh! Yeah, youre right. I totally forgot about that. I was working on ComponentGroup and got sidetracked. One thing I dont understand is why ComponentGroup isnt a parent node for Component. Itd be nice to have ComponentGroup exist inside of Directory or DirectoryRef so you wouldnt have to setup a ComponentGroup with each ComponentRef afterwards. Oh well. Thanks for your help, Simon. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED] From: Simon Dahlbacka [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 12:25 PM To: Peterson, Joel Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fragments, Cabinets, and Light, Oh My! ComponentRef Id=driver.exe/ seems missing /Simon On 10/18/06, Peterson, Joel [EMAIL PROTECTED] wrote: Hi all. I'm using WiX 3.0.2211.0. My installer is pretty basic, but I have a driver set provided by a partner that I want to have in its own .WXS, since creating modular installers is a good thing to do. I've attached both .WXS files (redacted and simplified); Product.wxs is the main and PrintDriver.wxs is the fragment. Every time I build the solution in Visual Studio 2005, I get the following: -- Rebuild All started: Project: Product, Configuration: Debug Any CPU -- C:\Program Files\Windows Installer XML v3\bin\candle.exe -dDebug -out obj\Debug\PrintDriver.wixobj PrintDriver.wxs C:\Program Files\Windows Installer XML v3\bin\candle.exe -dDebug -out obj\Debug\Product.wixobj Product.wxs C:\Program Files\Windows Installer XML v3\bin\Light.exe -out bin\Debug\Product.msi obj\Debug\PrintDriver.wixobj obj\Debug\Product.wixobj C:\Build\Installation\WiX\Product\Product.wxs(5,0): Warning LGHT1079: The cabinet 'Product.cab' does not contain any files. If this installation contains no files, this warning can likely be safely ignored. Otherwise, please add files to the cabinet or remove it. == Rebuild All: 1 succeeded, 0 failed, 0 skipped == What stupid thing did I forget to do while splitting this off in its own Fragment? I've poured over the WiX v2 Tutorial, blogs, and this mailing list for anything and have come up blank. Joel Peterson [EMAIL PROTECTED] - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fragments, Cabinets, and Light, Oh My!
Or even better, Heat should have a switch to throw each directorys contents into its own ComponentGroup. That would be very cool. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peterson, Joel Sent: Wednesday, October 18, 2006 1:40 PM To: Simon Dahlbacka Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fragments, Cabinets, and Light, Oh My! Doh! Yeah, youre right. I totally forgot about that. I was working on ComponentGroup and got sidetracked. One thing I dont understand is why ComponentGroup isnt a parent node for Component. Itd be nice to have ComponentGroup exist inside of Directory or DirectoryRef so you wouldnt have to setup a ComponentGroup with each ComponentRef afterwards. Oh well. Thanks for your help, Simon. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED] From: Simon Dahlbacka [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 12:25 PM To: Peterson, Joel Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fragments, Cabinets, and Light, Oh My! ComponentRef Id=driver.exe/ seems missing /Simon On 10/18/06, Peterson, Joel [EMAIL PROTECTED] wrote: Hi all. I'm using WiX 3.0.2211.0. My installer is pretty basic, but I have a driver set provided by a partner that I want to have in its own .WXS, since creating modular installers is a good thing to do. I've attached both .WXS files (redacted and simplified); Product.wxs is the main and PrintDriver.wxs is the fragment. Every time I build the solution in Visual Studio 2005, I get the following: -- Rebuild All started: Project: Product, Configuration: Debug Any CPU -- C:\Program Files\Windows Installer XML v3\bin\candle.exe -dDebug -out obj\Debug\PrintDriver.wixobj PrintDriver.wxs C:\Program Files\Windows Installer XML v3\bin\candle.exe -dDebug -out obj\Debug\Product.wixobj Product.wxs C:\Program Files\Windows Installer XML v3\bin\Light.exe -out bin\Debug\Product.msi obj\Debug\PrintDriver.wixobj obj\Debug\Product.wixobj C:\Build\Installation\WiX\Product\Product.wxs(5,0): Warning LGHT1079: The cabinet 'Product.cab' does not contain any files. If this installation contains no files, this warning can likely be safely ignored. Otherwise, please add files to the cabinet or remove it. == Rebuild All: 1 succeeded, 0 failed, 0 skipped == What stupid thing did I forget to do while splitting this off in its own Fragment? I've poured over the WiX v2 Tutorial, blogs, and this mailing list for anything and have come up blank. Joel Peterson [EMAIL PROTECTED] - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX v3, VS2005, and Preprocessor Environment Variables
Hi all. I know that when you open cmd.exe, it loads all of the environment variables and caches them. If you were to navigate to System - Advanced - Environment Variables and add a new System variable named testvar, typing cd %testvar% in the existing cmd.exe wouldnt work. Youd need to open a new cmd.exe instance for it to know about the new environment variable. This doesnt seem be to true for candle.exe, which I assume uses what Visual Studio 2005 caches from Environment Variables when it starts. I was working on a project and wanted all of my File sources to inherit from a parent directory that will be different on the Team Foundation Build system and developer workstations. Leaving Visual Studio 2005 open, I created a new Environment Variable named BuildPath with the value C:\Build. I then referenced this path for each File in my .WXS, for example: File Id=test.exe Name=test.exe KeyPath=yes Source=$(env.BuildPath)\TestFolder\test.exe / Upon pressing F7 (Build Solution), it returns the error Error CNDL0150: Undefined preprocessor variable $(env.BuildPath). On a hunch I closed Visual Studio 2005, opened the Solution, and pressed F7 again to it have it work perfectly. Im having a hard time understanding why this would be different from my cmd.exe example, if each time I press F7 (Build Solution), a new instance of candle.exe is starting. Im not familiar with all of the nuances of Visual Studio; is it standard for compilers and linkers to use environment variables cached by Visual Studio? If not, should I file this as a bug? Thank you. Joel Peterson [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX v3, VS2005, and Preprocessor Environment Variables
Hi Cullen. Thanks for putting my explanation into much better terms. Ive been thinking on this a little more, and Ive decided that every compiler and linker is probably at the mercy of Visual Studios environment variables. This cant be a bug in candle.exe, but more of the way Visual Studio handles paths. Thanks again! Joel Peterson [EMAIL PROTECTED] From: Cullen Waters [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 10, 2006 3:53 PM To: Peterson, Joel; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WiX v3, VS2005, and Preprocessor Environment Variables Joel, I think you may be seeing the difference between user scope environment variables, and system scope env variables. When you set a user-scope variable, it is set in the instance of cmd.exe that is executing. If you set a system-scope variable, it isnt re-read until you kill and restart cmd.exe. Im not sure how VS treats it, but based on the behavior youre seeing, I would guess that VS keeps an instance of cmd.exe alive (with console redirected back to VS). When you set the system-scope variable, VS isnt aware of it until you cause the cmd.exe to be reloaded (by closing and re-opening VS). Im not an expert on these issues, but that is what I think youre seeing. Cullen From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peterson, Joel Sent: Tuesday, October 10, 2006 3:42 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX v3, VS2005, and Preprocessor Environment Variables Hi all. I know that when you open cmd.exe, it loads all of the environment variables and caches them. If you were to navigate to System - Advanced - Environment Variables and add a new System variable named testvar, typing cd %testvar% in the existing cmd.exe wouldnt work. Youd need to open a new cmd.exe instance for it to know about the new environment variable. This doesnt seem be to true for candle.exe, which I assume uses what Visual Studio 2005 caches from Environment Variables when it starts. I was working on a project and wanted all of my File sources to inherit from a parent directory that will be different on the Team Foundation Build system and developer workstations. Leaving Visual Studio 2005 open, I created a new Environment Variable named BuildPath with the value C:\Build. I then referenced this path for each File in my .WXS, for example: File Id=test.exe Name=test.exe KeyPath=yes Source=$(env.BuildPath)\TestFolder\test.exe / Upon pressing F7 (Build Solution), it returns the error Error CNDL0150: Undefined preprocessor variable $(env.BuildPath). On a hunch I closed Visual Studio 2005, opened the Solution, and pressed F7 again to it have it work perfectly. Im having a hard time understanding why this would be different from my cmd.exe example, if each time I press F7 (Build Solution), a new instance of candle.exe is starting. Im not familiar with all of the nuances of Visual Studio; is it standard for compilers and linkers to use environment variables cached by Visual Studio? If not, should I file this as a bug? Thank you. Joel Peterson [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX UI Control Repository?
Hi all. Im sure I already know the answer to some of these questions, but I must ask. Is there a repository of user-submitted WiX UI content? Are there any available templates of some of the more popular dialogues that are used in MSI installers? Is there an unwritten spec to adhere to? What about some of the more robust install user interfaces, such as Exchange 2003/2007, Office 2003/2007, SQL Server 2005, or Visual Studio 2005? A lot of the interface elements in these installers are my personal WiX Holy Grail. Joel Peterson [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX 3 in Team Foundation Build
Hi Rob. Do you have any details on what specific domain policy is giving Light a headache? I can have that changed, but only if I know what specific policy setting is causing the issue. Id like to do that explicitly for our Team Foundation Server, rather than opening up security holes by adding DOMAIN\TFSService to local Administrators (which didnt work, maybe Ill have more on that later). Thanks, Rob. Thanks, Mike. Thanks, Bob (Outlook Desktop Alert was driving me nuts on your reply fest :D) Joel Peterson [EMAIL PROTECTED] From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, October 05, 2006 9:44 AM To: Mike Dimmick; Peterson, Joel; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WiX 3 in Team Foundation Build Mike is correct. However, ideally, youd look at getting the policy in the domain tweaked so you could run validation on your build servers. You will catch bugs much earlier running it there. If worse comes to worse, maybe you could only suppress validation on the build machines but ensure all dev machines still run validation. In case anyone hasnt noticed, Mike is just tearing up the mailing list with answers that are almost always *right on target* (very few times have I thought, Well, I would do that a bit differently, but whatever). If you havent said, Thanks, Mike recently, you should do that. At the same time, you might also say, Thanks, Bob since Bob also does quite a bit of work here (Bobs just been busy lately moving into his new condo). And, dont let these guys scare you away. If you know the answer to someone elses question, feel free to fire it off. If youre not quite right, someone will provide slightly adjusted guidance. One of the best ways to learn something well is to give a slightly wrong answer and then get corrected well, at least I remember those cases very well. smile/ Okay, time for me to get back to shipping Vista. Thanks, Mike. Thanks, Bob. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Thursday, October 05, 2006 7:48 AM To: Peterson, Joel; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX 3 in Team Foundation Build light.exe has, I believe,to load the .msi in order to perform the validation step. For the moment, you could suppress validation with the -sval switch which I think is a SuppressValidation property (I'm not familiar with MSBuild). -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peterson, Joel Sent: 04 October 2006 01:19 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX 3 in Team Foundation Build Hi all. Im new to this list so please correct me if this has already been discussed. Ive installed the latest weekly build of WiX 3 on my development system and also on my Team Foundation Server/Team Foundation Build. The WiX solution builds fine on my development system, in all Debug/Release configurations. I checked that solution in to the main project on the Team Foundation Server, and configured a Build for it. When I start the build, its all run with the DOMAIN\TFSService user account as specified in the Team Foundation Installation manual. Everything runs fine, until it gets to Light: Target PrepareForBuild: Creating directory obj\Release\. Creating directory D:\Build\ProjectName\WiX - Web Client Printer\Binaries\Release\. Target Compile: C:\Program Files\Windows Installer XML v3\bin\candle.exe -out obj\Release\Web Client Printer.wixobj Web Client Printer.wxs Target Link: C:\Program Files\Windows Installer XML v3\bin\Light.exe -out D:\Build\ProjectName\WiX - Web Client Printer\Binaries\Release\Web_Client_Printer.msi obj\Release\Web Client Printer.wixobj light.exe : error LGHT0216: An unexpected Win32 exception with error code 0x659 occurred: This installation is forbidden by system policy. Contact your system administrator Done building target Link in project Web Client Printer.wixproj -- FAILED. This error is what one would get if they ran a MSI with a user account that did not have Administrative priviledges, but why would that appear during the link process? The Team Foundation Server Installation manual specifically says not to give DOMAIN\TFSService administrative priviledges for security reasons, but I did anyways to see if it would get around this issue. It did not, and I still received the same error message. I can provide the full build log if necessary, I havent had a chance to redact it yet. Joel Peterson [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID
