[WiX-users] Wix doesn't recognize USB drive or other removable storage
We use Wix 3.0. Some of our customers complain that the installer doesn't recognize USB drive or other removable storage when installing. So basically, in "Destination Folder" page, the end user tried to change the install folder to a USB drive. But there is no USB drive showing up in drop-down list. When the end user tried to change the folder from "Folder name:" field, she got an error says: Installation directory must be on a local hard drive. I did some research and found this is not a Wix limitation, but MSI's. So my questions are: 1. Is there a way to get rid of it? I think it makes sense to allow the end user to install the software on their portable devices. 2. What's the purpose of this limitation? Security? I understand this is probably MSI's limitation. But if you happen to know the reason, please help me understand it. Thanks! -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to NOT Delete Application Directory on Uninstall?
Hi Joseph, Let's first make sure we use correct terminology. Wix is a tool to create MSI installers. MSI installer installs, upgrades and uninstalls products and while doing that, it also creates/deletes folders among numerous other things. One thing you can use to solve your problem is the fact that MSI will not delete non-empty folder. So, your installer (or installed application on the first run) can create (not install) a file in the folder you want to keep during upgrade. To be able to delete folder on uninstall (not upgrade) you can schedule custom action to remove the file. Keep in mind that during uninstall (both upgrade and regular uninstall) property REMOVE will have value ALL (REMOVE=ALL) and property UPGRADINGPRODUCTCODE will exist only if product is removed during upgrade. So, your extra file removal custom action should be scheduled as REMOVE=ALL AND NOT UPGRADINGPRODUCTCODE. Alex -Original Message- From: Joseph B. Kowalski [mailto:jkowal...@greendotcorp.com] Sent: Friday, May 07, 2010 10:22 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to NOT Delete Application Directory on Uninstall? Hi all, My apologies if this is already answered somewhere, but I couldn't find an answer. My question is: How can I setup a Wix installer to NOT delete the application directory on uninstall (even when the directory was initially created by the Wix install)? Some background: Let's say we have a Wix installer that installs an app in "C:\Dir1\Dir2". Well, the general behavior seems to be this: - If "Dir2" doesn't already exist when the install happens, it will obviously be created at install time (along with "Dir1" as well, if necessary). - If the "C:\Dir1\Dir2" path already exists at install time, then obviously it doesn't need to be created, and Wix will just install the necessary files underneath the path. - On uninstall, if Wix had to create the "Dir2" directory at install time, it will also remove the "Dir2" directory (unless there are other stray files there, of course). - On uninstall, if Wix DID NOT create the "Dir2" directory at install time (the path already existed), then it seems that Wix WILL NOT remove the "Dir2" directory. In summary, on uninstall Wix will remove whatever part of the directory tree it created at install time, assuming nothing else has placed other content there since the install. This behavior is very logical and makes sense. The problem comes in when you have a situation like this: - Let's say that after installing the above example app, we set some custom NTFS permissions on the "C:\Dir1\Dir2" folder. - Let's also say that when we installed the app, the "C:\Dir1\Dir2" path didn't exist, so the install created it. The problem now is that when we go to re-install this app (upgrading to a newer version of the app), when the uninstall portion of the install runs, it will remove the "Dir2" directory, and then re-add it when it gets to the "install" part, losing the custom NTFS permissions that were set. What can I do to ensure that "Dir2" NEVER gets deleted when installing an newer version of the app (whether or not Wix initially created the directory at install time) so that the NTFS permissions of the directory are preserved through upgrades? If this is impossible, I guess a secondary question would be: How can I enumerate the NTFS permissions of the existing folder before the uninstall happens, and then re-apply those same permissions after the directory is re-created? (although I'd much opt for the first solution) Any help is greatly appreciated. Thank you. Joe -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to NOT Delete Application Directory on Uninstall?
I don't know of any explicit setting to change this default behavior in Windows Installer. The best way to handle it would probably be to have the install manage configuring the permissions on the directory. There is some native permissions options in Windows Installer but they are not very robust. I typically use custom actions to configure any permissions in installs. Although not ideal, you could also force the directory to remain on uninstall by installing a file to that directory that isn't managed by Windows Installer by either adding a dummy file component with a null component GUID or by creating a dummy file during the install via a custom action. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-NOT-Delete-Application-Directory-on-Uninstall-tp5020438p5020595.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to NOT Delete Application Directory on Uninstall?
Hi all, My apologies if this is already answered somewhere, but I couldn't find an answer. My question is: How can I setup a Wix installer to NOT delete the application directory on uninstall (even when the directory was initially created by the Wix install)? Some background: Let's say we have a Wix installer that installs an app in "C:\Dir1\Dir2". Well, the general behavior seems to be this: - If "Dir2" doesn't already exist when the install happens, it will obviously be created at install time (along with "Dir1" as well, if necessary). - If the "C:\Dir1\Dir2" path already exists at install time, then obviously it doesn't need to be created, and Wix will just install the necessary files underneath the path. - On uninstall, if Wix had to create the "Dir2" directory at install time, it will also remove the "Dir2" directory (unless there are other stray files there, of course). - On uninstall, if Wix DID NOT create the "Dir2" directory at install time (the path already existed), then it seems that Wix WILL NOT remove the "Dir2" directory. In summary, on uninstall Wix will remove whatever part of the directory tree it created at install time, assuming nothing else has placed other content there since the install. This behavior is very logical and makes sense. The problem comes in when you have a situation like this: - Let's say that after installing the above example app, we set some custom NTFS permissions on the "C:\Dir1\Dir2" folder. - Let's also say that when we installed the app, the "C:\Dir1\Dir2" path didn't exist, so the install created it. The problem now is that when we go to re-install this app (upgrading to a newer version of the app), when the uninstall portion of the install runs, it will remove the "Dir2" directory, and then re-add it when it gets to the "install" part, losing the custom NTFS permissions that were set. What can I do to ensure that "Dir2" NEVER gets deleted when installing an newer version of the app (whether or not Wix initially created the directory at install time) so that the NTFS permissions of the directory are preserved through upgrades? If this is impossible, I guess a secondary question would be: How can I enumerate the NTFS permissions of the existing folder before the uninstall happens, and then re-apply those same permissions after the directory is re-created? (although I'd much opt for the first solution) Any help is greatly appreciated. Thank you. Joe -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Translations for WiX extensions
Would love to include translations for the extensions. Unfortunately,the people contributing right now only seem to read/write/speak English so we're dependent on the help of others. On Fri, May 7, 2010 at 9:20 AM, Yan Sklyarenko wrote: > Hello WiX community, > > I noticed that although WiX dist provides a number of predefined > translations for UI, those translations don't include WiX extensions > (IIsExtension, SqlExtension, etc.) Only en-US.wxl is present in each of > them... > > Does anybody have a translated set of extensions to the same set of > languages as the standard UI is? > WiX devs, are there any plans to have this included into the dist one > day? > > Thanks, > > -- Yan > > > > > -- > > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Translations for WiX extensions
Hello WiX community, I noticed that although WiX dist provides a number of predefined translations for UI, those translations don't include WiX extensions (IIsExtension, SqlExtension, etc.) Only en-US.wxl is present in each of them... Does anybody have a translated set of extensions to the same set of languages as the standard UI is? WiX devs, are there any plans to have this included into the dist one day? Thanks, -- Yan -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] torch.exe help is not very clear
Hello Wix community, The torch.exe help text seems a bit misleading to me. For instance, I was sure I could write something like this: Torch.exe ... -serr abcdef... but I couldn't. And only after looking down in code I realized it should be "-serr a -serr b", etc. Something wrong with me? :) Or worth a wish? -- Yan -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Udgrade example from tutorial doesn't work.
Not sure if it helps but there is an example here: http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrade s.html Neil -Original Message- From: Warloki [mailto:dmytro.vorotynt...@gmail.com] Sent: 07 May 2010 10:00 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Udgrade example from tutorial doesn't work. Hello, I'm trying to handle small, minor and major updates in WiX. I feel sad because it doesn't work for me as it wrote in the tutorial. http://www.tramontana.co.hu/wix/lesson4.php#4.1 I mean this example: http://www.tramontana.co.hu/wix/download.php?file=samples/sampleupgrade. zip&type=application/zip I want to create product version 1.0.0 and prevent it from update itself and be upgrated by product version 1.0.1 (different variants with reinstall all and only changes). Also I want to prevent product version 1.0.1 from downgrading. I read a lot, including "How To: Implement a Major Upgrade In Your Installer" and test a lot. So, I have the same result: properties specified in the UpgradeVersion section of Upgarde sections never becomes set... I can guarantee that I specified right upgrade code for product and Upgarde section. Maybe the conception was changed and I missed something... The main question is: Whatever I write to UpgradeVersion sections, it ignores and product version installs, reinstalls itself and downgrades without errors. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Udgrade-ex ample-from-tutorial-doesn-t-work-tp5018430p5018430.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] transactions in db scripts
So you cannot change schema in a transaction. So unless your installer only updates data, it's not a useful conversation :) How do we go about updating the db? We talk to our customers about their deployment and upgrade strategy and train them. It involves a lot more than clicking the installer button. Regarding backup in the installer: the short answer is just don't do it. It's a lot of work for no tangible benefit. It's best performed by the actual database application. I've seen an installer trying to backup the database before proceeding in an immediate CA, after asking the user. Nobody who knew what a "database" was (nobody sane) wanted to use the feature. The only time it had any benefit was for a small desktop-type applications that used an embedded database (Microsoft Access or SQL Lite). Any kind of SQL Server or "remote" backup is a crapshoot where you need to assume, for example, that the database backup has been configured (which remote path are you going to write a backup to?) and that you have permissions to execute a backup (most of the time the databases we deploy with MSI are pre-created and the user doesn't get enough permissions to drop the database or do it's backup). cheers -dB. dB. @ dblock.org Moscow|Geneva|Seattle|New York -Original Message- From: lewisv [mailto:le...@nitorco.com] Sent: Friday, May 07, 2010 9:10 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] transactions in db scripts I am wondering about how you guys handle transactions in db upgrade scripts. >From what i have seen sql server, does not allow create/alter/drop functions in transactions unless you have some flags sets. First am i correct with this? Next how do you guys go about updating the db? Should i surround my script with a transaction? I would imagine the transaction will get quite large with db changes etc... Or do i just let the scripts go and assume that they will work. - I am planning on backing up the db before i start the install anyway, so even if it fails we could just overwrite it with the backup ( which would be manual, but at least the db is not in a half upgraded state ) Is there a good clean way to rollback if there is an error with the install? Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/transactions-in-db-scripts-tp5019222p5019222.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] transactions in db scripts
No transaction. Standard operating procedure is that the admin makes a full backup before an update. Point. Admins not doing backups - should be fired. Run the script. Use transactions for small data changes - but nothing else. If something goes wrong, tell the admin to put in his backup ;) Do NOT make automated backups unless your app is small / the data is trivial. A 900gb database is nothing I want an installer to back up by chance ;) Installers should warn (did you do a backup?), then do their business in the database. Roll back - often not possible. Don't bother, so to say ;) Thomas -Original Message- From: lewisv [mailto:le...@nitorco.com] Sent: 07 May 2010 15:10 To: wix-users@lists.sourceforge.net Subject: [WiX-users] transactions in db scripts I am wondering about how you guys handle transactions in db upgrade scripts. >From what i have seen sql server, does not allow create/alter/drop >functions in transactions unless you have some flags sets. First am i correct with this? Next how do you guys go about updating the db? Should i surround my script with a transaction? I would imagine the transaction will get quite large with db changes etc... Or do i just let the scripts go and assume that they will work. - I am planning on backing up the db before i start the install anyway, so even if it fails we could just overwrite it with the backup ( which would be manual, but at least the db is not in a half upgraded state ) Is there a good clean way to rollback if there is an error with the install? Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/transactions-in-db-scripts-tp5019222p5019222.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX and TFS Build
Here's what I'm trying to do: I have two solutions - one for my main application and its associated projects and another for my database (VS .dbproj) and its associated projects. What I'd like to do is include the output from the database project (a .dbschema and some SQL scripts) in my installer (which exists in the main application solution.) This involves having TFS build the DB solution immediately before the main application solution. I've got that part working properly, but I'm having trouble referencing the output of the DB solution from my installer. I'm using relative paths to reference the output in my .wxs file (e.g. ) which works fine locally, but fails when building via TFS build. This is because TFS Build changes the output dir of each project to one common location. Instead of the path to my database project being "..\..\MyDatabaseSolution\MyDatabaseProject\sql\" like it is when building locally, it gets set to something like "..\..\..\Binaries\Release\". How can I get around this and have my WiX project build locally and via TFS? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-and-TFS-Build-tp5019254p5019254.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] transactions in db scripts
I am wondering about how you guys handle transactions in db upgrade scripts. >From what i have seen sql server, does not allow create/alter/drop functions in transactions unless you have some flags sets. First am i correct with this? Next how do you guys go about updating the db? Should i surround my script with a transaction? I would imagine the transaction will get quite large with db changes etc... Or do i just let the scripts go and assume that they will work. - I am planning on backing up the db before i start the install anyway, so even if it fails we could just overwrite it with the backup ( which would be manual, but at least the db is not in a half upgraded state ) Is there a good clean way to rollback if there is an error with the install? Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/transactions-in-db-scripts-tp5019222p5019222.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using web.config transformations in WiX
I agree - this is an oversight in Votive. Here was my workaround: 1) In the wix prebuild, add the following to create the transformed web configs: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe ..\..\..\PathTo\MyWebApp.csproj /t:TransformWebConfig /p:Configuration=$(ConfigurationName) /noconlog /nologo 2) Disable automatic harvesting on My project reference, since Votive doesn't provide a field to specify a transform file (another needed feature). 3) Instead, open the .wixproj file and add the following to call heat: Content;Binaries MyWebTransform.xslt MyWebApp.csproj 4) For reference in this example, my directory structure looks like this: 5) Create the xslt file referenced in step 3. Note, I do a few other things here also: http://www.w3.org/1999/XSL/Transform"; xmlns:wix="http://schemas.microsoft.com/wix/2006/wi";> INSTALLLOCATION BINDIR yes $(var.MyWebApp.ProjectDir)obj\$(var.MyWebApp.Configuration)\TransformWebConfig\transformed\Web.config That's it. When you build, msbuild will transform the webconfig, then heat will use the xslt to point at it properly. Matt Johnson MCPD, MCTS, MCSD, MCDBA Director of Application Development Time America, Inc. ma...@timeamerica.com | www.timeamerica.com -Original Message- From: Rob Jarratt (MCS UK) [mailto:rjarr...@microsoft.com] Sent: Friday, May 07, 2010 12:28 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Using web.config transformations in WiX I would like to make use of the web.config transformations feature in combination with the integration of Heat in VS 2010. I know I can get the transformation output during the build, but if I use the Content project output group then the web.config gets included from the source directory rather than a transformed one. Is there a way to use the project output group and yet replace the web.config with the transformed one? I would also like to find a way to avoid this including the web.config.release and web.config.debug files. Thanks Rob This email may contain confidential information. If you are not named on the addressee list, please take no action in relation to this email, do not open any attachment, and please contact the sender (details above) immediately. Information in this email is provided in good faith. If you are a customer of Microsoft, please refer to the terms and conditions which cover the provision of support and consulting services to you/My organization. If you are not corresponding in the course of, or in connection with a Microsoft contract or programme with its own terms and conditions, please note that no liability is accepted by Microsoft for the contents of this mail. Microsoft Limited (company number 01624297) is a company registered in England and Wales whose registered office is at Microsoft Campus, Thames Valley Park, Reading. RG6 1WG -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Read file content from CA
That's exactly what I did (in C#), and I even used Elmue's cablib:-) It works fine, but it gets a little "heavy" even if I can extract single files without upacking the whole cab. For now I include the files as binary items and read them as such. I didn't come to think of creating a custom table as Yan suggested - I haven't looked much at custom tables, but if I can get it to work in the same way as reading from the binary table I like that approach and think I'll go down that route. Thanks for all your suggestions and input! Regards, Niklas On Thu, May 6, 2010 at 15:45, dB. wrote: > It could make an interesting custom action. > > Microsoft CAB supports extracting files from any source (disk, stream, > memory, etc.). Elmue's cablib ( > http://www.codeproject.com/KB/files/CABCompressExtract.aspx) knows how to > deal with all of it, for example how to extract single files from a CAB > embedded as a resource. You could add an implementation that extracts the > file directly from the embedded CAB in an MSI without extracting the whole > thing first. > > Some C++/C# work required :) > > dB. @ dblock.org > Moscow|Geneva|Seattle|New York > > > -Original Message- > From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com] > Sent: Thursday, May 06, 2010 3:40 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Read file content from CA > > Thanks for your suggestions, but I guess I didn't emphasize enough that I > need to read the file in an _immediate_ custom action, that is, I need to > read it from the installation package before the file gets installed. I > guess there's no easy way to do it, so the way I solved it was to > temporarily extract the embedded cab-file and from there extract the file I > need. A bit cumbersome, but it works. > > Regards, > Niklas > > On Tue, May 4, 2010 at 16:14, dB. wrote: > > > There's a Win32_ReadFile immediate native (C++) CA in > > http://msiext.codeplex.com. It was added in 1.2 which hasn't shipped > yet, > > but is stable - http://msiext.codeplex.com/releases/view/39468. Note > that > > it doesn't support encoding, so only works for ANSI files. > > > > If you're writing a managed CA yourself, well, just read the file with > > StreamReader.ReadToEnd and then set a property with the contents read. > > > > Hope it helps, > > > > -dB. > > > > dB. @ dblock.org > > Moscow|Geneva|Seattle|New York > > > > > > -Original Message- > > From: Niklas Söderberg [mailto:niklas.soderb...@gmail.com] > > Sent: Tuesday, May 04, 2010 8:38 AM > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] Read file content from CA > > > > Is it possible to get the contents of a file from a custom action > (managed > > code)? I know I can get the contents of a binary item, but is it possible > > to > > somehow do the same for a regular file included in the installation > > package? > > I want to do this in an immediate custom action executed in the ui > > sequence. > > > > I'm guessing no since I've searched and googled extensively, in vain, but > > I'm still rather new to wix so perhaps I've missed something. > > > > Thanks, > > Niklas > > > > > -- > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > -- > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Show help file during installation
Creating an installer with loose files is discussed in this thread. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installing -from-embedded-CAB-file-and-Folder-td4743262.html#a4778170 Yes, it's possible to extract files from the binary table using a custom action and I suspect DTF can extract files from an external cab in a custom action too. -Original Message- From: Goran Brcanski [mailto:goran.brcan...@gmail.com] Sent: 07 May 2010 10:52 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Show help file during installation Did you mean to put .chm file in the same folder as msi package, but outside msi package? Is there a way to extract file from msi package? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Show-help- file-during-installation-tp5013146p5018587.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users http://www.sdl.com";>http://www.sdl.com/images/email logo_150dpi-01.png" alt="www.sdl.com" border="0"/> http://www.sdl.com"; style="color:005740; font-weight: bold">www.sdl.com SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Show help file during installation
Did you mean to put .chm file in the same folder as msi package, but outside msi package? Is there a way to extract file from msi package? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Show-help-file-during-installation-tp5013146p5018587.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Udgrade example from tutorial doesn't work.
Code samples would help us help you. Also that tutorial refers to Major Upgrades. Small Updates & Minor Upgrades are built, shipped & applied in a different manner. See -> http://msdn.microsoft.com/en-us/library/aa370579.aspx Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Warloki [mailto:dmytro.vorotynt...@gmail.com] Sent: 07 May 2010 10:00 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Udgrade example from tutorial doesn't work. Hello, I'm trying to handle small, minor and major updates in WiX. I feel sad because it doesn't work for me as it wrote in the tutorial. http://www.tramontana.co.hu/wix/lesson4.php#4.1 I mean this example: http://www.tramontana.co.hu/wix/download.php?file=samples/sampleupgrade. zip&type=application/zip I want to create product version 1.0.0 and prevent it from update itself and be upgrated by product version 1.0.1 (different variants with reinstall all and only changes). Also I want to prevent product version 1.0.1 from downgrading. I read a lot, including "How To: Implement a Major Upgrade In Your Installer" and test a lot. So, I have the same result: properties specified in the UpgradeVersion section of Upgarde sections never becomes set... I can guarantee that I specified right upgrade code for product and Upgarde section. Maybe the conception was changed and I missed something... The main question is: Whatever I write to UpgradeVersion sections, it ignores and product version installs, reinstalls itself and downgrades without errors. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Udgrade-ex ample-from-tutorial-doesn-t-work-tp5018430p5018430.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Udgrade example from tutorial doesn't work.
Hello, I'm trying to handle small, minor and major updates in WiX. I feel sad because it doesn't work for me as it wrote in the tutorial. http://www.tramontana.co.hu/wix/lesson4.php#4.1 I mean this example: http://www.tramontana.co.hu/wix/download.php?file=samples/sampleupgrade.zip&type=application/zip I want to create product version 1.0.0 and prevent it from update itself and be upgrated by product version 1.0.1 (different variants with reinstall all and only changes). Also I want to prevent product version 1.0.1 from downgrading. I read a lot, including "How To: Implement a Major Upgrade In Your Installer" and test a lot. So, I have the same result: properties specified in the UpgradeVersion section of Upgarde sections never becomes set... I can guarantee that I specified right upgrade code for product and Upgarde section. Maybe the conception was changed and I missed something... The main question is: Whatever I write to UpgradeVersion sections, it ignores and product version installs, reinstalls itself and downgrades without errors. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Udgrade-example-from-tutorial-doesn-t-work-tp5018430p5018430.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hide InstallDirDlg during upgrade
I got it working. I was using a wrong path in the RegistrySearch =) - Andy MSI Developer Schneider Electric -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-InstallDirDlg-during-upgrade-tp5014310p5018298.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using web.config transformations in WiX
I would like to make use of the web.config transformations feature in combination with the integration of Heat in VS 2010. I know I can get the transformation output during the build, but if I use the Content project output group then the web.config gets included from the source directory rather than a transformed one. Is there a way to use the project output group and yet replace the web.config with the transformed one? I would also like to find a way to avoid this including the web.config.release and web.config.debug files. Thanks Rob This email may contain confidential information. If you are not named on the addressee list, please take no action in relation to this email, do not open any attachment, and please contact the sender (details above) immediately. Information in this email is provided in good faith. If you are a customer of Microsoft, please refer to the terms and conditions which cover the provision of support and consulting services to you/your organization. If you are not corresponding in the course of, or in connection with a Microsoft contract or programme with its own terms and conditions, please note that no liability is accepted by Microsoft for the contents of this mail. Microsoft Limited (company number 01624297) is a company registered in England and Wales whose registered office is at Microsoft Campus, Thames Valley Park, Reading. RG6 1WG -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper sequence in wix
Arun Perregatturv, I have resolved this problem by modifying product.xml file in bootstrapper folder. I think following steps will help you to resolve your problem. you have used .NET Framework 3.5 for .NET Framework 3.5 as prerequisite. Crystal Reports 10 Runtime depends on .NET Framework 3.5. So you have to modify section of the product.xml file in "Crystal Reports 10 Runtime" package folder with Which will maintain your desired order list. This is only preserve your order list for 2. .NET 35 SP1 3. Crystal Reports 10 Runtime You can do for others in this way. N.B: Code="Microsoft.Net.Framework.3.5.SP1" attribute value of section will be same as Include="Microsoft.Net.Framework.3.5.SP1" attribute value of section to retain installation sequence. Thanks Md. Rasel Uddin Arun Perregatturv wrote: > > Strange, no one has complained about this? > Well, I guess it's something to do with Visual Studio 2008. > > > Arun Perregattur > > -Original Message- > From: Bob Arnson [mailto:b...@joyofsetup.com] > Sent: Friday, November 27, 2009 6:42 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Bootstrapper sequence in wix > > Arun Perregatturv wrote: >> I am having problem setting the bootstrapper sequence >> > > That's not a part of WiX. You might want to post to a .NET Framework > newsgroup, as it's the source of the bootstrapper. > > -- > sig://boB > http://joyofsetup.com/ > > > > -- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://old.nabble.com/Bootstrapper-sequence-in-wix-tp26481799p28482716.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hide InstallDirDlg during upgrade
Okie I removed the custom actions. Now When after I launch the MSI, when the UI tries to set the WIXUI_INSTALLDIR path with indirect="yes", it says specified path is empty I have also tried hard cording the property value say C:\Orange Please help - Andy MSI Developer Schneider Electric -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Hide-InstallDirDlg-during-upgrade-tp5014310p5018089.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
