Re: [WiX-users] 32-bit and 64-bit MSIs bundled in single EXE
It looks like the current bootstrapper calls msiexec.exe, rather than using the APIs. I inherited the code and it looks like it was done that way to make it convenient to pass command line arguments, among other things. If I continue to call the executable, I assume that I'll need to choose the correct msiexec.exe (system32 for 64-bit on x64, syswow64 for 32-bit on x64, system32 on 32-bit), or can x64's system32\msiexec install 32-bit MSIs? In my bootstrapper I just do CreateProcess(NULL, msiexec /i xxx, ...) and it does the right thing on both x64 and x86. Regards, John - 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 XML manipulation
HI I am aware of escaping square brackets and I have done it. My query looked exactly like /redirections/redirection[\[]last()[\]] and when error was displayed it had the proper XPATH format. I still wonder if there was some bug in WIX not handling XPATH right. Daniel From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: 22 January 2008 22:13 To: Daniel Hatala; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WIX XML manipulation From the documentation: ElementPath : String : The XPath of the element to be modified. Note that this is a formatted field and therefore, square brackets in the XPath must be escaped. To escape square brackets, use [\[] and [\]], so your XPath needs to be /redirections/redirection[\[]last()[\]] Otherwise Windows Installer thinks [last()] is a property and tries to evaluate it, and an error occurs as () aren't valid in a property name. This feature is present to allow properties to be used to control the XPath. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 22 January 2008 17:40 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WIX XML manipulation Hi I need to modify an XML file and create several nodes with the same name redirections xmlns=msmq-queue-redirections.xml redirection fromhttps://external_host/*/from tohttp://internal_host/msmq/internal_queue/to /redirection redirection fromhttps://external_host/*/from tohttp://internal_host/msmq/internal_queue/to /redirection redirection ... /redirection /redirections Does anyone know how to add new redirection node and then 'from' and 'to' nodes and set their values? I know that the script below can create a new node but I can not get to it then. When I try to modify the 'to' and'from' values it changes them in the first redirection node. If I use /redirections/redirection[last()] I get an error. Seems like WIX doesn't fully support XPATH The information contained in this email is intended only for the individual to whom it is addressed. It may contain privileged and/or confidential information. If you have received this message in error please notify the sender immediately and delete the message from your computer. The unauthorised use, disclosure, copying or alteration of this message is forbidden. Neither Vertex Data Science Limited nor any of its subsidiaries will be liable for direct, special, indirect or consequential damage as a result of any virus being passed on, or arising from alteration of the contents of this message by a third party. The following Vertex companies are registered in England and Wales and are authorised and regulated by the Financial Services Authority: Vertex Data Science Limited (company number 3153391); Exchange FS Limited (company number 2596452) trading as The Exchange; Vertex Mortgage Services Limited (company number 2042968); Vertex Administration Limited (company number 2138853); Jessop Fund Managers Limited (company number 5768993). All the above companies have their registered office at Pegasus House, Kings Business Park, Liverpool Road, Prescot, Merseyside, L34 1PJ. www.vertex.co.uk - 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
[WiX-users] Wix multiple installs
Hi I am trying to create WIX install that could be installed multiple times on one machine. To explain myself better I need to be able to install the same application on one computer several times in different locations (there is a good reason for this). Currently every time I install new into a new location it uninstalls the application in the old location and there is only one entry in the instaled application windows (Add or Remove Programs) where I would like to have as many entries as installed applications. I wonder if its possible to do it and if anyone knows how I would appreciate any hints. Regards Daniel The information contained in this email is intended only for the individual to whom it is addressed. It may contain privileged and/or confidential information. If you have received this message in error please notify the sender immediately and delete the message from your computer. The unauthorised use, disclosure, copying or alteration of this message is forbidden. Neither Vertex Data Science Limited nor any of its subsidiaries will be liable for direct, special, indirect or consequential damage as a result of any virus being passed on, or arising from alteration of the contents of this message by a third party. The following Vertex companies are registered in England and Wales and are authorised and regulated by the Financial Services Authority: Vertex Data Science Limited (company number 3153391); Exchange FS Limited (company number 2596452) trading as The Exchange; Vertex Mortgage Services Limited (company number 2042968); Vertex Administration Limited (company number 2138853); Jessop Fund Managers Limited (company number 5768993). All the above companies have their registered office at Pegasus House, Kings Business Park, Liverpool Road, Prescot, Merseyside, L34 1PJ. www.vertex.co.uk - 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
[WiX-users] Are the MSI built with WiX v2 is compatible with Vista/Server 2008?
Hello Community, I'm very new to WiX and have just subscribed to this mailing list. Sorry, if the questions below are stupid. Due to the fact that it is recommended to use WiX v2 for production projects so far, I have a couple of questions: 1) Will the MSI produced by WiX v2 be valid and compatible with Vista/Server 2008 requirements? I mean those defined in Certified For Windows Server 2008 program, for instance. 2) Does the MSI produced by WiX v2 validate against validation packages like Full MSI validation? Thanks. -- Yan - 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
[WiX-users] Click next control event - Prematurely Stopped
Hi, Am using one DLL custom action. This custom action am calling when user clicks next button in xyz.dlg Some machines it is working fine(i.e. opened next dialog) and in some machines immediately it is displaying Prematurely Stopped dialog and installation fails. There is no wrong in dll. Because it is working fine in some OS's. Can any one tell what is the wrong here. Following is the wix code: In dialog - Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=$(loc.WixUINext) Publish Event=DoAction Value=InvChrs1/Publish Publish Event=NewDialog Value=[WixUI_lServicesDlg_Next]SERVICE_INV=Service Name Correct/Publish /Control Custom Action: -- Binary Id=BinInv SourceFile=CustomAction.dll/ CustomAction Id=InvChrs BinaryKey=BinInv DllEntry=Fn_toChkInvalidChars/ -- View this message in context: http://www.nabble.com/Click-next-control-event---Prematurely-Stopped-tp15062166p15062166.html Sent from the wix-users mailing list archive at Nabble.com. - 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 multiple installs
Thanks That is an interesting way to deal with the problem. I understand now how to deal with the problem. Regards Daniel From: Yan Sklyarenko [mailto:[EMAIL PROTECTED] Sent: 24 January 2008 10:51 To: Daniel Hatala; [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix multiple installs Via VBScript custom action: ' open the MSI database of external package Set installer = CreateObject(WindowsInstaller.Installer) path = Session.Property(SETUPEXEDIR) \name.msi Set database = installer.OpenDatabase(path, msiOpenDatabaseModeDirect) ' setting new product code newProductCode = GetNewGUID() insertQuery = UPDATE `Property` SET `Value` = ' newProductCode ' WHERE `Property` = 'ProductCode' Set insertView = database.OpenView(insertQuery) insertView.Execute insertView.Close ' changing the package code set info = database.SummaryInformation(20) info.Property(9) = GetNewGUID() info.Persist ' changing components' IDs ChangeComponentID WebSite, database ChangeComponentID MSSQLDatabases, database ' etc. ' making the changes persistent database.Commit Whereas the ChangeComponentID is defined as follows: 'Helper function: changes the ID for a component Function ChangeComponentID(componentName, database) Dim newComponentID, insertQuery, insertView newComponentID = GetNewGUID() insertQuery = UPDATE `Component` SET `ComponentId` = ' newComponentID ' WHERE `Component` = ' componentName ' Set insertView = database.OpenView(insertQuery) insertView.Execute insertView.Close End Function Hope this helps. -- Yan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, January 24, 2008 12:36 PM To: Yan Sklyarenko; [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix multiple installs Hi Yan I wonder how did you 'patch' the second package with new Guid. Daniel From: Yan Sklyarenko [mailto:[EMAIL PROTECTED] Sent: 24 January 2008 10:32 To: Daniel Janz; Daniel Hatala Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix multiple installs I had the same problem once and here's how I solved it. I split my installation project into 2 projects: the first one is a so-called UI part, the second one is the main project and it actually installs the product. The UI part gathers the information from the user and the target system as usual, then opens the MSI database of the target package, patches it with new GUIDs, starts the main installation as msiexec /I list_of_public_properties and silently closes itself. In such case every time you install your product, from the system point of view it launches a different MSI package each time. I'm not sure if it is the way to go for your case and if it's at all the WiX-like approach. But when I was searching for the solution to this problem, this is the best advice I managed to get. Hope this helps. -- Yan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Janz Sent: Thursday, January 24, 2008 12:05 PM To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix multiple installs I don't think that this is possible because of the GUIDs which would have to be different every time you install the package. Try to build an installer which copies the same files into different locations instead. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Donnerstag, 24. Januar 2008 10:39 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix multiple installs Hi I am trying to create WIX install that could be installed multiple times on one machine. To explain myself better I need to be able to install the same application on one computer several times in different locations (there is a good reason for this). Currently every time I install new into a new location it uninstalls the application in the old location and there is only one entry in the instaled application windows (Add or Remove Programs) where I would like to have as many entries as installed applications. I wonder if its possible to do it and if anyone knows how I would appreciate any hints. Regards Daniel The information contained in this email is intended only for the individual to whom it is addressed. It may contain privileged and/or confidential information. If you have received this message in error please notify the sender immediately and delete the message from your computer. The unauthorised use, disclosure, copying or alteration of this message is forbidden. Neither Vertex Data Science Limited nor any of its subsidiaries will be liable for direct,
Re: [WiX-users] Wix multiple installs
I had the same problem once and here's how I solved it. I split my installation project into 2 projects: the first one is a so-called UI part, the second one is the main project and it actually installs the product. The UI part gathers the information from the user and the target system as usual, then opens the MSI database of the target package, patches it with new GUIDs, starts the main installation as msiexec /I list_of_public_properties and silently closes itself. In such case every time you install your product, from the system point of view it launches a different MSI package each time. I'm not sure if it is the way to go for your case and if it's at all the WiX-like approach. But when I was searching for the solution to this problem, this is the best advice I managed to get. Hope this helps. -- Yan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Janz Sent: Thursday, January 24, 2008 12:05 PM To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix multiple installs I don't think that this is possible because of the GUIDs which would have to be different every time you install the package. Try to build an installer which copies the same files into different locations instead. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Donnerstag, 24. Januar 2008 10:39 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix multiple installs Hi I am trying to create WIX install that could be installed multiple times on one machine. To explain myself better I need to be able to install the same application on one computer several times in different locations (there is a good reason for this). Currently every time I install new into a new location it uninstalls the application in the old location and there is only one entry in the instaled application windows (Add or Remove Programs) where I would like to have as many entries as installed applications. I wonder if its possible to do it and if anyone knows how I would appreciate any hints. Regards Daniel The information contained in this email is intended only for the individual to whom it is addressed. It may contain privileged and/or confidential information. If you have received this message in error please notify the sender immediately and delete the message from your computer. The unauthorised use, disclosure, copying or alteration of this message is forbidden. Neither Vertex Data Science Limited nor any of its subsidiaries will be liable for direct, special, indirect or consequential damage as a result of any virus being passed on, or arising from alteration of the contents of this message by a third party. The following Vertex companies are registered in England and Wales and are authorised and regulated by the Financial Services Authority: Vertex Data Science Limited (company number 3153391); Exchange FS Limited (company number 2596452) trading as The Exchange; Vertex Mortgage Services Limited (company number 2042968); Vertex Administration Limited (company number 2138853); Jessop Fund Managers Limited (company number 5768993). All the above companies have their registered office at Pegasus House, Kings Business Park, Liverpool Road, Prescot, Merseyside, L34 1PJ. www.vertex.co.uk - 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] Bootstrapper and MsiInstallProduct [Solved]
Hello, I've resolved the issue. The problem was that when I installed another executable I had an OpenFile common dialog from which I chose that executable. This file dialog caused the current directory to be changed. I then called MsiInstallProduct with a relative path which failed because the installation file could not be found. What I don't understand here is why MsiInstallProduct returns 0x80004005 here instead of a meaningful error message. If an error occurs later in the setup, the correct error code is returned so I'm ruling out some sort of interop problem here. Anyway, thanks for your help! Kind regards, Henning Krause -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Richard Sent: Thursday, January 24, 2008 4:31 AM To: WiX Users Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct In article [EMAIL PROTECTED], Krause, Henning [EMAIL PROTECTED] writes: the order is this: 1. Call calc.exe 2. Call MsiEnableLog 3. Call MsiInstallProduct. MsiInstallProduct then returns E_FAIL. MSI functions don't return HRESULTs, so it doesn't return E_FAIL. How are you calling MSI functions through interop? i.e. custom p/invoke, some wrapper library, what? -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ --- -- 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 - 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] Click next control event - Prematurely Stopped
Maybe elaborate a little bit more on 'working fine in some OS's' (which do work?) and what the Custom Action is trying to do? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of SaiTeja Sent: donderdag 24 januari 2008 11:20 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Click next control event - Prematurely Stopped Hi, Am using one DLL custom action. This custom action am calling when user clicks next button in xyz.dlg Some machines it is working fine(i.e. opened next dialog) and in some machines immediately it is displaying Prematurely Stopped dialog and installation fails. There is no wrong in dll. Because it is working fine in some OS's. Can any one tell what is the wrong here. Following is the wix code: In dialog - Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=$(loc.WixUINext) Publish Event=DoAction Value=InvChrs1/Publish Publish Event=NewDialog Value=[WixUI_lServicesDlg_Next]SERVICE_INV=Service Name Correct/Publish /Control Custom Action: -- Binary Id=BinInv SourceFile=CustomAction.dll/ CustomAction Id=InvChrs BinaryKey=BinInv DllEntry=Fn_toChkInvalidChars/ -- View this message in context: http://www.nabble.com/Click-next-control-event---Prematurely-Stopped-tp1 5062166p15062166.html Sent from the wix-users mailing list archive at Nabble.com. - 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 This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - 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
[WiX-users] Forcing the usage of the Bootstrapper instead of MSI
Hi, I generated a bootstrapper using the msistuff.exe SDK tool and now we want to force the user to launch the installler only from the bootstrapper (not by executing the MSI). Is there any chance to achieve this? Thanks! -Adrian - 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] Forcing the usage of the Bootstrapper instead of MSI
There has been a previous thread on this which I copied for your convenience Subject: Re: [WiX-users] Make User Run exe when the msi is run If the issue is that your Launch Condition prevents an uninstall, then you probably need your LaunchConditions to be performed only on an install. In your UI sequence and your Execute sequence, put a condition of Not Installed on the LaunchConditions action. Visual Studio setups do this by default, probably to stop people getting into the situation that you've got, even though launch conditions can be useful for uninstall conditions too. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig0ss Sent: Friday, September 21, 2007 3:27 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Make User Run exe when the msi is run HI there Basically i have had to take this conditon out for the mean time as its not allowign the uninstall of the product using the add remove programs feature. If there is any information on this i would be greatfull, i have read the below article and im still none the wiser. I need to be able to only install the product from the exe (No msi install) and i need to be able to un-install from the add remove programs from control panel without the procedure being canceled because the code for the exe Hoep that makes sence Rob Mensching-2 wrote: I talk through this problem here: http://blogs.msdn.com/robmen/archive/2006/08/22/712812.aspx http://blogs.msdn.com/robmen/archive/2006/08/22/712812.aspx -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig0ss Sent: Thursday, September 20, 2007 07:30 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Make User Run exe when the msi is run hi there I have now got this working fine, however i now have a problem on uninstall. When i go to add remove programs and try to uninstall my app from there, the app trys to start the .msi and obviously that wont work because of the launch conditonm i get the error Please run from the exe which is the error msg that i put in for when a user trys to load the program from the msi and not the exe So now i need to know how to put another condition to do with this to make the add remove programs use the installer exe and not the msi Any ideas Thank you Rob Hamflett wrote: I'm not familiar with whatever product you're using for the bootstrapper, sorry. Does the GenerateBootstrapper element really not have an Arguments value, or something similar? Rob Craig0ss wrote: Right then Basically the below code worked when run from a command line //..//..//setup.exe RUNFROMEXE=1 this works fine However i need this done automaticaly when the end user runs the setup.exe from a GUI Below is the code to the bootstrapper that im using and any help on the argument code and where to put it would be very welcome Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003 http://schemas.microsoft.com/developer/msbuild/2003 PropertyGroup AppFileFullPathC:\Projects\BuildStuff\Installer\Optisoft.msi/AppFileF ullPath /PropertyGroup ItemGroup BootstrapperFile Include=Microsoft.Net.Framework.2.0 ProductName.NET Framework 2.0/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.Data.Access.Components.2.8 ProductNameMicrosoft Data Access Components 2.8/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.Windows.Installer.3.1 ProductNameWindows Installer 3.1/ProductName /BootstrapperFile BootstrapperFile Include=MSJet35 ProductNameMSJet35/ProductName /BootstrapperFile BootstrapperFile Include=VB6Runtime ProductNameVB6Runtime/ProductName /BootstrapperFile /ItemGroup Target Name=Bootstrapper GenerateBootstrapper ApplicationFile=optisoft.msi ApplicationName=Optisoft Enteprise BootstrapperItems=@(BootstrapperFile) ComponentsLocation=Relative Culture=en FallbackCulture=en-GB CopyComponents=True Validate=False OutputPath=C:\Projects\BuildStuff\Installer\Bootstrapper\output\ / /Target /Project Thanks - 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/ http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net mailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to link to WiXUIExtension.dll - Light.exe exited with code 92
Hello, I have tried to build some test example setup project to test GUI and my CustomActionDLL. I have done something similar to wxs file presented at http://www.wixwiki.com/index.php?title=Simple_Custom_Action_Dll. But after build I have gotten in Visual Studio 2005: Error 1 Light.exe exited with code 92.C:\Program Files\MSBuild\Microsoft\WiX\v3.0\Wix.targets11226 WixSampleDllCA I have also tried to build in WiXEdit, but unfortunatelly WiXEdit does not use project files and it presents error that are caused by not linked WiXUIExtension.dll. How to force WiXUIExtension.dll linking outside Visual Studio, for example from command line? WiXEdit has much more familiar error presentation than that in VS (where if I click the Wix.targets file is opened instead of pointing the line in wxs file where error is expected - as it is in WiXEdit). Best regards, Peter Jaworski - 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] Get rid of distracting 'run from the network' installation in the root feature
I suspected that. Alas, I was hoping there was some obsecure trivia that I was missing that could mitigate the bisbehaving control. Bob Arnson [EMAIL PROTECTED] wrote: Christopher Painter wrote: Right, I'm familiar with MenuLocal and MenuAllLocal. The problem is consider this feature tree A (root) B Parent A MenuLocal and MenuAllLocal is displayed by my selection tree for both features. The annoyance is that B doesn't have any child features so I don't know why ( or how to stop ) the control from displaying the ManuAllLocal string. The string is correct however in the context of feature A. Is this just one of those MSI annoyances? Yes, that's the SelectionTree control. -- sig://boB http://joyofsetup.com/ - Looking for last minute shopping deals? Find them fast with Yahoo! Search.- 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 multiple installs
Actually this is possible with multiple instance transforms if you follow a few simple design guides. I discuss it in detail on my blog.InstallShield has custom tables to teach the build engine to generate and embed these tables and I've recently written some XML driven custom automation to allow you to generate and embed the transforms into packages made by other tools sets. If WiX doesn't have an element to describe this story you could use my automation until it does. Daniel Janz [EMAIL PROTECTED] wrote: I dont think that this is possible because of the GUIDs which would have to be different every time you install the package. Try to build an installer which copies the same files into different locations instead. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Donnerstag, 24. Januar 2008 10:39 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix multiple installs Hi I am trying to create WIX install that could be installed multiple times on one machine. To explain myself better I need to be able to install the same application on one computer several times in different locations (there is a good reason for this). Currently every time I install new into a new location it uninstalls the application in the old location and there is only one entry in the instaled application windows (Add or Remove Programs) where I would like to have as many entries as installed applications. I wonder if its possible to do it and if anyone knows how I would appreciate any hints. Regards Daniel The information contained in this email is intended only for the individual to whom it is addressed. It may contain privileged and/or confidential information. If you have received this message in error please notify the sender immediately and delete the message from your computer. The unauthorised use, disclosure, copying or alteration of this message is forbidden. Neither Vertex Data Science Limited nor any of its subsidiaries will be liable for direct, special, indirect or consequential damage as a result of any virus being passed on, or arising from alteration of the contents of this message by a third party. The following Vertex companies are registered in England and Wales and are authorised and regulated by the Financial Services Authority: Vertex Data Science Limited (company number 3153391); Exchange FS Limited (company number 2596452) trading as The Exchange; Vertex Mortgage Services Limited (company number 2042968); Vertex Administration Limited (company number 2138853); Jessop Fund Managers Limited (company number 5768993). All the above companies have their registered office at Pegasus House, Kings Business Park, Liverpool Road, Prescot, Merseyside, L34 1PJ. www.vertex.co.uk - 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 - Never miss a thing. Make Yahoo your homepage.- 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 multiple installs
That is very `interesting`, but I'd really suggest that you read this article
first:
http://msdn2.microsoft.com/en-us/library/aa369523(VS.85).aspx
http://msdn2.microsoft.com/en-us/library/aa367797(VS.85).aspx
http://msdn2.microsoft.com/en-us/library/aa369528(VS.85).aspx
http://blog.deploymentengineering.com/2006/10/multiple-instance-msis-and.html
[EMAIL PROTECTED] wrote:
v\:* { BEHAVIOR: url(#default#VML) } o\:* { BEHAVIOR:
url(#default#VML) } w\:* { BEHAVIOR: url(#default#VML) } .shape {
BEHAVIOR: url(#default#VML) } st1\:* { BEHAVIOR: url(#default#ieooui)
} @font-face { font-family: Tahoma; } @font-face { font-family:
Calibri; } @font-face { font-family: Consolas; } @font-face {
font-family: Trebuchet MS; } @page Section1 {size: 612.0pt 792.0pt; margin:
72.0pt 72.0pt 72.0pt 72.0pt; } A:link { mso-style-priority: 99 }
SPAN.MSOHYPERLINK { mso-style-priority: 99 } A:visited {
mso-style-priority: 99 } SPAN.MSOHYPERLINKFOLLOWED { mso-style-priority: 99
} P { mso-style-priority: 99 } PRE { mso-style-priority: 99 }
SPAN.HTMLPREFORMATTEDCHAR { mso-style-priority: 99 } P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Times New Roman }
LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Times New
Roman } DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Times New Roman }
A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: purple;
TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: purple;
TEXT-DECORATION: underline } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0cm;
MARGIN-RIGHT: 0cm; FONT-FAMILY: Times New Roman; mso-margin-top-alt: auto;
mso-margin-bottom-alt: auto } PRE { FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt;
FONT-FAMILY: Courier New } SPAN.htmlpreformattedchar { FONT-FAMILY:
Consolas } SPAN.EmailStyle20 { COLOR: #1f497d; FONT-FAMILY: Calibri;
mso-style-type: personal } SPAN.EmailStyle21 { COLOR: navy; FONT-FAMILY:
Arial; mso-style-type: personal } SPAN.EmailStyle22 { COLOR: navy;
FONT-FAMILY: Arial; mso-style-type: personal-reply } DIV.Section1 { page:
Section1 } Thanks
That is an interesting way to deal with the problem. I understand now how to
deal with the problem.
Regards
Daniel
-
From: Yan Sklyarenko [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 10:51
To: Daniel Hatala; [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix multiple installs
Via VBScript custom action:
open the MSI database of external package
Set installer = CreateObject(WindowsInstaller.Installer)
path = Session.Property(SETUPEXEDIR) \name.msi
Set database = installer.OpenDatabase(path, msiOpenDatabaseModeDirect)
setting new product code
newProductCode = GetNewGUID()
insertQuery = UPDATE `Property` SET `Value` = ' newProductCode ' WHERE
`Property` = 'ProductCode'
Set insertView = database.OpenView(insertQuery)
insertView.Execute
insertView.Close
' changing the package code
set info = database.SummaryInformation(20)
info.Property(9) = GetNewGUID()
info.Persist
changing components IDs
ChangeComponentID WebSite, database
ChangeComponentID MSSQLDatabases, database
etc.
making the changes persistent
database.Commit
Whereas the ChangeComponentID is defined as follows:
'Helper function: changes the ID for a component
Function ChangeComponentID(componentName, database)
Dim newComponentID, insertQuery, insertView
newComponentID = GetNewGUID()
insertQuery = UPDATE `Component` SET `ComponentId` = ' newComponentID
' WHERE `Component` = ' componentName '
Set insertView = database.OpenView(insertQuery)
insertView.Execute
insertView.Close
End Function
Hope this helps.
-- Yan
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 24, 2008 12:36 PM
To: Yan Sklyarenko; [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix multiple installs
Hi Yan
I wonder how did you 'patch' the second package with new Guid.
Daniel
-
From: Yan Sklyarenko [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 10:32
To: Daniel Janz; Daniel Hatala
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix multiple installs
I had the same problem once and heres how I solved it.
I split my installation project into 2 projects: the first one is a so-called
UI part, the second one is the main project and it actually installs the
product.
The UI part gathers the information from the user and the target system as
usual, then opens the MSI database
Re: [WiX-users] Are the MSI built with WiX v2 is compatible with Vista/Server 2008?
I'm very new to WiX and have just subscribed to this mailing list. Sorry, if the questions below are stupid. Due to the fact that it is recommended to use WiX v2 for production projects so far, I have a couple of questions: 1) Will the MSI produced by WiX v2 be valid and compatible with Vista/Server 2008 requirements? I mean those defined in Certified For Windows Server 2008 program, for instance. 2) Does the MSI produced by WiX v2 validate against validation packages like Full MSI validation? Yes, WiX V2 can be used to create Certified For packages. We use WiX V2 and we are Certified for Vista. We haven't gotten certified for 2008 yet but, I don't anticipate a problem. - 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] Click next control event - Prematurely Stopped
Am using one DLL custom action. (..) There is no wrong in dll. Because it is working fine in some OS's. Tell us something more about DLL, especially what kind of DLL is it (MFC, COM, .net...). How it is linked. It may need some runtimes that cause that on some installations it works (because libraries or runtimes are present) and on other it does not Best regards, Piotr Jaworski - 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 multiple installs
The UI part gathers the information from the user and the target system as usual, then opens the MSI database of the target package, patches it with new GUIDs, starts the main installation as msiexec /I list_of_public_properties and silently closes itself. In such case every time you install your product, from the system point of view it launches a different MSI package each time. I'm not sure if it is the way to go for your case and if it's at all the WiX-like approach. But when I was searching for the solution to this problem, this is the best advice I managed to get. I have just thought the same, the use of setup bootstrapper that patches the MSI on the fly is, I think, a good solution. Similar as when preparing multilanguage support. As described here: http://www.tramontana.co.hu/wix/lesson9.php. You have to, in some how, modify/change update code so the Windows Installer will think it as a setup of other application and install the same application next to prevously installed. Best regards, Peter Jaworski - 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] How to link to WiXUIExtension.dll - Light.exe exited with code 92
Peter Jaworski wrote: I have tried to build some test example setup project to test GUI and my CustomActionDLL. I have done something similar to wxs file presented at http://www.wixwiki.com/index.php?title=Simple_Custom_Action_Dll. But after build I have gotten in Visual Studio 2005: Error 1 Light.exe exited with code 92.C:\Program Files\MSBuild\Microsoft\WiX\v3.0\Wix.targets 11226 WixSampleDllCA 92 is a duplicate symbol error. Build outside of VS to get a more detailed error message. -- sig://boB http://joyofsetup.com/ - 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] Installing 2 files w/same filename from diff features breaks ICE30?
Chris Weiss wrote: Ahh - thanks!. What's the syntax for attaching a condition directly to a component? Use a child Condition element. -- sig://boB http://joyofsetup.com/ - 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] 32-bit and 64-bit MSIs bundled in single EXE
Kevin Richardson wrote: It looks like the current bootstrapper calls msiexec.exe, rather than using the APIs. I inherited the code and it looks like it was done that way to make it convenient to pass command line arguments, among other things. If I continue to call the executable, I assume that I'll need to choose the correct msiexec.exe (system32 for 64-bit on x64, syswow64 for 32-bit on x64, system32 on 32-bit), or can x64's system32\msiexec install 32-bit MSIs? Either way will work. In both cases, MSI will kick off an msiexec server and custom action servers of the right bitness based on the package and CA type. -- sig://boB http://joyofsetup.com/ - 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
[WiX-users] Unchecked features in un upgraded MSI
Hi, I'm creating an upgrade for an existent product and I need to add a few new *optional* features that didn't exist in the original one. I want the new features appear checked in the feature tree by default. The only way we found to achieve this is by defining the Allow=Disallow attribute in the feature but this won't allow the user to uncheck the feature. Any ideas? Thanks, -Adrian - 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
[WiX-users] CNDL1024 error using include files
I'm getting the following error... candle.exe : error CNDL0124 : An error has occurred that most likely indicates that the .NET Framework 1.1 Service Pack 1 has not been installed. Please see the following website for more information about the service pack and how to install it: http://support.microsoft.com/?kbid=867460 I'm working with including files into my main wxs file and my most recent change was to create a wxi with my directory definitions and then use directoryref around my component wxi files. Is there an issue with directoryref and include files that would throw this type of error? - 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] Bootstrapper and MsiInstallProduct [Solved]
MsiInstallProduct *DOESN'T* return 0x80004005 for a missing MSI file. It returns ERROR_FILE_NOT_FOUND (2) if the file isn't found and ERROR_PATH_NOT_FOUND (3) if the path does not exist. This goes back to Richard's question, which (paraphrased) is how the heck are you calling MsiInstallProduct? If you have an Interop problem it's perhaps because you decided to import msi.dll and you're using COM interfaces that were really intended only for late-binding (like VBScript). Using P/Invoke with one of the many wrappers (like Richard's) is much more reliable. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Krause, Henning Sent: Thursday, January 24, 2008 2:30 AM To: Richard; WiX Users Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct [Solved] Hello, I've resolved the issue. The problem was that when I installed another executable I had an OpenFile common dialog from which I chose that executable. This file dialog caused the current directory to be changed. I then called MsiInstallProduct with a relative path which failed because the installation file could not be found. What I don't understand here is why MsiInstallProduct returns 0x80004005 here instead of a meaningful error message. If an error occurs later in the setup, the correct error code is returned so I'm ruling out some sort of interop problem here. Anyway, thanks for your help! Kind regards, Henning Krause -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Richard Sent: Thursday, January 24, 2008 4:31 AM To: WiX Users Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct In article [EMAIL PROTECTED], Krause, Henning [EMAIL PROTECTED] writes: the order is this: 1. Call calc.exe 2. Call MsiEnableLog 3. Call MsiInstallProduct. MsiInstallProduct then returns E_FAIL. MSI functions don't return HRESULTs, so it doesn't return E_FAIL. How are you calling MSI functions through interop? i.e. custom p/invoke, some wrapper library, what? -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ --- -- 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 - 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 - 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] CNDL1024 error using include files
The preprocessor code returns this error if any XmlException occurs when loading the document after it has been preprocessed. One source of problems as I recall is that the XML namespaces used in the include file aren't 'hoisted' into the including document. Ensure that all namespaces used in the include file are explicitly listed in the document which includes it. Presumably not having .NET Framework 1.1 Service Pack 1 also tended to cause XmlExceptions at this point, but it's certainly not the only possible reason. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta (Volt) Sent: 24 January 2008 19:10 To: wix-users@lists.sourceforge.net Subject: [WiX-users] CNDL1024 error using include files I'm getting the following error. candle.exe : error CNDL0124 : An error has occurred that most likely indicates that the .NET Framework 1.1 Service Pack 1 has not been installed. Please see the following website for more information about the service pack and how to install it: http://support.microsoft.com/?kbid=867460 I'm working with including files into my main wxs file and my most recent change was to create a wxi with my directory definitions and then use directoryref around my component wxi files. Is there an issue with directoryref and include files that would throw this type of error? - 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
[WiX-users] Merge Module Custom Actions
Hello, I've got a few merge modules generated with Wix that have custom actions included in them. I'd like to populate the ModuleInstallExecuteSequence table to generically schedule them. Any ideas on accomplishing this? I looked through all the children of Module element and I'm not seeing anything that can get me there. Thanks, Tom - 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] Merge Module Custom Actions
Use InstallExecuteSequence. WiX generates ModuleInstallExecuteSequence table entries if you're building a merge module. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare Sent: 24 January 2008 22:26 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Merge Module Custom Actions Hello, I've got a few merge modules generated with Wix that have custom actions included in them. I'd like to populate the ModuleInstallExecuteSequence table to generically schedule them. Any ideas on accomplishing this? I looked through all the children of Module element and I'm not seeing anything that can get me there. Thanks, Tom - 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] Bootstrapper and MsiInstallProduct [Solved]
In article [EMAIL PROTECTED], Wilson, Phil [EMAIL PROTECTED] writes: MsiInstallProduct *DOESN'T* return 0x80004005 for a missing MSI file. It retu rns ERROR_FILE_NOT_FOUND (2) if the file isn't found and ERROR_PATH_NOT_FOUND ( 3) if the path does not exist. This goes back to Richard's question, which (par aphrased) is how the heck are you calling MsiInstallProduct? I think the translation to E_FAIL was in his own homebrew interop layer. That's why I suggested using my interop layer as it doesn't substitute any error values from what is returned from MSI. All errors turn into exceptions with the appropriate error code. -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - 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
[WiX-users] Checking out release sources.
Hi all, When a release is made is a corresponding tag made in CVS so we can get the sources corresponding to that release? I can't seem to find one way or the other. Currently I'm working from the date of the corresponding wix/history.txt file. Thanks, Luke - 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] Click next control event - Prematurely Stopped
Thanks for responses. I created DLL in MicroSoft Visual Studio and the type of file is Application Extension Please find uploadfile for the DLL. http://www.nabble.com/file/p15081184/invdll.txt invdll.txt and following is wix code In dialog - Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=$(loc.WixUINext) Publish Event=DoAction Value=InvChrs1/Publish Publish Event=NewDialog Value=[WixUI_lServicesDlg_Next]SERVICE_INV=Service Name Correct/Publish /Control Custom Action: -- Binary Id=BinInv SourceFile=CustomAction.dll/ CustomAction Id=InvChrs BinaryKey=BinInv DllEntry=Fn_toChkInvalidChars/ Thanks Peter Jaworski wrote: Am using one DLL custom action. (..) There is no wrong in dll. Because it is working fine in some OS's. Tell us something more about DLL, especially what kind of DLL is it (MFC, COM, .net...). How it is linked. It may need some runtimes that cause that on some installations it works (because libraries or runtimes are present) and on other it does not Best regards, Piotr Jaworski - 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 -- View this message in context: http://www.nabble.com/Click-next-control-event---Prematurely-Stopped-tp15062166p15081184.html Sent from the wix-users mailing list archive at Nabble.com. - 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] How to link to WiXUIExtension.dll - Light.exe exited with code 92
On Jan 24, 2008 4:21 PM, Bob Arnson [EMAIL PROTECTED] wrote: Peter Jaworski wrote: I have tried to build some test example setup project to test GUI and my CustomActionDLL. I have done something similar to wxs file presented at http://www.wixwiki.com/index.php?title=Simple_Custom_Action_Dll. But after build I have gotten in Visual Studio 2005: Error 1 Light.exe exited with code 92.C:\Program Files\MSBuild\Microsoft\WiX\v3.0\Wix.targets 11226 WixSampleDllCA 92 is a duplicate symbol error. Build outside of VS to get a more detailed error message. OK, I have solve this error just after sending that e-mail. Thank you for error description. Is there any table with errors' numbers and its descriptions? This debugging feature for WiX project under VS is not usefull. I have still problem with WiXUIExtension.dll referencing outside VS (because not using WiX project) and I have to comment lines that are refered to WiXUIExtension.dll features to compile it outside VS. How to solve this? Is there any command line attribute for candle or light (both in v2 and v3)? Thank you, ones more for your current help. Best regards, Peter Jaworski - 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
