Re: [WiX-users] Keyboard Enter key press does not validate the condition

I have verified giving the root folder name as C:\ . But still the problem persists. Any other suggestions? - Andy MSI Developer Schneider Electric:working: -- View this message in context:

Re: [WiX-users] Creation of an application pool on IIS7 installed on a server cluster

Hi Mike, Many thanks for your reply. You are right, I'm sorry: information I sent you refers to a try with Wix 3.5. I upgraded to Wix 3.5 in order to see if my problem was solved but nothing happened. Here is a part of the log generated for a try with an installation for the product

Re: [WiX-users] Creation of an application pool on IIS7 installed on a server cluster

The IIS7-specific code (which only exists in WiX 3.5) and the IIS6 code (which exists in both 3.0 and 3.5) are completely different codepaths. Please file 2 bugs on sourceforge (one for the error 3.0 gives, one for 3.5), and we'll take a look. Try to include as much information about how to

[WiX-users] Shortcut to a virtual drive

I'm working on a project which creates a virtual drive which is made available under Computer in Windows Explorer, but it hasn't assigned a letter to the drive. I've struggled with creating a shortcut on the desktop to this virtual drive. I've succeeded with creating a shortcut to an exe file, but

Re: [WiX-users] Creation of an application pool on IIS7 installed on a server cluster

Hi Mike, I opened two bug reports: #2942234 for Wix 3.5 and #2942229 for Wix 3.0. Many thanks for your effort, Matteo -Original Message- From: Mike Carlson (DEV DIV) mica...@mi... - 2010-01-29 10:17 The IIS7-specific code (which only exists in WiX 3.5) and the IIS6 code (which exists

[WiX-users] Wix 3.5 and Burn

Hey all, I was wondering if anyone knew the current status of WIX 3.5 and specifically Burn. The Latest News column on the sourceforge site is stuck at July 4, 2009. Thanks, Everette -- The Planet: dedicated and

Re: [WiX-users] Remove works in Control Panel, fails in Wix (or msiexec)

Thanks, Blair. You are a treasure of information, and I really appreciate your help! I've gotten this far: - I have created stub custom action and put the conditions on it. By looking at the log, that is all working fine. - I can get the directory. - I have the value of

Re: [WiX-users] Remove works in Control Panel, fails in Wix (or msiexec)

Nevermind on the first question. I had a duh moment as soon as I hit send. Using: [DllImport(Msi.DLL)] [return: MarshalAs(UnmanagedType.U4)] internal static extern int MsiSourceListAddSource(string szProduct, string szUserName, [MarshalAs(UnmanagedType.U4)] int dwReserved, string

[WiX-users] WIX and IIS 7.5: query

Hi, I am using WiX for production deployment of a few of our projects concerned with Microsoft Learning. I had a couple of questions for regarding WiX. 1. Can WiX 3.5 which is in Beta be used for production deployment? Currently I am working with WiX 3.0 and facing some issues like:

Re: [WiX-users] External UI

Those actions are duplicated in the Execute sequence anyway, but I'm sure you know that so I must be missing something. What are you trying to do? Phil Wilson -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Thursday, January 28, 2010 7:57

Re: [WiX-users] External UI

Awhile ago I started playing around with external ui and found that if the MSI doesn't actually have an appsearch table then I got the same exact error. Try opening an MSI that you know for a fact has a search and see if that works. Also, if you end up developing a good external ui it would be

Re: [WiX-users] Removing previous version of application that was installed from other installer software

Good point I must admit I have never tried. Neil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 29 January 2010 02:17 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Removing previous version of application that was

Re: [WiX-users] Wix 3.5 and Burn

Check out Rob Mensching's blog post on this here: http://robmensching.com/blog/posts/2010/1/15/Burn-moves-to-a-new-foundation I find the latest news comes from his blog and not necessarily the Sourceforge site. -- View this message in context:

Re: [WiX-users] Remove works in Control Panel, fails in Wix (or msiexec)

HandleObsolete needs to be anywhere convenient before RemoveExistingProducts. Before InstallInitialize is fine. -Original Message- From: Dave Mateer [mailto:dave_mat...@ntm.org] Sent: Friday, January 29, 2010 8:56 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Remove

Re: [WiX-users] WIX and IIS 7.5: query

WiX 3.0 uses the IIS 6 APIs and is thus limited in what IIS 7 features it can modify. WiX 3.5 has the ability to use the IIS 7 APIs directly as well. For core tasks 3.5 is built on the foundation of 3.0 and you shouldn't have problems, but active development is occurring so you will have to

Re: [WiX-users] Wix 3.5 and Burn

I bothered Rob about this a week ago and he reckons it is about 2 months away from being usable. It seems to be good, but due to the lack of docs right now you'll have to get stuck into the source to understand the bootstrapper schemas. I wish I had the time to do that and contribute back.

Re: [WiX-users] Category not updated with patch

Two (sets of) questions: 1. Does your PatchFamily have any children or is it empty? If it has children, what are they? 2. Please look in your .wixmst file for the table name=PublishComponent element and look for the row where the category is modified. Do you see the new value in a field of that

Re: [WiX-users] External UI

I verified that it had the table. I used wix to create a simple reglocator. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Fri, 1/29/10, jhennessey jack.hennes...@onbase.com wrote:

Re: [WiX-users] External UI

I just fired up my old project and it looks like it is working (of course I'm not sure if this is the best way way of doing it). Here's a snippet of how I did it: Installer.SetInternalUI(InstallUIOptions.Silent); session =

[WiX-users] Error 1325 in CostFinalize when uninstalling

When trying to uninstall the previous version of our application, I receive the following error: Error 1325. 'mFileBagIDE.dll' is not a valid short file name. Curiously, if the original installation DVD is in the drive, then there is no error. I checked through the entire MSI database of

Re: [WiX-users] Wix 3.5 and Burn

Cool, thanks for the info On Jan 29, 2010, at 15:30 PM, Ryan O'Neill wrote: I bothered Rob about this a week ago and he reckons it is about 2 months away from being usable. It seems to be good, but due to the lack of docs right now you'll have to get stuck into the source to understand the

Re: [WiX-users] External UI

I've always done basic msi / internal ui so maybe this is a silly question due to me never having done this before. It's my (mis?)understanding that with an external UI handler I'm not in the execute sequence until I say go and that I have to drive the UI myself. What if in my UI sequence I

Re: [WiX-users] External UI

For the actual install, my external UI just does the MsiInstallProduct in silent mode after calling MsiSetInternalUI and gets the messages with MsiSetExternalUIRecord, and it just works. So in that sense there's no need to explicitly drive it. It's more accurate to say that the install drives

[WiX-users] File association description

I'm trying to get a description fixed for a file association. Here is the fragment I'm using: Component Id=DPWFileAssociationion_CMP Guid=74ce314d-ab2b-4756-a729-1223200adecd DiskId=1 File Id=DPWIcon Name=C20PlanningWizardFile.ico Source=Bitmaps\C20PlanningWizardFile.ico / ProgId

Re: [WiX-users] Category not updated with patch

Hi Blair, Thanks for your help. When I look in my .wixmst I see the PublishComponent table and it has the correct value. The value of op is add and there is no previousData attribute. I assume this is correct, since this is a new component rather than a component that is being updated. My