Re: [WiX-users] Per-User Previlage To Write to Program Files
As I understand this, the original problem wasn't explained at all clearly. The issue is not about a limited user being unable to install to Program Files. The issue is that with the IS per-user installer, the user gets offered a UAC prompt and the installation proceeds if he authenticates correctly. With the equivalent default WiX per-user installer, he just gets told that he can't install there (that is, he doesn't get offered a UAC prompt) and he can't install. If my understanding is wrong, sorry for adding to the confusion ... On 11/05/2015 17:43, Phil Wilson wrote: Well it asked me for elevation on my system and installed to ProgramFiles. It also doesn't actually TELL you or show you the install destination and there is no browse dialog. So Rob is correct, and it's as I basically said before, it's one of those IS packages that redirects to ProgramData by calling a custom action called SetAllUsersProfile2k. If a limited user installs it then it won't go to ProgramFiles folder. --- Phil Wilson On Mon, May 11, 2015 at 9:05 AM, Rob Mensching r...@firegiant.com wrote: In this case, a verbose log file would be more useful. -Original Message- From: Scott Ferguson [mailto:scott.fergu...@a2ktechnologies.co.nz] Sent: Monday, May 11, 2015 12:21 AM Not sure about the internal filters that might be set and I wouldn't know what to look for using Orca to view the .msi file to see what might be allowing me to install to Program Files in a per-user install. I do know it is installing to Program Files and not Program Data. If you are curious and wanted to have a look I have created a simple test app and an InstallShield LE installer where the ALLUSERS switch is set to per-user and the data installs to Program Files. The resulting .msi file is in the top level of the zip. I have zipped them and placed them in dropbox if you wanted to download. This is a x64 installer.: https://www.dropbox.com/s/f78ijq0z8qpuwn3/Test%20Project.zip?dl=0 -- J. J. Farrell -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Writing a C++ Custom Action Project
Your checks for an empty string are wrong - constructs like
ip == L
need to be
*ip == 0
or similar.
Check the documentation for the sprintf() implementation you're using.
In Standard C %s is for a normal character string but you're using it
for wide character strings - that would explain an IP address starting
with a 1 getting printed as just a single 1. Microsoft's
implementation does weird things under some circumstances, you need to
be using whatever is appropriate for a wide string here.
You're getting ipaddress and spaces in the output because that's what
you told it to put there.
Regards,
jjf
On 13/03/2015 17:40, Sarvagya Pant wrote:
I have written a C# Custom Action that is supposed to get the Values of
Properties passed to the installer and create some config file. Since the
C# Custom action was done, my installer depends upon .Net too. I want to
avoid this dependency, thus I am opting to write the Custom action in C++.
Following is the C# code that I'm trying to convert in C++:
session.Log(Entering WriteFileToDisk);string ipAddress =
session[IPADDRESS];string productCode =
session[ProductCode];string config_path =
C:\\SomeFolderToInstall\\;string compression =
session[COMPRESSION];string ssl = session[SSL];if
(string.IsNullOrEmpty(compression)){
compression = True; //default true}if (string.IsNullOrEmpty(ssl)){
ssl = False; //default false}if (string.IsNullOrEmpty(ipAddress)){
ipAddress = 127.0.0.1;}string temp = @
{{
logpoint_ip : {0},
compression : {1},
ssl: {2}
}};string filePath =
C:\\SomeFolderToInstall\\lpa.config;System.IO.FileInfo file = new
System.IO.FileInfo(filePath);
file.Directory.Create(); // If the directory already exists, this
method does nothing.System.IO.File.WriteAllText(file.FullName,
config);System.IO.File.WriteAllText(config_path + productcode.txt,
productCode);
session.Log(Confile file is written);
session.Log(Product Code file is written);return ActionResult.Success;
The Visual C++ code is given below:
#include stdafx.h
UINT __stdcall WriteFileToDisk(MSIHANDLE hInstall){
HRESULT hr = S_OK;
UINT er = ERROR_SUCCESS;
hr = WcaInitialize(hInstall, WriteFileToDisk);
ExitOnFailure(hr, Failed to initialize);
LPWSTR ip = NULL;
hr = WcaGetProperty(LIPADDRESS,ip);
ExitOnFailure(hr, Failure in IPADDRESS);
if(ip == L || ip == NULL)
{
ip = L127.0.0.1;
}
WcaLog(LOGMSG_STANDARD, (PCSTR)ip);
LPWSTR ssl = NULL;
hr = WcaGetProperty(LSSL,ssl);
ExitOnFailure(hr, Failure in SSL);
if(ssl == L || ssl == NULL)
{
ssl = LFalse;
}
LPWSTR comp = NULL;
hr = WcaGetProperty(LCOMPRESSION,comp);
ExitOnFailure(hr, Failure in COMPRESSION);
if(comp == L || comp == NULL)
{
comp = LTrue;
}
WcaLog(LOGMSG_STANDARD, Got the Parameters);
char buffer[150];
sprintf(buffer, {\n\ipaddress\: \%s\,\n\ssl\:
\%s\,\n\compression\:\%s\\n},ip,ssl,comp);
WcaLog(LOGMSG_STANDARD, Config Generated is : );
WcaLog(LOGMSG_STANDARD, buffer);
HANDLE hFile;
hFile = CreateFile(LC://LogPointAgent//some_config.config,
// name of the write
GENERIC_WRITE, // open for writing
0, // do not share
NULL, // default security
CREATE_NEW, // create new file only
FILE_ATTRIBUTE_NORMAL, // normal file
NULL);
if (hFile == INVALID_HANDLE_VALUE)
{
WcaLog(LOGMSG_STANDARD, Invalid Handle for Config File);
ExitFunction();
}
BOOL bErrorFlag;
DWORD dwBytesToWrite = (DWORD)strlen(buffer);
DWORD dwBytesWritten = 0;
bErrorFlag = WriteFile(
hFile, // open file handle
buffer, // start of data to write
dwBytesToWrite, // number of bytes to write
dwBytesWritten, // number of bytes that were written
NULL);// no overlapped structure
if (FALSE == bErrorFlag)
{
WcaLog(LOGMSG_STANDARD, Terminal failure: Unable to write to
file.\n);
}
else
{
if (dwBytesWritten != dwBytesToWrite)
{
// This is an error because a synchronous write that results in
// success (WriteFile returns TRUE) should write all data as
// requested. This would not necessarily be the case for
// asynchronous writes.
WcaLog(LOGMSG_STANDARD, Error: dwBytesWritten !=
dwBytesToWrite\n);
}
else
{
WcaLog(LOGMSG_STANDARD, Wrote Config file Successfully);
}
}
Re: [WiX-users] WSX file contains extra files?
You'll probably find it useful to read http://www.catb.org/~esr/faqs/smart-questions.html and follow its advice. On 23/02/2015 15:56, Chrys Perdue wrote: Does anyone have a solution for this? I keep getting this error but don't understand why it is saying that I have these extra dlls. What does that error mean I can't imagine that I'm the only that has ever had a problem with this. -Original Message- From: Chrys Perdue [mailto:chrys.per...@synesis7.com] Sent: Friday, February 20, 2015 11:14 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WSX file contains extra files? I don't understand what causes this error in visual studio 2008. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Torch output, how to force wixmst XML output instead of CAB
ASCII (the One True ASCII, ANSI X3.4-1986) is the 7 bit subset of both Windows ANSI and Unicode. In UTF-8 encoding, this subset is a 7-bit value, so ends up in a single byte which makes it identical to the ASCII and ANSI encodings. The top half of Windows ANSI (values 128 to 255) does not match ASCII or Unicode. So it depends what Stephen means by the file is encoded in ANSI. If it only uses the ASCII subset, then it's equally valid to describe it as encoded in ASCII, UTF-8 or Windows ANSI. If it uses characters from the top half of Windows ANSI then it's not UTF-8. -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Friday, June 13, 2014 8:53 AM I always get this mixed up but I thought that ASCII was basically a subset of ANSI and UTF-8 and they all look the same (unless you write a BOM) until you use non-ASCII characters. The grand majority of internal WiX goo is ASCII without a BOM so it all looks the same... I think Joel agrees with my memory (http://www.joelonsoftware.com/articles/Unicode.html): This has the neat side effect that English text looks exactly the same in UTF-8 as it did in ASCII, so Americans don't even notice anything wrong. -Original Message- From: Tunney, Stephen [mailto:stephen.tun...@nuance.com] Sent: Thursday, June 12, 2014 6:25 PM Also, I have been looking at this file in more detail. The file itself is encoded with ANSI, but the XML header tag states that the XML is in UTF-8. Is this intentional? -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstalling Service on Windows Server 2012 Not Removing Service
No. What does a verbose log show? From: Greg Edwards [mailto:gedwa...@polariswireless.com] Sent: Monday, May 19, 2014 9:53 PM I have a WIX installer build to install a Windows Service. When the uninstaller is run on a Windows 8, it properly removes the service. But when run on a Windows Server 2012, the service remains. In order to remove the service on a 2012 server, we are forced to issue an sc.exe delete from the console. Is there additional parameters that need to be included on a Windows Server 2012 service installer? -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RemoveFolderEx really slow on large folders
How does rollback work with your CA? From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Yes, what it is getting hung up on is enumerating a hundred thousand files one by one and adding them up to a giant string that is passed on to the MSI engine. I looked at the RemoveFolderEx C++ implementation and it confirmed all my suspicions, so I went ahead and took it out and created my own managed custom action instead, which does the whole thing in one line: Directory.Delete(path, true) :-) Of course I added proper error handling and session return codes etc. but now it's super fast and doing exactly what I needed it to do. I'll probably do a blog post on it, I'll update this thread with the link when it's up. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Preserving install directory on upgrade
Perhaps I'm missing something, or this just works by luck, but it seems to work for me in WiX v2: Upgrade Id='$(var.GuidUpgrade)' UpgradeVersion MigrateFeatures='no' Property='UPGRADING' / /Upgrade Property Id=OLDINSTALLDIR RegistrySearch Id=GetOldInstallDir Type=raw Win64='$(var.Comp64)' Root=HKLM Key=Software\Microsoft\Windows\CurrentVersion\Uninstall\[UPGRADING] Name=InstallLocation / /Property If I'm living on borrowed time, I'd value an explanation. From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Friday, April 18, 2014 6:56 PM There is a kind of built-in way, and that's to set the ARPINSTALLLOCATION property (with a type 51 set property CA) after you know the folder location. The good part about this is that it exposes the location to the standard APIs such as using MsiGetProductInfo (INSTALLPROPERTY_INSTALLLOCATION... ) and the equivalents in script etc. The bad part about it is that retrieving it requires code because the registry search to find it is awkward. --- Phil Wilson On Fri, Apr 18, 2014 at 9:45 AM, Neil Sleightholm n...@x2systems.com wrote: Does that persist across an upgrade? (Last time I checked, admittedly in v3.6, it didn't.) Neil -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: 18 April 2014 17:16 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Preserving install directory on upgrade If your msi package will always be launched by a burn bundle, then you could initialize and set Persisted=yes on the burn string variable, which is then passed as a MsiProperty to the package. But if the msi package will be launched by on-demand msiexec install due to advertising or a repair issue, or if the user would ever launch the msi directly, then the value of properties used in the initial install should be saved and initialized the next time the package is launched, as indicated previously. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Check for Installed app
http://wix.tramontana.co.hu/ From: Joel Palmer [mailto:jpalmer1...@comcast.net] Sent: Monday, March 24, 2014 6:17 PM Can you give me the code to check for a previously installed version of my app? Then, prevent install if it is there? Currently, I am allowed to install the same app twice and I want to prevent that. Also, do you have example code on how to check for an old version installed? Then, uninstall when old and replace with new version? -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setup.exe cygwin question
Before that even, I suggest explaining what this is about. Cygwin has a working installer. You're proposing creating a new installer for Cygwin which looks just like the current one. Why? I can imagine possible reasons, but without knowing some good ones it sound like a great deal of work for no gain. From: Carter Young [mailto:ecyo...@grandecom.net] Sent: Tuesday, January 28, 2014 5:34 PM First of All, I would contact the maintainers of Cygwin(http://www.redhat.com/services/custom/cygwin/) and ask how that setup is packaged before trying to retrofit a WiX installer... Quoting Blair Murri os...@live.com: Certainly it is possible using a custom BA from a bundle. Somewhat less so from an MSI. One big advantage of the bundle, however, is that the entire set of packages can be divided up between some arbitrary set of MSIs abstracted away from the end user (in fact, the most logical would be to have each package be an MSI). In fact, you might even be able to reuse your current UI in a custom bundle and save much of the redevelopment effort. Not sure on the project leader part. What resources are available to such a leader (types and experience of developers/testers/PMs, etc.)? Blair From: BGINFO4X Sent: Friday, January 24, 2014 7:25 AM Attending your experience, do you think that is possible to build an installer like the traditional setup.exe installer from cygwin.com? In the following url you can see the main screens. http://x.cygwin.com/docs/ug/setup-cygwin-x-installing.html I ask basically for the screens number 11, 13, 15, 16. Do you think that this is possible with WIX? Does anyone would like to be the project leader of such project? cygwin community should agree with this. I must admit that I can't build such project, I don't have the necessary experience and knowledge. Any recommendation is welcome. Thanks for your time and regards. -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ExeCommand will not accept any path with spaces
From: Gerry Reno [mailto:gr...@verizon.net] Sent: Friday, December 20, 2013 6:28 PM On 12/20/2013 01:16 PM, Edwin Castro wrote: On 12/20/13, 9:49 AM, Gerry Reno wrote: It's not a Windows program. It's a CUI program that you launch from cmd.exe Which you can still more easily start directly. If you insist in wrapping the call with cmd.exe then you MUST adhere to cmd.exe's funky quotation rules. Do it the easy way and remove cmd.exe from your invocation. It looks like you don't have command line arguments for myprogram.exe... Assuming the File/@Id for myprogram.exe is myprogram.exe, I would try CustomAction Id=Launch_myprogram.exe FileKey=myprogram.exe ExeCommand= Execute=deferred Return=asyncWait/ Or to run myprogram.exe without showing the Command Prompt window... SetProperty Id=Launch_myprogram.exe Before=Launch_myprogram.exe Sequence=execute Value=quot;[#myprogram.exe]quot;/ CustomAction Id=Launch_myprogram.exe BinaryKey=CAQuietExec Execute=deferred Return=asyncWait/ I not certain this will work. It might with something like a .bat file since the system knows that .bat files are executed by cmd.exe. But what is there to tell the system that my exe requires being run by cmd.exe? Why does your program require being run by cmd.exe? How does it know whether or not it was run by cmd.exe? It sounds rather unusual. If myprogram.exe is a file which is being installed by this installer, you've got other complications as well. -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ExeCommand will not accept any path with spaces
From: Gerry Reno [mailto:gr...@verizon.net] Sent: Friday, December 20, 2013 6:46 PM On 12/20/2013 01:43 PM, Jeremy Farrell wrote: From: Gerry Reno [mailto:gr...@verizon.net] Sent: Friday, December 20, 2013 6:28 PM On 12/20/2013 01:16 PM, Edwin Castro wrote: On 12/20/13, 9:49 AM, Gerry Reno wrote: It's not a Windows program. It's a CUI program that you launch from cmd.exe Which you can still more easily start directly. If you insist in wrapping the call with cmd.exe then you MUST adhere to cmd.exe's funky quotation rules. Do it the easy way and remove cmd.exe from your invocation. It looks like you don't have command line arguments for myprogram.exe... Assuming the File/@Id for myprogram.exe is myprogram.exe, I would try CustomAction Id=Launch_myprogram.exe FileKey=myprogram.exe ExeCommand= Execute=deferred Return=asyncWait/ Or to run myprogram.exe without showing the Command Prompt window... SetProperty Id=Launch_myprogram.exe Before=Launch_myprogram.exe Sequence=execute Value=quot;[#myprogram.exe]quot;/ CustomAction Id=Launch_myprogram.exe BinaryKey=CAQuietExec Execute=deferred Return=asyncWait/ I not certain this will work. It might with something like a .bat file since the system knows that .bat files are executed by cmd.exe. But what is there to tell the system that my exe requires being run by cmd.exe? Why does your program require being run by cmd.exe? How does it know whether or not it was run by cmd.exe? It sounds rather unusual. Read first line. The line which says it's a CUI program? That's clear, you've said it many times, but so what? Answer question. If myprogram.exe is a file which is being installed by this installer, you've got other complications as well. How so? Care to explain? Not my area of expertise, plenty of discussion in the archives. Depending on the sequencing of the install the file may not be on the system at the time you want to execute it. -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0, Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its dependencies. The system cannot find the file specified
I'm lost; what has this got to do with WiX? From: james pruett [mailto:gpscru...@gmail.com] Hi, Can anyone spot what I am doing wrong? Thanks for looking. -cellurl VisualStudio10 comes up with this error:-- Could not load file or assembly 'GMap.NET.Core, Version=1.7.0.0, Culture=neutral, PublicKeyToken=b85b9027b614afef' or one of its dependencies. The system cannot find the file specified. here is the .SED file- [Version] Class=IEXPRESS SEDVersion=3 [Options] PackagePurpose=InstallApp ShowInstallProgramWindow=0 HideExtractAnimation=0 UseLongFileName=0 InsideCompressed=0 CAB_FixedSize=0 CAB_ResvCodeSigning=0 RebootMode=N InstallPrompt=%InstallPrompt% DisplayLicense=%DisplayLicense% FinishMessage=%FinishMessage% TargetName=%TargetName% FriendlyName=%FriendlyName% AppLaunched=%AppLaunched% PostInstallCmd=%PostInstallCmd% AdminQuietInstCmd=%AdminQuietInstCmd% UserQuietInstCmd=%UserQuietInstCmd% SourceFiles=SourceFiles [Strings] InstallPrompt= DisplayLicense= FinishMessage= TargetName=C:\aaa_jim_test\Speedanator_installer.EXE FriendlyName=Speedanator AppLaunched=Demo.WindowsForms.exe PostInstallCmd=None AdminQuietInstCmd= UserQuietInstCmd= FILE0=GMap.NET.WindowsForms.dll FILE1=Demo.WindowsForms.exe FILE2=GMap.NET.Core.dll [SourceFiles] SourceFiles0=C:\aaa_jim_test\ [SourceFiles0] %FILE0%= %FILE1%= %FILE2%= ---here are all the source files-- http://www.wikispeedia.org/speedo/ --- -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Read System IP adresss
To start with you need to define what you mean by System IP address. The smallest Windows systems I use have four different IP addresses, others have many more. From: Chaitanya [mailto:chaita...@pointcross.com] Sent: Thursday, January 03, 2013 08:55 In wix I want to read system IP address. In registry I need to give system name and IP address.I can read system name. But I cant read System Ip address. -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add Templates
http://www.catb.org/~esr/faqs/smart-questions.html From: Chaitanya [mailto:chaita...@pointcross.com] Sent: Friday, December 14, 2012 7:46 AM Hi, How to add templates in wix. Thanks for help Chaitanya. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Where to install to by default nowadays; App Data or Program Files?
Googling 'msdn appdata' brought up http://blogs.msdn.com/b/patricka/archive/2010/03/18/where-should-i-store-my-data-and-configuration-files-if-i-target-multiple-os-versions.aspx which might be useful. From: Katherine Moss [mailto:katherine.m...@gordon.edu] Sent: Wednesday, November 28, 2012 8:16 PM Thanks. I'll have to look at the certificate properties then and see if I can glean any more information on why the cert needs to be there. I always found it odd, but I also know that it is unprofessional to push professional developers especially if the source code is not publically available. And in this case, it is a commercial product, and just because the dev works for my best friend doesn't really mean much; it doesn't mean that I'll use him as my go-to guy. But anyway, then can somebody tell me why certain applications choose to place some stuff in app data while some of it is in program files? Is that decision made based on the needed permissions of the application, or is it based on the type of information stored in the directory. For instance, Malwarebytes uses App Data to store logs and other things, so I'd assume that Malwarebytes corp thought it too much work to require admin priveleges just to install a log directory, right? And you know something even ! more interesting? I think it gets even more dicy when the person running the application chooses their own custom directory for the application installation. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Tuesday, November 27, 2012 11:37 PM App Data can be non-elevated writable. Program Files requires elevation to be placed there. If you go to Program Files you don't have to worry about your application being tampered with but an App Data install can happen without elevation. The certificate comment doesn't make sense to me. On Tue, Nov 27, 2012 at 8:12 PM, Katherine Moss katherine.m...@gordon.eduwrote: I'm just wondering this since I have a program that installs to app data by default rather than program files, and it's developer says that the change of default directory has to do with special permissions needed. I mean, what is the point of the app data folder anyway? I'd never understood it; why not just leave everything in one directory or the other? The developer of this application says that the directory being app data also has something to do with a certificate or something. Could you folks shed any light on this? -- Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel hardware, programming and related areas? Interviews and blogs by thought leaders keep you ahead of the curve. http://goparallel.sourceforge.net ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ldap_open/ldap_connect in Custom Action
Assuming the code is C or similar ... I know nothing about these APIs, but the way you're calling them doesn't make sense. If they expect to receive a pointer to a wide character as their first parameter, then they presumably expect that pointer to point to a wide character string - taking a pointer to something else and converting it to a pointer to a wide character (as you're doing here) is almost certainly wrong. If this is the problem, then replacing (PWCHR) with L should fix it. If the APIs don't expect a pointer to a wide character as the first parameter, why are you casting it to PWCHR? From: Kun Shi (ofox) [mailto:s...@vmware.com] I need to access LDAP when running a msi on a Windows server 2008 , so I have to call LDAP APIs using CA. I tried 2 approaches, but both failed with error code 0x51 Cannot contact the LDAP server . 1. ldap_open((PWCHR)localhost, 389) 2. ldap_init( (PWCHR)127.0.01, 389 ), then ldap_connect(...) I also tested with ldp.exe on the same machine, it could connect to LDAP server with localhost. Am I doing anything wrong? Did anybody have similar experience? Thanks! -ofox -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstallation
From: DellaRosa, James [mailto:jdellar...@aspexcorp.com] I have been trying, for about two days not, to get my product to use the same .msi to install and uninstall. I've no idea what you're trying to say here. WI usually works by using the same MSI to install and uninstall. What are you trying to do that's unusual? I have am using separate .wxs files for all of my custom dialogs and then have one .wxs that I reference from my main Product.wxs to reference the rest (not user if I explained that too well or not). That depends what you were trying to explain. What you say here makes sense and is clear, but I don't see what it's got to do with your first sentence. I am not sure what else to do here...any ideas? Just the usual - explain clearly what you're trying to do, how you're trying to do it, in what way it fails, exactly what error messages or other indications are seen when it fails, and what your verbose installer log says about it. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Completely revert installation on install failure
Yes, David Watson did at 2012-01-11 18:09:28 GMT: Rollback should and does happen automatically. If you have any custom actions they need to cater for this. What does a verbose log say? How are you installing the service, are you using the ServiceInstall element? From: Kevin Hebert [mailto:ke...@legendary-immersion.com] Anyone have any suggestions about this? Thank you. On 1/11/2012 12:06 PM, AxiomaticImpact wrote: My installer is installing a service (which starts automatically upon installation) and a program. Now, if the install fails for any reason, the service is still installed, but fails to start. How can I go about doing a complete rollback upon failure? Is a custom action that calls the installers uninstall portion feasible? Thanks. -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Can an x86 msi create a registry key under HKEY_CLASSES_ROOT\Wow6432Node on x64 systems?
If you run a 32-bit MSI then its registry entries will be created under Wow6432Node automatically on 64-bit versions of Windows. This is an feature of how Windows emulates the 32-bit environment on 64-bit Windows, nothing to do with WiX or Windows Installer. From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] I have an x86 installer which needs to create a registry key under HKEY_CLASSES_ROOT\Wow6432Node on 64-bit machines. I created a component to do the task. The component installs fine but does not create the key on x64 systems. Is there a way to accomplish this with WiX? Your help will be greatly appreciated. Thanks a lot, Miaohsi -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help needed
From: Kshitish Seet [mailto:kshitish.s...@nextsphere.com] I am asked to use Windows Installer XML (WiX)http://wix.codeplex.com/ to create installation package. I donot know where to start. If anybody have done anything on this please advise. The web page you mention would be an excellent place to start. It has links which lead off to manuals, an excellent tutorial, book references, FAQ lists, blogs, ... -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Combined 32-bit and 64-bit MSI?
The fact that you need separate MSI files but can build them both from the same source? From: Brad Lemings [mailto:b...@rebit.com] AFAICT, both links use separate MSI files for 32-bit and 64-bit installs. Did I miss something? -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Two separate MSI files are recommended. http://blogs.msdn.com/b/heaths/archive/2008/01/15/different-pa ckages-are-required-for-different-processor-architectures.aspx Same source though: http://blogs.msdn.com/b/astebner/archive/2007/08/09/4317654.aspx Phil Wilson -Original Message- From: Brad Lemings [mailto:b...@rebit.com] Is it possible to combine a 32-bit and 64-bit install in the same MSI file? If so, are there some examples, tutorials to look at? Thanks, Eric. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Why are we using a mailing list vs forum?
From: john.bu...@telvent.com [mailto:john.bu...@telvent.com] Subject: [WiX-users] Why are we using a mailing list vs forum? Just curious. Because mailing lists are easier and far more convenient to use. I find forums easier to use. :o) ... All down to personal preference. I believe there are web-based interfaces to this list available. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Suppress Warning LGHT1008
From: Simon Chromow [mailto:simon.chro...@bewotec.de] Hello everybody, is it possible to suppress the warning LGHT1008? Thanks for your efforts Simon http://lmgtfy.com/?q=wix+light+suppress+warnings -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VC++ redistributable questions
From: Tobias S [mailto:tobias.s1...@gmail.com] ... - Most installs run in UI mode Interesting, where did you get that information from? What's the ratio between UI-mode runs and silent, and how accurate is the estimate believed to be? -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSVC problem on Vista (no SP)
You'd perhaps get a more useful answer if you told us what the problem is. From: Michael Tissington [mailto:michael_tissing...@ciqual.com] I have a problem when doing a major upgrade on Vista (no service pack) My install is using both MSVC 9.0 and 10.0 merge modules. The first time my install runs it does install MSVC without any problems. My upgrade package does a RemoveExistingProducts and then installs itself. The problem is ONLY on Vista without service pack, on XP and Windows 7 my package works correctly. Is this a known issue with MSVC and Vista? Is there a fix I can do in the install? -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to write INSTALLDIR to registry?
That defines a property called WIXUI_INSTALLDIR with the value INSTALLDIR. it has nothing to do with a property called INSTALLDIR. From: Michel [mailto:mic...@acromania.nl] Sent: Monday, March 28, 2011 7:33 AM INSTALLDIR is defined: Property Id='WIXUI_INSTALLDIR' Value='INSTALLDIR' / ... -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] One install for multiple OS
And the problem is? From: Robert Hermann [mailto:rob.herm...@nicewareintl.com] I've got an install for a backend service that needs to consider a couple of OS and then scenarios within that os. For the time being I need my project to first detect the os and if its not at least Windows 2003, to throw an error. If its Windows 2008 R2, then the install needs to detect if its being run from a Administrator command prompt or not. If its not, say something. I can the logic to work if its either or but not together ... Right now I've got !-- first make sure the platform is at least win 2003 -- Condition Message='Your operating system must be Windows 2003 or greater'![CDATA[VersionNT = 502]]/Condition !-- if the platform is win 2008 R2 then check for an administrator level -- Condition Message='You must be an administrator to execute to this'![CDATA[VersionNT = 601 and AdminUser]]/Condition Rob -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall Previous Inno Setup Installed App
One thing is that it looks like you're not allowing for the automatic
redirection of various things such as the registry when you run 32-bit things
on a 64-bit system. If your installer is 32-bit and you run it on a 64-bit
system, then references to 'SOFTWARE\Microsoft' will get silently redirected to
'SOFTWARE\Wow6432Node\Microsoft' behind the scenes.
If the old installer was 32 bit and you new installer is 32-bit, you should
just be able to create an installer as if you were targeting a 32-bit system
and it will do the right thing on both 32 and 64 bit - that's the purpose of
the automatic redirection system.
From: Jammer [mailto:jam...@jammer.biz]
Sent: Friday, March 11, 2011 8:01 PM
Hi Again,
I've just created a log of my installer and it seems that
I've got some
of it work now but the last test just left me with a mangled install
that won't uninstall :(
According to the log both of these searches found their
registry values,
which is confusing since using regedit I can only find the first
Wow6432Node key:
Property Id='UNINSTALL_EXE64'
RegistrySearch Id='LocateUninstallExe64' Type='file' Root='HKLM'
Key='SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uni
nstall\{413B7644-1F93-4890-BD40-AC540C29935B}_is1'
Name='UninstallString'
FileSearch Id='LocateUninstallExe64File' Name='unins000.exe' /
/RegistrySearch
/Property
Property Id='UNINSTALL_EXE32'
RegistrySearch Id='LocateUninstallExe32' Type='file' Root='HKLM'
Key='SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{413B
7644-1F93-4890-BD40-AC540C29935B}_is1'
Name='UninstallString'
FileSearch Id='LocateUninstallExe32File' Name='unins000.exe' /
/RegistrySearch
/Property
I'm running Win7 64 and my old app is installed into Program
Files (x86)
is this why it ran the 32bit CustomAction?
InstallExecuteSequence
Custom Action=ca.RemovePreviousVersion64
Before=InstallFilesVERSIONNT64/Custom
Custom Action=ca.RemovePreviousVersion32 Before=InstallFilesNOT
VERSIONNT64/Custom
/InstallExecuteSequence
MSI (s) (C4:64) [19:37:29:528]: Skipping action:
ca.RemovePreviousVersion64 (condition is false)
MSI (s) (C4:64) [19:37:21:422]: Doing action:
ca.RemovePreviousVersion32
Pretty confused by this to be honest I tried VERSIONNT64 and
VERSIONNT
before this but both evaluated false
Is the VERSIONNT64 actually referring to Program Files (x86)
and not the
OS version?
Also, I think the InstallFiles is wrong as I've ended up with
only some
of the files from the MSI installer actually being installed. Or did
the time the uninstall execute after some of the MSI files
had been copied.
Off to fix this utterly mangled install ...
Thanks,
James
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] install location not preserved while upgradation
Feel free to contribute the implementation and documentation. From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Wednesday, February 02, 2011 8:48 PM There should be simpler method like MigrateFeatures in UpgradeVersionelement. On 02-02-2011 12:24, Neil Sleightholm wrote: I believe the registry is the only way: http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-R emember-Pr operty-pattern You could set the ARPINSTALLLOCATION http://robmensching.com/blog/posts/2011/1/14/ARPINSTALLLOCATIO N-and-how- to-set-it-with-the-WiX-toolset but I don't know how you would recall that. Neil -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: 02 February 2011 19:01 Hi, Every time when I upgrade my software, install location dialog shows the default install location, It does not picks the previously installed location automatically. Is there any way to do this other than storing/searching registry keys. Pointer to a article is also welcome. Thanks in advance. Regards, Sanjay Rao -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall shortcut?
Are you saying that the example doesn't work? In what way does it fail? From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 5:14 PM The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_sho rtcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c ,00,54,00,65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall shortcut?
In what sense is it not right? It's a registry key private to your installer which the example creates to meet the requirements of the ICE tests, as explained in the documentation. If you consider the path or name not right use different ones, as others have already suggested. I wouldn't go anywhere near Windows Installer's private entries such as the ones you quoted though. From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 7:13 PM I haven't tried the example but based on other installed applications it seems that the registry settings that the example is using are not right. I didn't want to run an example that didn't meet the sniff test especially when modifying the registry. The sniff test for me was looking at other installed applications and seeing what registry settings they establish. So unless WiX has some special registry settings it seems that these registry settings are incorrect. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Tuesday, January 25, 2011 12:16 PM Are you saying that the example doesn't work? In what way does it fail? From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Tuesday, January 25, 2011 5:14 PM The link to install an uninstall link seems to be outdated: http://wix.sourceforge.net/manual-wix3/create_an_uninstall_sho rtcut.htm Specifically the registry entry does not exist. I am thinking it should be something like HKCU/Micosoft/Installer/Products. Also the application name doesn't seem to come into play. In the registry there is what looks like a GUID that is the key name. I am not sure where this value is derived. Here is the exported key for an installed product: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products] [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797] ProductName=Bsi WebServices PackageCode=34C74D484BB32C140A1D3766499CFCD3 Language=dword:0409 Version=dword:0200 Assignment=dword: AdvertiseFlags=dword:0184 InstanceType=dword: AuthorizedLUAApp=dword: Clients=hex(7):3a,00,00,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList] PackageName=DebugBsiServices.msi LastUsedSource=hex(2):6e,00,3b,00,31,00,3b,00,43,00,3a,00,5c ,00,54,00,65,00,\ 6d,00,70,00,5c,00,00,00 [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Media] 1=; [HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\77A86 7D85B17F234682FCB1D7916A797\SourceList\Net] 1=hex(2):43,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,00,00 -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How do you fix this error? (id is too long, 72 characters max)
Maybe it's just my lack of understanding, but you don't seem to be giving us many clues here. You say the problem Id is in a generated file - what file, generated by what? -Original Message- From: John Bergman [mailto:john.berg...@xpedienttechnologies.com] Sent: Thursday, December 09, 2010 10:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How do you fix this error? (id is too long, 72 characters max) This is the full contents of the WiX file, I don't see how I can shorten it based on what you replied. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; ?include ..\..\common\shared\XPedientInstallerVersionInfo.wxi ? Module Id=MM.Platform.ClientPlugins Language=1033 Version=$(var.MajorVersion).$(var.MinorVersion).$(var.BuildNumber) Package Id=xxx InstallerVersion=200 Manufacturer=XPT / Directory Id=TARGETDIR Name=SourceDir Directory Id=MergeRedirectFolder Component Id='c_c.Data.dm.Plugins.Client' Guid='xxx' File Id='f.c.Data.dm.Plugins.Client' Name='$(var.Core.Data.DataManagement.Plugins.Client.TargetFile Name)' Source='$(var.Core.Data.DataManagement.Plugins.Client.TargetPath)' / File Id='f.c.Data.dm.Plugins.Client.pdb' Name='XPedient.Core.Data.DataManagement.Plugins.Client.pdb' Source='$(var.Core.Data.DataManagement.Plugins.Client.TargetDi r)XPedient.Core.Data.DataManagement.Plugins.Client.pdb' / /Component Component Id='c_c.md.Plugins.Model.Client' Guid='xxx' File Id='f.c.md.Plugins.Model.Client' Name='$(var.Core.MetaData.Plugins.Model.Client.TargetFileName) ' Source='$(var.Core.MetaData.Plugins.Model.Client.TargetPath)' / File Id='f.c.md.Plugins.Model.Client.pdb' Name='XPedient.Core.MetaData.Plugins.Model.Client.pdb' Source='$(var.Core.MetaData.Plugins.Model.Client.TargetDir)XPe dient.Core.MetaData.Plugins.Model.Client.pdb' / /Component Component Id='c_c.rep.Plugins.Client' Guid='xxx' File Id='f.c.rep.Plugins.Client' Name='$(var.Core.Repository.Plugins.Client.TargetFileName)' Source='$(var.Core.Repository.Plugins.Client.TargetPath)' / File Id='f.c.rep.Plugins.Client.pdb' Name='XPedient.Core.Repository.Plugins.Client.pdb' Source='$(var.Core.Repository.Plugins.Client.TargetDir)XPedien t.Core.Repository.Plugins.Client.pdb' / /Component Component Id='c_c.System.Plugins.Client' Guid='xxx' File Id='f.c.System.Plugins.Client' Name='$(var.Core.System.Plugins.Client.TargetFileName)' Source='$(var.Core.System.Plugins.Client.TargetPath)' / File Id='f.c.System.Plugins.Client.pdb' Name='XPedient.Core.System.Plugins.Client.pdb' Source='$(var.Core.System.Plugins.Client.TargetDir)XPedient.Co re.System.Plugins.Client.pdb' / /Component Component Id='c_c.System.Plugins.Presenter' Guid='xxx' File Id='f.c.System.Plugins.Presenter' Name='$(var.Core.System.Plugins.Presenter.TargetFileName)' Source='$(var.Core.System.Plugins.Presenter.TargetPath)' / File Id='f.c.System.Plugins.Presenter.pdb' Name='XPedient.Core.System.Plugins.Presenter.pdb' Source='$(var.Core.System.Plugins.Presenter.TargetDir)XPedient .Core.System.Plugins.Presenter.pdb' / /Component /Directory /Directory /Module /Wix -Original Message- From: Paden, Patrick [mailto:patrick.pa...@wolterskluwer.com] Sent: Thursday, December 09, 2010 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How do you fix this error? (id is too long, 72 characters max) -=-=-=- snip error: The DirectoryRef/@Id of attributes value, 'Application.managementserver.plugins.authentication.native.cl ient.symbo ls' is too long for an identifier, standard identifiers are 72 characters or less. snip DirectoryRef Id=Application.ManagementServer.Plugins.Authentication.Native .Client.Sy mbols snip -=-=-=- The DirectoryRef in the above text-cut is 73 characters long, this is what needs to be changed down to 72 characters or less. Your Directory elsewhere in the code most likely needs to be changed too. Hope this helps, Patrick Paden -- ___ 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] Custom Action
No, the CA DLL doesn't get installed at all if you've set it up correctly. It's a binary stream in the MSI and is available at uninstall time. Hard to tell what's wrong without seeing your WiX code and the relevant bits of a verbose log. From: sagar shinde [mailto:sagar.i...@gmail.com] Hi, I think u got it wrong, i did it in same way u can use that dll in custom action while installation but at uninstall time that dll will be uninstalled with other files and i want to use it at uninstall timehow can i do this On Thu, Nov 11, 2010 at 3:08 PM, Umeshj umesh_jogle...@hotmail.com wrote: Why are you copying this to the user's system? Just use it like this: Binary Id=myC_A_DLL SourceFile=what ever is your source path / refer to it with the id. This way it will stay with your MSI and uninstall will have access to it. Umesh sagar shinde wrote: Hi, I created one custom action dll file, which is copied to destination computer. while installation of product But the problem is i want to use that dll. at uninstall time but it get deleted before it is used by installer so it shows error while uninstall please suggest me proper way to do it,or how can i use that dll at the uninstall time Thank you. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hide commandline parameters in CAQuietExec
The '/c switch in the commandline' is - how can I put this - in the commandline ;). It's a parameter of the command, just data as far as WiX is concerned. It can't affect Wix's behaviour. -Original Message- From: David Binkovic [mailto:david.binko...@googlemail.com] Sent: Thursday, November 11, 2010 8:38 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Hide commandline parameters in CAQuietExec Hi, this statement doesn't even compile here: The CustomAction/@Value attribute cannot be specified without attribute Directory or Property present. But again, even when using the /c switch in the commandline, CAQuietExec still prints out everything inside the Value attribute to the .msi log. David 2010/11/10 sagar shinde sagar.i...@gmail.com: This is how i used it.Which is working efficiently in my work. CustomAction Id=QtExecExample BinaryKey=WixCA Value='/c rmdir /S /Q [LOCATION]' Execute=immediate Return=check/ On Wed, Nov 10, 2010 at 6:30 PM, David Binkovic david.binko...@googlemail.com wrote: Hi, I've tried that, but still the complete commandline is logged from CAQuietExe like this: CAQuietExec: C:\WINDOWS\system32\cmd.exe /c COMMANDLINE IN CLEARTEXT David 2010/11/10 sagar shinde sagar.i...@gmail.com: You can try /C switch in ur commandline while u send your command value or ExeCommand On Fri, Nov 5, 2010 at 2:42 PM, David Binkovic david.binko...@googlemail.com wrote: Hi, I have a password string the user enters in the UI of the installation wizard that needs to be passed to a commandline application in a custom action. I'm using the CAQuietExec function in the WixCA library. I was able to hide the commandline being logged during its creation by setting HideTarget=yes, but the commandline still gets logged when CAQuietExec is invoked, e.g.: MSI (s) (A4:58) [09:52:40:402]: Executing op: CustomActionSchedule(Action=CreateProfile,ActionType=11265,Sou rce=BinaryData,Target=**,CustomActionData=**) MSI (s) (A4:30) [09:52:40:406]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIE213.tmp, Entrypoint: CAQuietExec CAQuietExec: COMMANDLINE IN CLEARTEXT Is is possible to hide this log output, too? Thanks, David -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev
Re: [WiX-users] Dealing with packages bigger than 2Gb
So you're assuming that whoever wrote the error message included three different ways to fix the problem, but chose not to mention the best way? Why do you assume that? From: vivekanandan balaguru [mailto:vivb...@gmail.com] Sent: Wednesday, October 06, 2010 7:49 PM We are trying to build a MSI package that includes multiple files and total size of all files around 2.3 GB. While building we get the error below, Whats the best solution to fix this error? 2light.exe(0,0): error LGHT0296: An error (E_FAIL) was returned while adding files to a CAB file. This most commonly happens when creating a CAB file 2 GB or larger. Either reduce the size of your installation package, raise Media/@CompressionLevel to a higher compression level, or split your installation package's files into more than one CAB file. thanks, Vivek -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues when evaluating a condition
http://lmgtfy.com/?q=msi+verbose+log -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Monday, October 04, 2010 9:52 PM Ok, how do I gereragte a verose log? Cheers Seanm. -Original Message- From: Blair [mailto:os...@live.com] Sent: 04 October 2010 21:15 You change both because the actions will run run in the execute sequence only if the UI sequence didn't run. Generate a verbose log and see what is going on. -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to stop msiserver after installation;
Then the customer needs to speak to Microsoft and get them to change how their Windows package installation system works. The MSI service is part of the Operating System. It has nothing directly to do with your installation, in the sense that your installation doesn't control anything about it. It is up to the Operating System when it starts and stops this service. How do you know it isn't doing other things which have nothing to do with your package installation? -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 11:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task manager while msiserver keeps running untill after 10 minutes and then its status changes to stopped. Customer's requirement is to stop msiserver immediately after our installation completes. All of our custom actions are synchronous return=check. - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 2:53:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I don't think you should be trying to stop msiserver.exe. 1.) I don't know what msiserver.exe is. I would expect to see msiexec.exe but you certainly don't want to stop these process as one of them will be yourself. 2.) The Windows Installer architecture uses a client process and a server process. You really want the OS to determine when the server process is ready to die if at all. The client process should not be killed as that will kill yourself as I mentioned above. Seems to me like the requirement interpretation should be make sure you wait for any exe custom actions your spin up during your installation. WiX will let you wait for their completion already. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 2:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___
Re: [WiX-users] Bootstrapping and Burn
From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Friday, September 03, 2010 6:55 PM On Fri, 3 Sep 2010 10:31:34 -0700 (PDT) Christopher Painter chr...@deploymentengineering.com wrote: Well said other then I don't agree that InstallShield is the reason people don't want to write installs. ( Although this seems to be supported by tweats and blogs that I read. ) I just can't buy it based on my experience using the tool for the last 14 years. Maybe I'm just hard headed enough to look past the tools faults. I used it for a while and found it to be awful. For a start it's expensive enough that we could only buy a single copy - that ruled out other developers creating their own installers, and eventually caused us to abandon it in favour of Visual Studio 2003's Setup Deployment project. I did try and recommend WiX but the senior developers didn't want to learn a new language just to write an installer. We tried to use it, despite not liking products which advertise themselves all over what they produce. We began to lose interest when it failed to install, claiming we were installing it on an unsupported version of Windows - despite the error message and the box listing the version we were installing it on as one of the supported versions. We lost interest completely when their Customer Support refused to help unless we bought a support contract. I have doubts about installer development programs which fail to install, produce an incorrect message about why, and regard that as something that I should pay a lot of money to fix. WiX was wonderful, even in its early 2.x iterations. We were off to a flying start when it installed successfully ... -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How author wix file to uninstall previous MSI version?
http://lmgtfy.com/?q=wix+uninstall+previous+upgrade From: Lucius Fleuchaus [mailto:luci...@microsoft.com] Hello, I like to author an MSI in such a way that it first uninstalls any previous version using the same upgrade code. What is the key element of a wix file that enables this scenario? Thank you! -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX proposal on Area51
Would this be instead of the mailing list, rather than as well as it or gatewayed to it like the existing nabble interface? If so, I'd hate the idea, can't stand these horrible web-based forums. Regards, jjf From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, July 28, 2010 7:47 PM I love this idea. I was actually looking at using their hosted solution for a while then they took it off the market. I didn't realize they opened a new way to get the same thing. On Tue, Jul 27, 2010 at 5:20 AM, Yan Sklyarenko y...@sitecore.net wrote: Hello WiX Community, I'm sure you know about StackOverflow.com. The authors of this fantastic resource opened another service, called Area51. It allows building a community around a certain topic and create an ad hoc site like StackOverflow.com for free. Take a look here: http://area51.stackexchange.com/faq I thought it might be a good occasion to try to build something like http://wix.stackexchange.com as a substitution for this list. Imagine a site like StackOverflow.com devoted to WiX(MSI)-related QA! :) If you like the idea, you're welcome to follow and support this proposal: http://area51.stackexchange.com/proposals/15242/wix-windows-installer-xml?referrer=QMsccxqTnYmfDpFmz1HCvA2 If you don't, let me know - probably it is not as bright as it seems to me. :) -- Yan -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Logging Error
Perhaps Windows path separators (\) in the paths? From: Thode, Katelyn [mailto:katelyn.th...@guidancesoftware.com] I am attempting to log the installation of a package I created. When I run the following command line: msiexec.exe /I C:/comp/code/libdbg/tfuInstaller.msi /l*v C:/Documents and Settings/name/My Documents/tfuInstaller.txt I get an error message that states: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer Package. If I go to the directory and run the .msi from there, the installer runs. Am I doing something wrong? -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error when tryin to install the latest drop of the wix toolset
Other than the various people who've discussed it on this list and answered the questions about it in the last couple of days? From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Sunday, July 04, 2010 9:47 AM Importance: High Hi: When trying to install the latest drop of the Wix toolset the installation doesn't proceed past the install feature selections dialog. It takes me back to what looks like the welcome dialog. Anyone else seen this problem? Cheers Sean. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Quiet Execution of an executable embedded within the MSI
The traditional way to do this (discussed on this list a few times a few years ago) is a little hacky, but works well enough. 1) Put your executable in a self-extracting archive, using iexpress for example; 2) execute the self-extracting archive from the binary table in a 'quiet' mode, putting your executable in a well-known place (such as [TempFolder]); 3) use CAQuietExec to run your program from the well-known place; 4) use CAQuietExec to delete your program from the well-known place. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Friday, June 18, 2010 4:29 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Quiet Execution of an executable embedded within the MSI Binary Elements are extracted to temporary directories using auto generated filenames (see a verbose log for an example). It's not possible to use an application in a Binary Element with QtExec (I looked at the same thing a while ago for a plug-in installer). You'll either need to change it to use a File Element modify the CustomAction to use [#fileid] instead of quot;myexec.exequot; or live without QtExec or as Blair says, write your own Custom Actions to write the Binary to disk in a known location so QtExec can run it. 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 Virtual Environment** 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: Leigh Wetmore [mailto:lwetm...@gmail.com] Sent: 17 June 2010 18:29 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Quiet Execution of an executable embedded within the MSI Hello, I'm trying to figure out how to quietly execute (QtExec) an executable that I include within my MSI yet do not want installed on the user's machine. I've been able to achieve this without using the quiet execute feature, but I don't like the command window popping up during installation. Here is the code for that: Binary Id=CfgUpdateExe SourceFile=..\bin\myexe.exe / CustomAction Id=LaunchCfgUpdateExe BinaryKey=CfgUpdateExe ExeCommand=quot;[TempFolder]UpdateLog.txtquot; UpdateAppConfig quot;[DASLocation]myexec.exe.Configquot; Execute=deferred Impersonate=no Return=asyncNoWait / InstallExecuteSequence Custom Action=LaunchCfgUpdateExe After=InstallInitializeOLDERVERSIONDETECTED/Custom /InstallExecuteSequence I use the binary element to bring the executable (myexe.exe) into the MSI, then launch a custom action with the necessary arguments. I have it executing as deferred with no impersonation as I need the admin privileges already captured by the installer to carry through to the executable. Again, this works fine. However, if I try to convert this to use QtExec, I'm unable to get it to work. Looking in the MSI install log, I see: CAQuietExec: Error 0x80070002: Command failed to execute. CAQuietExec: Error 0x80070002: CAQuietExec Failed Here is my code so far: Binary Id=CfgUpdateExe SourceFile=..\bin\myexec.exe / CustomAction Id=QtExecCommand Property=QtExecUserCfg Value=quot;myexec.exequot; quot;[TempFolder]UpdateLog.txtquot; quot;UpdateAppConfigquot; quot;[DASLocation]myexec.exe.Configquot; Execute=immediate / CustomAction Id=QtExecUserCfg BinaryKey=WixCA DllEntry=CAQuietExec Execute=deferred Impersonate=no Return=check/ InstallExecuteSequence Custom Action=QtExecCommand After=CostFinalizeOLDERVERSIONDETECTED/Custom Custom Action=QtExecUserCfg After=InstallInitializeOLDERVERSIONDETECTED/Custom /InstallExecuteSequence I've left the binary element there, but I don't think the custom actions know about it. It looks like QtExec can't find the executable which makes sense (I can have it run notepad.exe no problem). I'm thinking maybe the files in the MSI, including myexec.exe, get extracted to a temp directory during installation, and I can potentially reference it, like Value=quot;[MSITempDir]myexec.exe...? Thanks in advance for any help anyone can provide. Leigh -- -- -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --
Re: [WiX-users] when can we expect Wix 3.5 RTM?
If people can't be bothered to read the last day or two of the mailing list, or to search the mailing list archives, I'm not convinced that repeating the information elsewhere will have much value - it just gives them somewhere else to not bother looking. On the other hand, your suggestion can't do any harm; feel free to contribute the change. -Original Message- From: Markus Karg [mailto:k...@quipsy.de] Sent: Thursday, April 15, 2010 9:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] when can we expect Wix 3.5 RTM? If it is really so frequently asked, maybe it would be a good idea to post the date in the WiX FAQ http://wix.sourceforge.net/faq.html or on the WiX web site's front page http://wix.sourceforge.net/ to prevent dumb people like me asking silly questions like this over and over again? ;-) -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: Dienstag, 13. April 2010 17:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] when can we expect Wix 3.5 RTM? I'll be surprised if the date has moved much since this question was answered yesterday, or even since the several times it and similar questions have been answered in recent weeks. From: MYFLEX [mailto:shrinuen...@gmail.com] Sent: Tuesday, April 13, 2010 5:41 AM when can we expect Wix 3.5 RTM? Is it ok to use Wix 3.5 beta versions to build my setups? -- - --- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Speeding up Light command
That's funny, it only takes about 20 seconds for me. Perhaps if you provide some information about what you're doing, people may be able to work out what's going on and suggest fixes or workarounds. http://www.catb.org/~esr/faqs/smart-questions.html -Original Message- From: S.P [mailto:iraniangirl9...@yahoo.com] Sent: Thursday, April 15, 2010 12:45 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Speeding up Light command Hi all, I want to create an install package with WiX,but light command is very very slow. It takes about 5 hours to run. Could you please help me if there is anyway to speed this up, without increasing the size of the resulting file? Thanks in advance, Regards New Email addresses available on Yahoo! Get the Email name you#39;ve always wanted on the new @ymail and @rocketmail. Hurry before someone else does! http://mail.promotions.yahoo.com/newdomains/aa/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] when can we expect Wix 3.5 RTM?
I'll be surprised if the date has moved much since this question was answered yesterday, or even since the several times it and similar questions have been answered in recent weeks. From: MYFLEX [mailto:shrinuen...@gmail.com] Sent: Tuesday, April 13, 2010 5:41 AM when can we expect Wix 3.5 RTM? Is it ok to use Wix 3.5 beta versions to build my setups? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Beginner's Question: 32 Bit MSI on 64 Bit OS
I can't imagine why you'd consider that to be obvious - it's nonsense. WiX is software, it can have knowledge of anything its authors want, and it can build any knowledge it needs to into an msi. An msi for a 32-bit application doesn't need any knowledge of the 64-bit environment anyway. You can use WiX on a 32-bit system to build an installer for a 32-bit application, and it will install and work fine on any of 32-bit, x64 or Itanium system. If it's an all CPU application rather than a 32-bit one, you may need to do a bit of extra coding in your WiX sources or the application itself to handle different environments. You can also use WiX on a 32-bit system to build installers for x64 or Itanium applications. -Original Message- From: Lodhiya, Harshil [mailto:harshil.lodh...@eclipsys.com] Sent: Thursday, March 25, 2010 11:41 AM Well it is obvious that msi created on 32-bit machine has no knowledge of 64-bit environment and if u wont to provide support to both 64-bit and 32-bit OS, its required man...sorry.. you can try with it.. -Original Message- From: Markus Karg [mailto:k...@quipsy.de] Sent: Thursday, March 25, 2010 4:59 PM But that's weird -- it would mean that it is impossible to install a MSI on a 64 Bit machine that was created in times when there was no 64 Bit around already... -- or that all software vendors in the past obtained 64 Bit machines just to create their 32 Bit MSIs THERE!? Can't believe that. From: Lodhiya, Harshil [mailto:harshil.lodh...@eclipsys.com] Sent: Donnerstag, 25. März 2010 12:20 Well you have to do it on 64-bit machine only then and then only msi will be fully 64-bit\32-bit compatible. I already encounter this issue in past and had to get 64-bit OS just to solve this issue. -Original Message- From: Markus Karg [mailto:k...@quipsy.de] Sent: Thursday, March 25, 2010 4:46 PM But we do not own a 64 Bit machine, so how to do it on a 32 Bit machine? From: Lodhiya, Harshil [mailto:harshil.lodh...@eclipsys.com] Sent: Donnerstag, 25. März 2010 12:14 Just create your MSI on 64-bit machine with the DLLs created as target x86, and it will run on both 32-bit\64-bit machine. 64-bit OS will automatically take care of system folder. -Original Message- From: Markus Karg [mailto:k...@quipsy.de] Sent: Thursday, March 25, 2010 4:41 PM we need to write a MSI file that has to install a 32 Bit software. It shall correctly install on both, Windows 32 and Windows 64. Is it correct to do one setup that always installs into SystemFolder, or do we have to take any special care for the Windows 64 case? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 2.0 to Wix 3.0
Your question doesn't make sense. WiX 2.0 and WiX 3.0 are releases of the WiX toolset which you use to build MSIs (product installers) - WiX is not a product installer. To move from one to the other you just upgrade the WiX toolset on your build machine, following the instructions with the new release. Whether that's done by a patch or a minor upgrade (or, much more likely, a major upgrade or an uninstall/install) is decided by the team which creates the new release - you just do what the instructions tell you to do. Once you have the new version of WiX installed, you update your installer sources (.wxs files and relatives) to the new WiX schema. The wixcop tool in the new release should help a lot with these updates. From: Anurag Pahwa [mailto:apa...@microsoft.com] Sent: Thursday, March 11, 2010 2:13 PM Hi Guys, Our product installer currently is WIX 2.0 and we are thinking of moving to Wix 3.0. Is it possible to do that in a patch or we have to do in a minor upgrade as there must be huge changes between wix 2.0 and wix 3.0. Thanks Anurag -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem installing a .NET installer-based service using InstallUtilLib.dll
Err ... perhaps I'm missing something, but: in the message you link to,
Brian describes the problem, then Neil points to the MSDN documentation
on how to avoid the problem, then Brian says this method appears to
work perfectly. Have you tried the recommendations in the message you
linked to?
-Original Message-
From: Rajendra Magar [mailto:rma...@newfrontieradvisors.com]
Sent: Tuesday, February 23, 2010 10:38 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Problem installing a .NET
installer-based service using InstallUtilLib.dll
Yes I did. I used 'Account=NT Authority\Network Service'
and it worked in all of the machine configurations I tested
but the experience described in the link below tells me that
this value could be fragile.
http://www.mail-archive.com/wix-users@lists.sourceforge.net/ms
g27992.html
Are you aware of a value that will work with 100% guarantee
in all the platforms? I can't seem to find any documentation on that.
Thank you,
Raz
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
Sent: Tuesday, February 23, 2010 5:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem installing a .NET
installer-based service using InstallUtilLib.dll
Did you try using Network Service? with std wix servicecontrol?
Arun Perregattur
-Original Message-
From: Rajendra Magar [mailto:rma...@newfrontieradvisors.com]
Sent: Tuesday, February 23, 2010 5:01 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Problem installing a .NET
installer-based service using InstallUtilLib.dll
In my case I am required to use NetworkService because the
installer I am working on is supposed to install a client
that looks for problems to solve on a network drive.
Thank you,
Raz
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
Sent: Tuesday, February 23, 2010 4:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem installing a .NET
installer-based service using InstallUtilLib.dll
For our service we set the Account to LocalSystem and works fine.
Arun Perregattur
-Original Message-
From: Rajendra Magar [mailto:rma...@newfrontieradvisors.com]
Sent: Tuesday, February 23, 2010 4:44 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Problem installing a .NET
installer-based service using InstallUtilLib.dll
Arun and Phil, Thank you but I am stuck with a .NET installer
class which does much more than just install the service so I
did not use ServiceInstall and ServiceControl. Besides
ServiceInstall doesn't seem to obey the service parameters
set by the installer class. For example, the .NET installer
class I have sets the service account to NetworkService and
if I want to use NetworkService account to run the installed
service using ServiceInstall I have to specify Account=NT
Authority\Network Service, which I have been warned in
several forums may not always work for all Windows platforms.
Please let me know if you are aware of a good documentation
on what Account value to use that will work on all target machines.
Phil, thank you for the condition hint. The link I pasted
below
(http://blog.vagmim.com/2004/09/installing-windows-services-cr
eated.html) had conditions around the custom actions. I am
afraid I seemed to have ignored them since I didn't
understand what they were exactly. I will try with those
conditions and provide an update.
Sincerely,
Raz
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Tuesday, February 23, 2010 4:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem installing a .NET
installer-based service using InstallUtilLib.dll
It seems to me that you are calling your custom action to
uninstall the service *on an install* because you haven't got
a condition on it. That looks like your first point of failure.
Curious why don't you have a choice about doing it the
proper way as Arun described...
Phil Wilson
-Original Message-
From: Rajendra Magar [mailto:rma...@newfrontieradvisors.com]
Sent: Tuesday, February 23, 2010 12:22 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Problem installing a .NET
installer-based service using InstallUtilLib.dll
Two of my attachments got clobbered on the way, so I am
copy+pasting them here.
(1) ServiceInstaller.wxs
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Product Id=* Name=product name Language=1033
Version=1.0.0.0 Manufacturer=manufacturer name
UpgradeCode={C14D63B3-E9F0-45cf-A86E-B609E48CC642}
Package Id=*
Re: [WiX-users] RegistrySearch Type raw causes a '1' to bewrittenin RegLocater table - should be a '2'
Wow, that's incredibly ancient - an early development build from 2004 or
earlier. The bits have probably rotted. The release version of WIX 2.0
is 2.0.5805.0 which was released in 2008; since WiX 3.0 was released in
July 2009 though, even that is obsolescent.
If you want to stick to WiX 2.0 (perhaps to minimize any required
changes in your installer sources) I'd upgrade to the release version
and try again.
From: Toews, Margaret [mailto:margaret.to...@wolterskluwer.com]
Sent: Thursday, January 28, 2010 3:24 PM
Wix version 2.0.1605.0
Margaret Toews
Programmer Analyst
ProSystem fx Engagement
CCH, a Wolters Kluwer business
Phone: 316.612.5148
Fax: 316.612.3406
E-Mail: margaret.to...@wolterskluwer.com
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, January 27, 2010 11:20 PM
Which build of the WiX toolset?
-Original Message-
From: mtoews [mailto:margaret.to...@wolterskluwer.com]
Sent: Wednesday, January 27, 2010 8:14 AM
From a Wix newby: When I use the registrysearch element as below
Property Id='TESTPROPERTYTOSET'
RegistrySearch Id='NewSignature1'
Type='raw'
Root='HKLM'
Key='Software\Microsoft\Windows\CurrentVersion\Uninstall\{59FF
80EA-267A-418B-9C33-2CC4CC39A365}'
Name='DisplayVersion' /
/Property
the search fails unless I edit the msi package and change the value
in the Type column of the RegLocator table from 1 to 2. From
reading it seems to me that when 'raw' is specified as a type the
RegLocator table Type column should be populated with a 2. If I
edit the package and change it to a 2 the search is successful.
Any assistance is appreciated.
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CNDL1033, LGHT1079 - question about long cabinet file names
I'd be very surprised if anyone could answer that question, certainly not reliably and completely. As the message clearly says, it's unsupported; and as the message helpfully explains, that means it's not guaranteed to work. That means anything can happen. Developers of everything which ever touches these names have been free to build in the assumption that they have short names, or may even have built such assumptions in by accident. Such assumptions could get added at any time. Perhaps long names will always work perfectly in all situations. Perhaps they'll cause very subtle problems which are extremely hard to diagnose in very particular circumstances. Perhaps they'll cause frequent obvious failures. The one thing you can be sure of is that if they do cause problems you won't get any support. From: Ondrej Zarevucky [mailto:ondrej.zarevu...@fine.cz] Sent: Monday, January 18, 2010 3:47 PM Hi everybody, I have question about these two warnings thrown by Candle and Light tools: CNDL1033 and LGHT1079 - both are about long cabinet file names. The warning is telling me I should use short (8.3) file names referencing some Windows Installer team recommendation, but I couldn't find any documentation describing the compatibility problems I can encounter. I would prefer using long file names for easier work with the cabinet files. (Program_Help_EN.CAB is better name then Prog_HEN.CAB) Can you please tell me, what compatibility problems could result from using long cabinet names? I'm targeting Windows XP with Windows Installer 3.1. Thank you for clarification Sample warning from Candle: Media.wxi(15) : warning CNDL1033 : The Media/@Cabinet attribute's value, 'LongCabinetName.CAB', is not a valid external cabinet name. Legal cabinet names must follow 8.3 format: they should contain no more than 8 characters followed by an optional extension of no more than 3 characters. Any character except for the follow may be used: \ ? | : / * + , ; = [ ] (space). The Windows Installer team has recommended following the 8.3 format for external cabinet files and any other naming scheme is officially unsupported (which means its not guaranteed to work on all platforms). Have a nice day zarevak -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Avoiding hard-coding the path to the WiX SDK when usingthe WDK
I recommend keeping the tools under source control, so you always know where they are and what they are. If you don't want to do that, the simplest thing is probably just to normalize the WIX variable in the script you use to launch build. Something like for %%X in (%WIX%) do set WIX=%%~fsX should set it to its short-name form (and clean out any \..\ if there were any). From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Friday, January 15, 2010 1:06 PM I'm using the WDK to build a C++ custom action DLL that gets included in my MSI that I create using WiX 3.5. The problem I've come across is that the WiX headers are located in C:\Program Files (x86)\Windows Installer XML v3.5\SDK\inc, and the WDK doesn't appear to recognise long filenames. I've tried adding $(WIX)SDK\inc both with and without quotes to the 'sources' file, but the only thing that works is using C:\PROGRA~2\WINDOWS~1.5\SDK\doc. I'd rather not use that because it'll be wrong on 32-bit Windows. Does anyone know a way around this to avoid hard-coding paths that other developers are going to have to change for their machines? -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to handle Registry Redirection through WIXon64-bit Platform
From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, January 13, 2010 10:49 AM ... An MSI has a platform attribute which must be set to Intel for x86 packages or Intel64 for x64 packages (can also use AMD64 for x64 packages but it's deprecated by Intel64). ... Some confusion here? I believe it's Intel - 32-bit x86 Intel64 - Itanium family AMD64 - 64-bit x86, deprecated x64 - 64-bit x86 -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building Votive - Email found in subject
Works for me as long as I correct for the line wrapping. -Original Message- From: Jahanzeb Khan [mailto:jk...@commondesk.com] Sent: Wednesday, January 06, 2010 9:32 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Building Votive - Email found in subject Neil The url does not work; whats the new url for this. thnx -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Wednesday, January 06, 2010 3:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Building Votive - Email found in subject This documents what you need for 3.0, it might help: http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix- build-mach ine.html. The other thing to watch is that the last time I checked the CVS source didn't contain the binary files saved correctly. Neil -Original Message- From: Adam Langley [mailto:alang...@winscribe.com] Sent: 06 January 2010 20:25 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Building Votive I would like to add some functionality to Votive (3.5 codebase), yet I am finding it rather difficult getting it to build in Visual Studio 2008. Is the environment setup documented anywhere? Thanks Adam Langley -- -- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- -- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix redistributable
Really? Why? I'm still using an old version of WiX which didn't include such a warning - why was it added? Does something not work properly with more recent versions of WiX if Visual Studio isn't present? -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 05, 2010 4:28 PM To: nagara...@symphony.cc; General discussion for Windows For info the WiX install doesn't require visual studio, it just warns if it is not found. Neil -Original Message- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: 05 January 2010 12:07 Hi, I am using just smoke.exe to one of solutions I am working right now, Is there any link by which only this light weight component be downloaded instead of wix toolkit that requires visual studio. Thanks, Nag -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix redistributable
Thanks Neil, that makes sense - it would be impressive if Votive worked without VS ;). It's more a common-sense informational than a warning I suppose ... The discussion had me worried that some dependency on VS had crept into WiX itself. -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 05, 2010 7:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix redistributable Yes Votive doesn't work, everything else works fine. I assume it was added as it is not common to install it without VS (I only noticed it because I install to a build server that doesn't need VS). This is the message: Votive, the WiX project and editor package for Visual Studio, cannot be installed because Visual Studio 2005 or 2008 Standard Edition or higher is not installed. Neil -Original Message- From: Jeremy Farrell [mailto:jfarr...@pillardata.com] Sent: 05 January 2010 19:02 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix redistributable Really? Why? I'm still using an old version of WiX which didn't include such a warning - why was it added? Does something not work properly with more recent versions of WiX if Visual Studio isn't present? -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Tuesday, January 05, 2010 4:28 PM To: nagara...@symphony.cc; General discussion for Windows For info the WiX install doesn't require visual studio, it just warns if it is not found. Neil -Original Message- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: 05 January 2010 12:07 Hi, I am using just smoke.exe to one of solutions I am working right now, Is there any link by which only this light weight component be downloaded instead of wix toolkit that requires visual studio. Thanks, Nag -- -- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] UI Custom Action displays dialog behing MSI UI
I had a similar situation where I needed to convert a mass of existing
code into MSI custom actions. This code called various driver
installation APIs which could create message boxes in unusual
situations, and these boxes were displaying behind (and hidden by) the
MSI UI.
I know almost nothing about UI programming so this solution may work
more by luck than design, but it works for me on Server OSes from 2000
to 2008 R2. I set the 'owner window' parameter on relevant API calls to
the MSI UI window, which I find with the FindWindow function as follows:
hWindow = FindWindow(TEXT(MsiDialogNoCloseClass), NULL);
I don't know to what extent I've been lucky with this; if anyone knows
of a better way to achieve the same thing, please let me know.
Regards,
jjf
-Original Message-
From: Tobi Ha [mailto:tob...@gmx.net]
Sent: Tuesday, December 15, 2009 1:32 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] UI Custom Action displays dialog behing MSI UI
Hello,
I have a WiX installation that shows within a custom action a
dialog from a dll that is installed during this installation.
It all works fine, except that the dialogs appears behind the
normal MSI UI.
Here a short example how my custom action looks like (instead
of message box, a real UI appears)
UINT __stdcall MessageBoxAction (MSIHANDLE hInstall)
{
Beep(500,2000);
LPCTSTR lpszText = LA message box text;
LPCTSTR lpszCaption = LA message box title;
UINT nType = MB_OK;
MessageBox(NULL,lpszText,lpszCaption,nType);
return ERROR_SUCCESS;
}
Is there a way to display the own UI in foreground?
Cheers,
Tobias
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] _Validation table
So MSDN is wrong when it says This table is not shipped with the installer database? In that case I assume either that it's intending to say something other than what it says, or it's presuming the use of a particular toolset which strips the table. As far as WIX is concerned though, this table is shipped with the installer database unless something non-WIXy is done to strip it out after building the MSI and before shipping it. -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, December 02, 2009 4:45 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] _Validation table From a functionality point-of-view, the table is not considered part of the installation database (it is ignored if present by the routines involved in installation maintenance of your product). However, many administrators depend on guidance from the ICE tests and other tests which often depend on this table in determining if they will allow any given application on their networks. Being OSS or not, you still need customers for most software, and that can be valuable information that others will use in helping gauge the quality of the package being offered. I would recommend leaving it in. -Original Message- From: Piotr Fusik [mailto:pi...@fusik.info] Sent: Wednesday, December 02, 2009 2:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] _Validation table Ok, I dropped this table with Orca and the MSI is just 19kB smaller which is no big deal (however nice for open source software where you don't care about certification). Could you please explain This table is not shipped with the installer database from the MSDN article linked below? Thanks, Piotr Sebastian Brand \(Instyler Software\) wix+us...@instyler.com wrote: I think you need to keep this table to ensure others your app was ICE validated, I remember this was part of the Designed for Windows requirement or so. Best regards, Sebastian Brand Deployment consultant E-Mail: sebast...@instyler.com Blog: www.sebastianbrand.com -Original Message- From: Piotr Fusik [mailto:pi...@fusik.info] Sent: Wednesday, December 02, 2009 10:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] _Validation table A quick look with a hex editor into my MSI reveals that this table is 50 kB or so. I'd be happy to drop it if it's optional, preferably with a WiX option. End users won't read Descriptions anyway, why are they so long then? Piotr Blair os...@live.com wrote: Besides what is available on MSDN (e.g. http://msdn.microsoft.com/library/aa372930.aspx) what more do you need to know? -Original Message- From: Piotr Fusik [mailto:pi...@fusik.info] Sent: Tuesday, December 01, 2009 2:39 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] _Validation table Hello, Could you please explain what's the purpose of the _Validation table in MSI files? How is the long Description column used? How much overhead does this table add to my MSI and how can I reduce it? Thank you, Piotr -- --- --- -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- --- - Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- --- --- -- Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- --- - Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk.
Re: [WiX-users] InstallShield 2010 vs InstallAware 9
I don't know where you draw the line between 'simple' and 'top shelf', a few of the products whose installers were developed entirely with WiX are: Microsoft Office Enterprise 2007 (over 4,600 files and 53,000 registry keys) Microsoft Visual Studio 2008 Sun Microsystems MySQL -Original Message- From: Matt Walker [mailto:matt.wal...@synergis.com] Sent: Thursday, November 12, 2009 7:00 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] InstallShield 2010 vs InstallAware 9 From just initially talking about or thinking about WiX my first guess would be that this would be the option for simpler installation processes/tasks and that the 'Top Shelf' products (with regard to price not quality) would pull the heavier weighted install stuff. I would be interested in the cons of WiX, but I don't know if that would offend anyone in this group. Here is the list of what our installations do... what can't be done or is difficult to do with WiX? -Install\Configure a web site (with the help of some Custom Actions to tweak some config files) -Various Custom Actions: call windows installer .dlls, call executables stored in the .msi, call executables on destination or installed w/application -Dialog addition and editing -Copy, Move and Delete File operations (Wise - basically populates the Move.. and RemoveFile tables -Query the Registry up front for launch condition values and values to populate dialog controls in the UI -Add, update INI files -Add File Associations/Extensions -Create and control Windows Services -Install Pre-requisite checking -Language localization support -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Thursday, November 12, 2009 1:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] InstallShield 2010 vs InstallAware 9 Anything? Really? I'm sorry, I like WiX a lot but I can list out a couple dozen glaring feature and usability gaps. WiX is nice but let's keep some perspective here. --- On Thu, 11/12/09, Brian Simoneau bsimon...@freedomscientific.com wrote: From: Brian Simoneau bsimon...@freedomscientific.com Subject: Re: [WiX-users] InstallShield 2010 vs InstallAware 9 To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Thursday, November 12, 2009, 11:05 AM My company was using InstallShield before switching to WiX. I have never used InstallAware, but the only advice I can give is to use WiX. It's free and can do anything that the commercial products do, sometimes better. -Brian Simoneau -Original Message- From: Matt Walker [mailto:matt.wal...@synergis.com] Sent: Thursday, November 12, 2009 9:10 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] InstallShield 2010 vs InstallAware 9 Hi All, I'm new to the group and was pointed here by an individual from whom I've received valuable assistance on many .NET, install related topics over the past several years. I know this is a Wix users group, but I'm hoping someone can give me some insight, guidance, etc. We as a company are looking to switch our install build product. The company whose product we use has undergone several company takeovers/changes recently and it doesn't look like the development effort is there for this particular product. We've been focusing on InstallShield 2010 and InstallAware 9. I've used InstallShield products in the past and never really had any major problems to speak of. IS seemed fairly easy to use and suited all of our needs. This seems to be the case with InstallShield 2010. InstallAware is a tool of a different kind as it appears to be primarily script based but does have a Visual interface as well. It might be because I could be subconsciously hooked on InstallShield, but InstallAware seems cumbersome to me. I guess that may also be that I'm just not used to their way of doing things. Conversion for us would take a larger amount of time with this product, but if it works and is stable, that really won't matter much to me. What I've heard and from what I already knew, they are both major players with InstallShield having a longer lifespan so far. I've been told that InstallAware claims to be on the cutting edge, but their installs at times display weird behavior. I'm trying to find an individual(s) that has used both or similar products for a compare and contrast of sorts. What are the pros and cons? Early on, Of course price will be a factor for us, but I just want to be sure after making a selection I don't miss major advantages of the product that is left behind by our decision. Please help if you can.
Re: [WiX-users] Are short names even useful anymore?
Don't forget that the WI team are still living back before UNICODE was invented. WI, the team that time forgot. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Saturday, October 17, 2009 6:27 PM To: d...@tramontana.co.hu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Are short names even useful anymore? I think the point is all of this is pointless and yes, quite useless to the vast majority of the world. Case in point.. Rename SomeDotNetAssembly.dll to SomeDo~1.dll or some other hashed/transformed representation like WiX does and try referencing the classes in it after it's installed. The CLR will throw an exception in a heartbeat. I suppose someone out there still needs this functionality but it's got to be a .1% use case by now. If I'm wrong, I'd love to know of real world use cases other then someone might be trying to do an HTTP stream ( which no one does anyways ) or passing a public property that would break my application anyways. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Sat, 10/17/09, Rob Mensching r...@robmensching.com wrote: From: Rob Mensching r...@robmensching.com Subject: Re: [WiX-users] Are short names even useful anymore? To: d...@tramontana.co.hu, General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Saturday, October 17, 2009, 10:39 AM That and if you try to use the install an MSI over HTTP (which is such a pain to deal with it isn't worth it) the Windows Installer will use short names as well. Oh, and the user can technically speaking always pass in the SHORTFILENAMES Property and force your MSI to use short filenames. I don't quite follow the question though. MSI requires short filenames. WiX v3 will auto-generate them in a stable and highly-unlikely to collide sort of way. Why does it matter? virtually, Rob Mensching - http://robmensching.com 2009/10/17 DEÁK JAHN, Gábor d...@tramontana.co.hu On Tue, 13 Oct 2009 15:17:32 -0700, Blair wrote: Blair, the last time I heard this question mentioned from some of the developers, maybe Rob, the answer always was that the only real reason for short names was that some old Novel servers couldn't cope with long names and removing this would make it impossible to make network installations on those servers. I don't know if this is still an issue today. Bye, Gábor --- DEÁK JAHN, Gábor -- Budapest, Hungary E-mail: d...@tramontana.co.hu -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now!
Re: [WiX-users] Windows 2003 Server 64 bit and XP 64 bit
You missed the MsiNTProductType property. Regards, jjf -Original Message- From: John Lalande [mailto:johnlala...@gmail.com] Sent: Friday, October 16, 2009 10:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Windows 2003 Server 64 bit and XP 64 bit Since XP64 is based on Win2k3 64, their OS installer properties are identical. Is there another way to distinguish the two operating systems? We would like to add a launch condition that allows XP64 but not Win2k3 Server 64. John -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Cannot install in any other drive, except c drive
From: Sunkesula, Srivardhan [mailto:srivardhan.sunkes...@netapp.com] I have a strange problem with my installer. When I select a drive other than C drive for installation. The installation is failing. Can you please let me know, what could be the problem? Thanks Regards, Srivardhan. You've probably got something wrong in one of your WiX source files. A verbose log of the installation failing might help you see what's wrong; if it doesn't help you, it might help someone here help you. See also http://www.catb.org/~esr/faqs/smart-questions.html -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] using dism.exe in my custom action
You missed the wonderful file system redirector. Whichever of the two names you use, Windows forces the 32-bit custom action to use the file in SysWOW64. [WindowsFolder]Sysnative\dism.exe should do what you need. From: Lian Jiang [mailto:lji...@microsoft.com] Sent: Friday, September 18, 2009 1:07 AM I am trying to use dism.exe in one of my custom actions for Windows server 2008 R2. There are two dism.exe, one in c:\windows\system, the other in c:\windows\syswow64. No matter which one I use, running msi fails with this error: You cannot service a running 64-bit operating system with a 32-bit version of DISM. Please use the version of DISM that corresponds to your computer's architecture. Here is my custom action: !-- install .NET framework -- CustomAction Id=InstallNetFramework Property=InstallNetFrameworkDeferred Value='[WindowsFolder]SysWOW64\dism.exe /online /enable-feature /featurename:NetFx3' Execute='immediate' Return='check'/ CustomAction Id=InstallNetFrameworkDeferred BinaryKey='WixCA' DllEntry=CAQuietExec Execute=deferred Return=check Impersonate=no / Did I miss anything? -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multiple Driver Packages
From: Slide [mailto:slide.o@gmail.com] I have two drivers that I need to install, I currently have two inf files for them. Apparently DIFXAPP doesn't support this as I get the following error: ... DIFXAPP: ERROR: more than one driver package found in 'C:\Program Files\MYAPP\' DIFXAPP: ERROR: InstallDriverPackages failed with error 0xD DIFXAPP: RETURN: InstallDriverPackages() 13 (0xD) Action ended 20:52:22: InstallFinalize. Return value 3. Do I have to combine the two drivers into a single inf file? Just based on the error message, it looks like putting the different packages in different directories would work. -- 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
Re: [WiX-users] Can an installer use a file (extracted to the temparory file extraction directory) but not actually install it?
From: Lian Jiang [mailto:lji...@microsoft.com] Sent: Sunday, August 16, 2009 4:45 AM I have a driver file mydriver.sys which will be installed to c:\windows\system32. What I am doing is: Step 1: install mydriver.sys to c:\program files\myapp; Step 2: a custom action install this driver file to c:\windows\systems. Have you looked at DIFxApp, the official way to install drivers using Windows Installer and WiX? Therefore, after installation, mydriver.sys exists in two locations mentioned above, which is confusing. Why so? It's a normal thing to do. The laptop I'm using has about 50 .sys files under the 'program files' directory where they've been put a part of the installation of various packages. The application installations then went on to use these as the source files for the driver installation steps which copied them into the system directory. I want to remove the one in c:\program files\myapp to clear the confusion. Candidate solutions include: Solution 1: make this file hidden in step 1. Solution 2: after Step 2, use a custom action to delete this file under %PROGRAMFILES%. Solution 3: Do not install this file in Step 1 at all. Instead, just extract it to the temporary file extraction directory, and the driver installation custom action directly installs this driver file from the temporary extraction directory. After installation, this driver file is deleted together with the temporary extraction directory. To me solution 3 is cleaner than 1 and 2. But is it possible? Yes. For example, is it possible to pack a file and extract it to temporary directory but not install it? Is it possible to access the temporary directory directly from a custom action? I know solution 3 may go into the wild a little but am interested having some discussion. Why not just review the countless previous exhaustive discussions of this subject on this list? The most recent pass through it that I'm aware of was my message six days ago in the thread How to treat support files that do notgetinstalledontarget machine?; it's been discussed every few months for several years if that instance isn't adequate. -- 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
Re: [WiX-users] warning LGHT1076: ICE47
When you ask for a way to get rid of a warning without fixing the problem and without suppressing the warning, it's hard to imagine what could be suggested. -Original Message- From: Vuchuru, Surekha (SBT US EXT) [mailto:surekha.vuchuru@siemens.com] Sent: Tuesday, August 11, 2009 4:57 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] warning LGHT1076: ICE47 Any suggestions please? Thanks and Regards, Surekha Vuchuru -Original Message- From: Vuchuru, Surekha (SBT US EXT) Sent: Friday, August 07, 2009 2:45 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] warning LGHT1076: ICE47 Hello All, I am getting a lot of Wix compilation warmings. This is one of them. warning LGHT1076: ICE47: Feature 'NetworkGatewayFeature' has 878 components. This could cause problems on Win9X systems. You should try to have fewer than 817 components per feature. Please let me know how I can get rid of this warning without supressing it and without reducing the number of components...Is this a limitation in Wix? Thanks and Regards, Surekha Vuchuru -- -- -- 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 -- 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
Re: [WiX-users] How to treat support files that do not getinstalledontarget machine?
You sounds a bit confused about merge modules. Think of them as source code; they're used when building your MSI, to include functionality defined by a third party. The merge module doesn't exist when you get to the machine on which you're installing you're MSI. As a parallel, suppose I sent you a .c file which contained the code for a custom action; you'd build the .c into a Custom Action DLL and include and reference it in your MSI. When you run that MSI to install your product, the functionality described by my .c file gets used, but the .c file itself never gets anywhere near the installation machine. A merge module is conceptually similar. A different possibility is where you want to distribute a merge module as part of your product, to enable other people to build an MSI using the functionality you've defined in the merge module. In this case, the merge module is just a file which is part of your product, like any other, and would be installed as a file. If you need to put files on the installation system which are used as helpers of some sort during the installation, one way is to include them in a self-extracting archive which you execute as an executable custom action. I then use another customer action to delete them once they've been used. I believe a slightly more favoured way to do this sort of thing is to include the files as binary streams in the MSI and use custom actions to extract and manipulate them. It should only rarely be necessary to do this sort of thing, though. -Original Message- From: MacDiarmid, James D [mailto:james.macdiar...@eds.com] Sent: Tuesday, August 11, 2009 6:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to treat support files that do not getinstalledontarget machine? Sorry. I was wondering what the normal practice would be when you have files that are utility files for the installation and not apart of the application. They are not supposed to be installed, such as a merge module. The msm doesn't get installed however it's content will be installed. Thanks, Jim -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, August 11, 2009 7:45 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to treat support files that do not getinstalled ontarget machine? Your question is a bit vague (and contradictory). What do you want to do with these support files exactly? If they're required for your product then use a bootstrapper to install them before your product. Since you have a merge module for the XML Parser simply merge it into your MSI using the Merge MergeRef nodes if that's the case. 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 Virtual Environment** 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: MacDiarmid, James D [mailto:james.macdiar...@eds.com] Sent: 10 August 2009 20:08 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to treat support files that do not get installed ontarget machine? I have some support files that I would like to include on the installation disk. What's the typical practice for dealing with these types of files that do not get installed? For example, I have a merge module for the MS XML Parser that I want to call in my install. Thanks, Jim -- -- -- 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 -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment
Re: [WiX-users] Is there a walkthrough that works for installingdrivers in an MSI, wix v 3 (5120)?
Perhaps MSDN will be helpful: http://msdn.microsoft.com/en-us/library/ms790295.aspx?ppud=4 Regards, jjf -Original Message- From: Mark Roden [mailto:mmro...@gmail.com] Sent: Wednesday, July 29, 2009 8:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is there a walkthrough that works for installingdrivers in an MSI, wix v 3 (5120)? Well, now I get the drivers tags, but the driver itself still isn't getting installed. Seriously, is there a walkthrough or anything on how to use this? I've found numerous sites where people _ask_ the question, but none with actual responses with actual code that says Here is how you take an inf and a sys and install it. Thanks, Mark On Wed, Jul 29, 2009 at 7:56 AM, Mark Rodenmmro...@gmail.com wrote: I had not done that. Hopefully, that will be all I need to get it done. Thanks, Mark On Wed, Jul 29, 2009 at 12:28 AM, Blairos...@live.com wrote: Are you talking about Intellisense in VisualStudio? You added the DifxAppExtension's namespace, right? Here is a short example (warning: not tested): Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:dfx=http://schemas.microsoft.com/wix/DifxAppExtension; ... Component ... File .../ dfx:Driver AddRemovePrograms=no ForceInstall=no/ ... -Original Message- From: Mark Roden [mailto:mmro...@gmail.com] Sent: Tuesday, July 28, 2009 10:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Is there a walkthrough that works for installing drivers in an MSI, wix v 3 (5120)? It doesn't work. The driver tags aren't showing up. According to what I can see in the schema, the driver tags are derived from component, and neither the component tag has driver tags, nor does it contain driver tags, nor is a driver tag being recognized. They are all failing. So, I figure I'm probably doing something wrong. I've updated to the release version, in case that was the problem. It didn't help. On Tue, Jul 28, 2009 at 8:33 PM, Blairos...@live.com wrote: DifxApp? See the Difxapp Schema page in wix.chm. -Original Message- From: Mark Roden [mailto:mmro...@gmail.com] Sent: Tuesday, July 28, 2009 4:17 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Is there a walkthrough that works for installing drivers in an MSI, wix v 3 (5120)? Hi all, I'm running wix v 3.0.5120, and I need to install a driver. Basically, it's one inf file and onesys files, and I'm having no joy. I've tried this: Directory Id='DriversFolder' Name='Drivers'/ ... DirectoryRef Id=DriversFolder Component Id=cyusb_inf Guid=* File Id=cyusb.inf Source=..\Includes\cyusb.inf / /Component Component Id=cyusb_sys Guid=* File Id=cyusb.sys Source=..\Includes\cyusb.sys / /Component /DirectoryRef I've also tried putting things into system32. The drivers are there, and they work perfectly well on a vista machine if I tell the system exactly where to look, but I'd like it to Just Work. Thanks! Mark -- -- -- 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 -- -- -- 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 --
Re: [WiX-users] Packaging multiple installers
The whole MSI SDK documentation is huge, no one would expect anyone to absorb it all quickly; many people building MSIs only need to be conversant with a fraction of it. Did you look at the Remarks section of the Feature Table documentation, as Rob recommended? It's about half a page, and (as he said) appears to give plenty of information on the area you were asking about. The search string 'msdn feature table' in Google finds it as the first hit. From: SToney [mailto:stoneya...@msn.com] Sent: Thursday, June 18, 2009 12:50 PM I did look at the MSI SDK. It gave me more keywords that I could search for. After searching and spending the day yesterday modifying my code and running the created MSI, I was able to change the directory that I was installing to. I apologize for my sarcastic response and hope I didn't offend anyone. I'll keep searching the reference material and when I get to my wits end, I'll put off asking my questions and go back to searching some more and then I'll re-read what helped me the most http://geekswithblogs.net/jwatson/archive/2006/11/03/96052.aspx Thanks Date: Wed, 17 Jun 2009 14:48:43 -0700 From: ml-user+58124-794520...@n2.nabble.com To: stoneya...@msn.com Subject: Re: [WiX-users] Packaging multiple installers Did you look at the resource he recommended to you? What further questions do you have after studying that? Sarcastic slamming of helpful responses is unlikely to encourage people to help you further, and is likely to put off others who might have helped. From: SToney [mailto:stoneya...@...] Thank you so much for your invaluable reply. If you had read my original post, it would let you know that I am just starting with WIX and was looking for directions on where to look because I work with people that tell me to look in the book or Hmm, MSI SDK about the Feature table Remarks section talks about all kinds of this stuff. The first thing I do is Look in the book and then I try to find out for myself and I look in the documentation. Maybe you should put Look in MSI SDK in the WIX help documentation. Again, thanks for the 20 seconds that it took you to type that, unless it took you more, then thank you for that extra time. Rob Mensching-6 wrote: Hmm, MSI SDK about the Feature table Remarks section talks about all kinds of this stuff. SToney wrote: I'm putting all DirectoryRef's in one library, and understand that the directory tree structure doesn't get created until you copy files to it. How can I change the Feature Level so that the feature for Level 2 gets processed instead of Level 1? SToney wrote: I am starting on my first WIX Installer Package. Thanks in advance for all the information I have read to get me this far. In my installation, I put 3 radio buttons to install a Demo, Advanced or Network version. I am going to have all 3 options on the CD/DVD. Some files are shared between the 3 and some are not. Should I create fragment libraries for each and then have the shared files in the main .wxs file or is there a better way? Where do I need to create the different Program Files tree structure because Demo has a different tree structure and Advanced and the Network version have the same tree structure so I don't want to create the Demo Tree if it is not being installed. Also, when I go to install different applications, can I spawn other MSI's? With parameters or is it better to have the MSI read registry entries or ini files? I am going to have many more questions and will also try to answer some because being new, there are a lot of brick walls. Thanks -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Packaging multiple installers
Did you look at the resource he recommended to you? What further questions do you have after studying that? Sarcastic slamming of helpful responses is unlikely to encourage people to help you further, and is likely to put off others who might have helped. From: SToney [mailto:stoneya...@msn.com] Thank you so much for your invaluable reply. If you had read my original post, it would let you know that I am just starting with WIX and was looking for directions on where to look because I work with people that tell me to look in the book or Hmm, MSI SDK about the Feature table Remarks section talks about all kinds of this stuff. The first thing I do is Look in the book and then I try to find out for myself and I look in the documentation. Maybe you should put Look in MSI SDK in the WIX help documentation. Again, thanks for the 20 seconds that it took you to type that, unless it took you more, then thank you for that extra time. Rob Mensching-6 wrote: Hmm, MSI SDK about the Feature table Remarks section talks about all kinds of this stuff. SToney wrote: I'm putting all DirectoryRef's in one library, and understand that the directory tree structure doesn't get created until you copy files to it. How can I change the Feature Level so that the feature for Level 2 gets processed instead of Level 1? SToney wrote: I am starting on my first WIX Installer Package. Thanks in advance for all the information I have read to get me this far. In my installation, I put 3 radio buttons to install a Demo, Advanced or Network version. I am going to have all 3 options on the CD/DVD. Some files are shared between the 3 and some are not. Should I create fragment libraries for each and then have the shared files in the main .wxs file or is there a better way? Where do I need to create the different Program Files tree structure because Demo has a different tree structure and Advanced and the Network version have the same tree structure so I don't want to create the Demo Tree if it is not being installed. Also, when I go to install different applications, can I spawn other MSI's? With parameters or is it better to have the MSI read registry entries or ini files? I am going to have many more questions and will also try to answer some because being new, there are a lot of brick walls. Thanks -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error CNDL0288: The variable 'Configuration' with value'Release' was previously declared with value 'Release'
It would probably be helpful if you showed the code. Please show all uses of the token 'Configuration' in the .wxs file which candle is complaining about. -Original Message- From: Scott Button [mailto:scott.but...@sphericalangle.com] Sent: Monday, May 18, 2009 7:02 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error CNDL0288: The variable 'Configuration' with value'Release' was previously declared with value 'Release' Scott Button wrote: Yes, I have re-read the WiX.chm sections on multi-language builds. Also read a number of blogs and the tutorial at blogs.technet.com/alexshev/ How about another hint about how to diagnose the error: candle.exe : error CNDL0288: The variable 'Configuration' with value 'Release' was previously declared with value 'Release'. From: Rob Mensching r...@wixtoolset.org Subject: Re: [WiX-users] FW: multi-lingual installation support for Windows 7 and Wix 3.0.5217 Sat, 16 May 2009 13:27:43 -0700 That is actually an error in the WiX MSBuild Tasks that was just fixed in this last week's build. Scott again: I downloaded and installed Wix 3.0.5315. (15 May 2009). Same error. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Detecting Server 2008 Core
http://www.letmegooglethatforyou.com/?q=Detecting+Server+2008+Core -Original Message- From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com] Sent: Saturday, March 07, 2009 7:10 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Detecting Server 2008 Core How do you detect Server 2008 Core? -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Log file generation
http://www.letmegooglethatforyou.com/?q=msi+log+file -Original Message- From: Hukumchand Shah [mailto:hukum.s...@gmail.com] Sent: Thursday, February 19, 2009 9:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Log file generation Hi, Thank you for the solution. But when I double click the .msi file then how to generate the log file. user will not run the installer by using msiexec coomand. He will just double click .msi file to run it. waiting for reply. Thanks Regards, Hukumchand Shah On Thu, Feb 19, 2009 at 1:10 PM, Anweshi D anwe...@yahoo.com wrote: Hi use msiexec /i [msiname] /l*v [logfilename] Thank you Anweshi With Regards, Anweshi Deverasetty, Associate Consultant, Microsoft Global Services India. http://anweshi-microsoft.spaces.live.com/ Give when others are in need , not when u have. - Anweshi - Original Message From: Hukumchand Shah hukum.s...@gmail.com To: wix-users wix-users@lists.sourceforge.net Sent: Thursday, February 19, 2009 10:25:02 AM Subject: [WiX-users] Log file generation Hi All, Can anyone tell me, how to generate log file for my installation process. I want log file for whatever installer does during installation process. Thanks, Hukum -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] extracting WiX compiled version from msi file
Not at all - it's the simplest and most straightforward option I've seen
so far ...
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, January 28, 2009 6:42 PM
To: chr...@deploymentengineering.com; General discussion for
Windows Installer XML toolset.
Subject: Re: [WiX-users] extracting WiX compiled version from msi file
Now you are all making my open in a text editor look really
stupid :-)
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: 28 January 2009 18:30
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] extracting WiX compiled version from msi file
It's easy as pie in C#/DTF:
String creatingApp;
using( var database = new Database( PATH_TO_MSI,
DatabaseOpenMode.ReadOnly))
{
creatingApp = database.SummaryInfo.CreatingApp;
}
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread
that deserves
attention? E-Mail Me
--- On Wed, 1/28/09, Neil Sleightholm n...@x2systems.com wrote:
From: Neil Sleightholm n...@x2systems.com
Subject: Re: [WiX-users] extracting WiX compiled version
from msi file
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Date: Wednesday, January 28, 2009, 12:13 PM
It is in the summary information but the only tool I know
that displays
it is InstEd (http://www.instedit.com/). A rough way of
find it is to
open the MSI in a text editor and search for Windows
Installer XML you
should find a string like Windows Installer XML
(3.0.4923.0). I am
sure there is an easier way of finding though.
Neil
-Original Message-
From: Cohen, Roy [mailto:roy.co...@verint.com]
Sent: 28 January 2009 18:01
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] extracting WiX compiled version from
msi file
Hi all.
I have a set of MSI installation files that ware compiled
from different
version of WiX (v3)
My question is, is there a way for extracting the complier
(WiX) version
from the MSI ?
And I mean any possible way ... ORCA / VBScript / windows
installer DLL
etc' ?
Best wishes
--Roy
It's all in the head /
This electronic message may contain proprietary and
confidential
information of Verint Systems Inc., its affiliates and/or
subsidiaries.
The information is intended to be for the use of the
individual(s) or
entity(ies) named above. If you are not the intended
recipient (or
authorized to receive this e-mail for the intended
recipient), you may
not use, copy, disclose or distribute to anyone this
message or any
information contained in this message. If you have
received this
electronic message in error, please notify us by replying
to this
e-mail.
--
--
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
--
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
--
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Prevent 32 bit MSI install on 64 bit OS
From: Jeremy Lew [mailto:j...@liquidmachines.com] Before I resort to a CA that tries to call IsWow64Process(), is there any other simple way to bail out if attempting to run a 32 bit installer on a Win64 OS? (My product requires the 64 bit installer on a 64 bit OS) Launch conditions based on some combination of standard properties such as VersionNT64, Intel64, Msix64. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Prevent 32 bit MSI install on 64 bit OS
The VersionNT64, Intel64, and Msix64 properties are all imprecisely and inaccurately worded, which makes it very difficult to work out how to use them properly. It's a while since I wasted a chunk of time experimenting to work out what they actually mean, but I'm fairly sure that Msix64 being defined actually means that you are running on an x64 edition of Windows. Its documentation implies that you could be on a 32-bit or x64 edition running on an x64 processor, or on an Itanium processor, but it's wrong. Regards, jjf -Original Message- From: Jeremy Lew [mailto:j...@liquidmachines.com] Sent: Monday, January 26, 2009 9:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Prevent 32 bit MSI install on 64 bit OS Hmm, the doc says that Msix64 is set when running on a 64 bit processor. What does it mean if I have a 32bit version of Windows running on a 64-bit processor? -Original Message- From: Moradi, Ari [mailto:arastoo.mor...@hp.com] Sent: Monday, January 26, 2009 4:15 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Prevent 32 bit MSI install on 64 bit OS I think a LaunchCondition with the property Msix64 will do what you want. -Ari -Original Message- From: Jeremy Lew [mailto:j...@liquidmachines.com] Sent: Monday, January 26, 2009 2:49 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Prevent 32 bit MSI install on 64 bit OS Before I resort to a CA that tries to call IsWow64Process(), is there any other simple way to bail out if attempting to run a 32 bit installer on a Win64 OS? (My product requires the 64 bit installer on a 64 bit OS) Thanks, Jeremy -- -- -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- -- -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MSI, pkgmgr, DISM, Optional Components
How is Windows Installer related to the other Microsoft packaging tools (pkgmgr.exe in Windows Server 2008 and DISM.exe in Windows 7), in particular when using them to enable or disable Windows Optional Components? I know that I can't nest Windows Installer invocations (that is, use a Custom Action in one .msi to invoke an install of another .msi). Can I use Custom Actions in a .msi to invoke pkgmgr or DISM to manage Optional Components? The commands would be of the form pkgmgr.exe /iu:Component DISM.exe /online /disable-feature:Component and I'd want to use CAQuietExec (in WiX v2) to call them. Apologies if this is too far off-topic; recommendations for better places to ask would be welcome. Many Thanks, jjf -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Detecting IA64 bit architecture
Only if a better solution is one which doesn't meet your requirements ;). Msix64 doesn't tell you anything about Itanium; if Msix64 is not defined, you could be on either a 32-bit or an Itanium processor (or running with a version of Windows Installer earlier than 3.1). You were asking about a property, presumably for use in a Launch Condition - where does the TemplateSummary come into it? From: Andy2k8 [mailto:[EMAIL PROTECTED] Mine is a 32 bit package..so i wonder if i can specify Intel64 in the TemplateSummary.. Msix64 seems to be a better solution J. J. Farrell wrote: From: Andy2k8 [mailto:[EMAIL PROTECTED] Is there any property that i can use to detect itanium 64 bit architecture and abort the installation? Intel64 - http://msdn.microsoft.com/en-us/library/aa372396(VS.85).aspx -- --- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Andy MSI Developer Schneider Electric:working: -- View this message in context: http://n2.nabble.com/Detecting-IA64-bit-architecture-tp1381532 p1386420.html Sent from the wix-users mailing list archive at Nabble.com. -- --- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Detecting IA64 bit architecture
From: Andy2k8 [mailto:[EMAIL PROTECTED] Is there any property that i can use to detect itanium 64 bit architecture and abort the installation? Intel64 - http://msdn.microsoft.com/en-us/library/aa372396(VS.85).aspx - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Equivalent of UPGRADINGPRODUCTCODE under MSI 4.0
From: dB. I just realized that UPGRADINGPRODUCTCODE is an MSI 4.0 thing. How can I detect that the product is being uninstalled during a major upgrade for old versions of MSI? That's bad realization; if you're basing it on MSDN, you've been caught by some poor thinking (or rather, lack of thinking) on how to present the Requirements information. It requires WI 4.0 on Windows Server 2008 and Windows Vista, probably because that's the only version of WI supported on those OSes. It works with any version of WI on 2003, XP, and 2000. In other words, it works for all version of WI on all versions of Windows since 2000. Regards, jjf - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Checking/installing Windows 2008 Features
What is the best way for a WiX v2 built installer to test if one of the standard Windows Server 2008 Features is installed? Is it possible for an MSI file to invoke the installation of a Feature before continuing with the rest of its own installation? I need to check if a Feature is installed; if not, I'd like to install it automatically before continuing, but I need at least to abort if the Feature is not installed. I'm aware of the ocsetup and servermanagercmd utilities around which I could presumably hack up a custom action or two, but a more elegant solution would be better. The Feature in question in this case is Multipath I/O in case that's relevant. Thanks for any advice. Regards, jjf - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Installing certificates with WiX v2
I'm using the release version of WiX v2 (2.0.5805.0) and need to install a certificate to the local machine's Trusted Root Certification Authorities certificate store and the Trusted Publishers certificate store - the equivalent of certmgr.exe -add cert.cer -s -r localMachine root certmgr.exe -add cert.cer -s -r localMachine trustedpublisher Can the Certificate element in WiX v2 do this? I'm having trouble mapping the choices for StoreName onto the Microsoft terminology above. I guess that root is the Trusted Root store (as it is for certmgr) but what about Trusted Publishers? Is that what WiX calls ca, or does WiX not support Trusted Publisher? The definition of ca in wix.chm is very similar to that of root ... I've a vague memory that installing certificates requires more than Certificate / and linking against sca.wixlib; can anyone remind me what else I need to do? Many Thanks, jjf - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing certificates with WiX v2
Thanks Rob, looks like Ugly CA Time again then ... Regards, jjf From: Rob Mensching TrustedPublishers was added to WiX *v3* jus this last week. No plan to add the feature to WiX v2 (since it is stable and we're not adding features there). -Original Message- From: Jeremy Farrell I'm using the release version of WiX v2 (2.0.5805.0) and need to install a certificate to the local machine's Trusted Root Certification Authorities certificate store and the Trusted Publishers certificate store - the equivalent of certmgr.exe -add cert.cer -s -r localMachine root certmgr.exe -add cert.cer -s -r localMachine trustedpublisher Can the Certificate element in WiX v2 do this? I'm having trouble mapping the choices for StoreName onto the Microsoft terminology above. I guess that root is the Trusted Root store (as it is for certmgr) but what about Trusted Publishers? Is that what WiX calls ca, or does WiX not support Trusted Publisher? The definition of ca in wix.chm is very similar to that of root ... I've a vague memory that installing certificates requires more than Certificate / and linking against sca.wixlib; can anyone remind me what else I need to do? Many Thanks, jjf - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Improve the WiX mailing list
Is there a big complaint? I thought it was just that many people prefer a mailing list to a forum, in the same way that you prefer a forum to a mailing list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Painter Sent: Monday, June 02, 2008 2:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Improve the WiX mailing list A forum instead of a mailing list would go a long way to solve the problem. While vBulletin is standard out of the box, I actually like the feature over at the Microsoft forums where topics can be attributed as a Question and as Answered. This allows a group of volunteers to see who has been assisted and who has not. BTW, this is one place where I feel that their is a disconnect between the leaders and the users of WiX. I've posted over 3,500 times on InstallShield Community helping many, many people over the years and personally I don't see what the big complaint is about going to a forum based system. Rob Mensching [EMAIL PROTECTED] wrote: Answering questions takes time. Depending on the complexity of the question and the amount of time available some questions may go unanswered for a very long time. The only thing I know to do is to keep doing research and follow up with your own question with whatever extra research you may have found narrowing down the complexity of the question until someone has cycles to answer it... I'm answering community stuff tonight since I'm home sick and can't sleep any longer but don't have enough focus to dig into technical problems. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Riyaz Mogharabin Sent: Monday, June 02, 2008 00:09 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Improve the WiX mailing list Dear All, I hope you are fine and doing well. I have a question from you experts about the mailing lists. How can we manage the WiX mailing list to ensure most of the emails are answered? I personally have sent some emails to the group that I'm sure they have answers, but nobody has answered them yet, and perhaps will never answer. How can we change this? How can we have a guarantee that all the mails are answered and if necessary are treated with? (Some of them may need research and maybe useful to be added in the next releases.) Maybe we can have an index or a list of the emails with no answers? And try to answer them one by one? Do not forget that the archive is a very good help besides the documentation. I hope there are good suggestions for this. Regards, Riyaz - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX 3.0 release date
From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 6:10 PM WiX v2 *is* out of beta. It has been for a good many months (http://robmensching.com/blog/archive/2008/02/17/WiX-toolset-o n-SourceForge-marked-ProductionStable.aspx). We're going to have to do an SP1 to add the MSI4.5 features to WiX v2 in the not too distant future but that will be 100% backwards compatible and done very carefully to minimize regressions. That's great news, thanks Rob. Why keep so quiet about it though? I'd have thought the first formal WiX release would have had a bit of a fanfare. My main interest in scanning this list of late has been watching for an announcement of v2.0 being released, but I don't think it's been mentioned here at all before this. I may have missed it of course, but I can't find it in the archive either. Similarly, no mention in the Latest news section on the project web site at http://wix.sourceforge.net/ or anywhere else on that site that I can find - that's the other place I check occasionally. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix mailing lists open to public = more spam
From: DEÁK JAHN, Gábor On Thu, 22 May 2008 10:26:27 -0700, Neil Enns wrote: Neil, I was one of those people. It's painful. And I can figure out Wix... Come on, guys, all it takes is a single, emtpy e-mail to [EMAIL PROTECTED] and, I guess, a reply to a confirmation mail. Couldn't be easier... Planting a flag on the peak of Everest is easy as well - all you have to do is press the stick firmly into the snow. - 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] Device Driver Installation
It's called the WDK these days, and is available from MSDN under Windows Server 2008. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Mahieu Sent: Friday, April 25, 2008 4:20 PM To: wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [WiX-users] Device Driver Installation Well, I've downloaded WiX 2 and I'm going to create a merge module for my device drivers that I will merge into my WiX 3 installer. My big issue now is, where can I find the Windows DDK so I can use DIFxApp with WiX? I know this probably isn't the place to ask, but I'm guessing someone here has used it and knows where it can be found. The Microsoft site is pointing me to Microsoft Connect and MSDN, neither of which are turning up anything for me. Does the DDK need to be purchased? If so, is there any way to obtain the DIFxApp/WiX stuff for free (as that's all I need)? I should mention, we're only supporting WinXP SP2 or greater, if that makes a difference in terms of which DDK I need. Thanks for the help so far, it's really appreciated. Tony On Fri, Apr 25, 2008 at 6:04 AM, John Hall [EMAIL PROTECTED] wrote: Anthony, As far as I know DIFxApp still only works with WiX 2. My workaround was to create a merge module using WiX 2 just for the driver installation and merge that into my WiX 3 installer. Regards, John From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Mahieu Sent: 25 April 2008 04:46 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Device Driver Installation Hey guys, this is my first post. I've got this relatively simple project (WiX v3, using Votive w/ VS2005) that I now need to add device driver installation to. I need to install two drivers if a specific feature is selected to be installed. From everything I'm reading, I need to use DIFxApp. Unfortunately, this is where all helpful information I've found on the web stops. I read in previous questions that DIFxApp won't work with WiX 3. Is this still the case? If so, how would one recommend going about installing drivers in WiX 3? If the issue has been resolved and DIFxApp now works with WiX 3, does anyone have a tutorial on what needs to be done to install the drivers? I know I should be looking into the DDK for some help, but I couldn't even find that (anyone have a link?). Any help someone can give me would be greatly appreciated, as I'm rather new to all this. Thanks! - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix mailing lists open to public = more spam
Require registration to post. WiX isn't the sort of subject that people typically want to ask a question or two about and then forget. Most newbies have been tasked with using WiX, so would be well advised to follow the list anyway. For the few people who have valid reasons to ask a question or two then go away, subscribing just isn't a big deal and they can unsubscribe as soon as their questions have run their course. Given the list netiquette of replying to the list rather than the individual, they need to be subscribed to get email responses to their questions anyway. It's a common practice on technical lists to require registration to post. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, April 22, 2008 6:29 PM To: Rob Hamflett; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] wix mailing lists open to public = more spam If anyone has any other opinions on this topic, please do make your voice heard. I'm still following this thread and trying to figure out if I should lock non-members out of the list. I'm still very hesitant to do that since it raises the bar for people just starting to get involved with WiX (and we don't need to make anything *harder* smile/). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Tuesday, April 22, 2008 03:58 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] wix mailing lists open to public = more spam There's still a problem if you prefer to use the newsgroup interface (I'm using Thnderbird). You can't delete messages, and the best I think I can do is move them into a separate folder. That might have to suffice if we can't filter them out before they hit the list. Rob DEÁK JAHN, Gábor wrote: On Mon, 21 Apr 2008 15:22:35 +0100, Martin MacPherson wrote: Martin, I have been thinking the same. I found a post who suggested the following if you use gmail: Instead of web-based mail services, just use a good, traditional e-mail client with proper Bayesian spam filter (eg. Thunderbird) and it will eliminate 98-99% of the spam after the initial learning period. It will also adapt to languages other than English, it might take slightly more time (a couple of dozen additional messages) but it will be just fine. You can manually handle the small number of false positives and negatives. Bye, Gábor --- DEÁK JAHN, Gábor -- Budapest, Hungary E-mail: [EMAIL PROTECTED] -- -- -- --- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java .sun.com/javaone -- -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- --- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java .sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- --- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java .sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade Problem with WIX installer
You were asked if you had changed the product code and you replied that you had changed the product upgrade code. What do you mean by that term? The message you are seeing implies that you have not changed the product code. You need to give precise accurate information for people to be able to help you effectively. From: amitchopra But if we are installing it from msi , it is saying that Product is already Installed Wilson, Phil wrote: If you're doing an upgrade you don't use that command line. Just run the MSI as if it is a clean install (which it is, the upgrade makes it remove older versions as well). From: amitchopra Yes, we have changed the product upgrade code. The command that we have used is: msiexec /i SampleUpgrade2.msi REINSTALL=ALL REINSTALLMODE=vomus ” Sebastian Brand-2 wrote: Did you change the product code in the upgrade? What's the command prompt's parameters? On Apr 4, 2008, at 12:36 , amitchopra wrote: I have created an installer using WIX. When i am upgrading it using command prompt, it is upgraing my existing version. But when i am upgrading it by clicking it on the msi, it is giving error : The version is already installed. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Systray doesn't work during Repair
From: Anidil Sent: Thursday, March 27, 2008 10:19 AM It works fine during repair when i change the condition to Installed.But it doesn't launch automatically after the installation unless i make it NOT Installed , in that case repair doesn't work :(...strange.. What's strange? Think about it. When you set the condition to NOT installed you're saying only do this action if the product was not installed at the start of this MSI run. When you set the condition to installed you're saying only do this action if the product was installed at the start of this MSI run. Is the product installed when you do the initial installation? Is the product installed when you're doing a repair? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Forums...
Maybe no-one can remember. I can't be sure if it was here, but I've a feeling there was such discussion once. It should be possible to find out from the archives. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aurélien DEROUINEAU Sent: Saturday, March 01, 2008 1:57 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Forums... Still waiting for an answer... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aurélien DEROUINEAU Sent: vendredi 22 février 2008 13:15 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Forums... Has there been any discussion on the creation of community-driven forums? - 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] In place upgradation...
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of V K Gangwar Sent: Monday, December 24, 2007 4:22 AM I developed an MSI installer with version 1.10.0. I want to upgrade this installer with version 1.11.0. When I double click on version 1.11.0 installer a message is displayed that Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use add/ remove programs on the control panel. I am able to upgrade through command line option msiexec /i XXX.msi REINSTALL=ALL REINSTALLMODE=vomus. But my customer is looking for in place upgradation. Is there any way for in place upgradation. Sounds like you want an ordinary 'major upgrade'. Have you had a look at Lesson 4 of the tutorial at http://www.tramontana.co.hu/wix/ ? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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] silent uninstallation using wix
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jenefer I am new to wix programming. I have created a wix installer that will copy files to some desired directories on installation. The current situation is such that every time i make changes to the files i need to build the new installer and uninstall the previous installed product and then install the latest one. I want a way so that whenever i install the updated installer, the installer should check for the presence of the same product in the system and uninstall the previous product automatically and install the latest one. (silent uninstallation) I am using InstallExecuteSequence RemoveExistingProducts Before =InstallInitialize /RemoveExistingProducts /InstallExecuteSequence but it is not working. It neither uninstalls the previous installed product or installs the new one. Can you please suggest some way..It would be better if you sent me the source code alsoIt is very urgent.. Sounds like you want an ordinary 'major upgrade'. Have you had a look at Lesson 4 of the tutorial at http://www.tramontana.co.hu/wix/ ? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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] Upgrading
From: Craig0ss Sent: Monday, November 05, 2007 12:01 PM Ive read alot of other posts regarding upgrading but ive yet to find any information relavent to my situation, so if anyone knows of any threads and have the links to them then please post. Here is what i want to do I need my MSI to check for an existing install of the software ie. 5.2.1, now it does this fine, however i also need it to check for the existing directory and then pass that information to a variable that the installer then sets the installer to install to. Basically i need the upgrade to install to the directory that the previous installation resides in? Any ideas Discussed here just the other day. See http://sourceforge.net/mailarchive/message.php?msg_name=OFF5E86288.1900F763-ON88257387.004CFDBD-88257387.004D795F%40milliman.com for a few ways to do this. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX v2 status
What is the current status of WiX v2? Rob wrote back in early April about its going into escrow in preparation for releasing the final build. I've not seen any announcements about it since then, and can't find anything about an official release on the web sites. There was a build 2.0.5325.0 published on May 25 - is this the final build? It would be good if some information on this could be added to the 'Latest News' on the front page of the SourceForge site. Many Thanks, jjf - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bitmap scaling
From: Scott Palmer On 1/22/07, Bob Arnson [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Steve Bennett wrote: Ok, I should have clarified that I have read that bit of the tutorial many times and it doesn't help a lot. In particular: - the two systems that are displaying it differently have the same font size, different screen resolutions (1280x1024 vs 1152x864) but the same pixels-per-inch settings. And strangely, the installer box appears physically larger on the smaller screen (that is, the box is a greater number of pixels across on the 1152-wide display than it is on the 1280-wide display – quite a few more). - The bitmaps I'm using more or less conform to the specifications. There are big letters which are part of the logo, and it's a pain if we can't use that. No dithering or chequered backgrounds. Resolution and DPI aren't directly related to MSI dialog scaling. It's not documented, but from experimenting, it appears that MSI uses the message box font to determine when it thinks it needs to scale dialogs. Typical XP themes all look the same with the same DPI setting but custom themes, customized fonts, or non-English fonts all can cause scaling. There's really nothing you can do to avoid it using MSI UI; even Win32 UI suffers from the same problem though it's more predictable (based on DPI) and most folks running high DPI are used to minor artifacts because of scaling. It also appears that MSI is using a broken algorithm to scale the image. The result is spectacularly ugly, with streaks of color where it has duplicated a row or column of pixels. Not realizing that the size was not fixed (since the documentation indicates otherwise), I spent time tweaking my images so they didn't scale on my development computer because the scaling totally ruined the images... (I should have known something was up because the image sizes I needed didn't match the docs). Now what am I supposed to do? The purple streaks through the image that appear when scaling are totally unacceptable. I'm using JPEGs for my images, and know almost nothing about image manipulation and GUIs. Here's my experience, for what it's worth. I was also having problems with ugly scaling artifacts. The way I got round this was to pick a 'typical' screen resolution and font size, and measure the exact size in pixels at which my image was being drawn by MSI on that setup. I then recreated my image at exactly that pixel size and incorporated it. It was obviously then drawn perfectly in that configuration (since there was no scaling at all) but I find it now also scales cleanly to all the other screen resolutions and font sizes which I've tried (albeit not an exhaustive list - I was pleased enough getting it to work well in the common cases). I don't know if I've just been lucky, but previously I was seeing all sorts of ugly striping effects and false colours, whereas now it's near perfect in every screen config I've used. I believe that MSI's scaling is documented, unless I misunderstand what's being talked about. Sizes of controls are specified in 'Installer Units' which are approximately equal to one-twelfth (1/12) the height of the 10-point MS Sans Serif font size - http://msdn2.microsoft.com/en-us/library/aa369490.aspx - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] DIFx prompt shows up behind UI
From: Bob Arnson [mailto:[EMAIL PROTECTED] J. J. Farrell wrote: At the moment I'm setting these SetupAPI parameters to NULL. I'm guessing from Bob's message that I can solve this problem by passing a handle to the Installer UI window instead of NULL. Does this sound right? I know almost nothing about Windows UI programming, so my main question is: how should a C deferred custom action get hold of a handle to the installer UI window for passing to these SetupAPI routines? Possibly. I thought there was a WiX function that returned the active installer window but I can't find it at the moment. You might want to check out GetForegroundWindow. Thanks Bob. I ended up with hWindow = FindWindow(MsiDialogNoCloseClass, NULL); To find the Installer's UI window. The class name varies with the style of the window, but a call of this sort should be able to find a window associated with the Installer. Passing this handle to the SetupAPI functions solved my problem of pop-ups appearing behind the Installer UI window. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] rfc: Package element changes
It's not a big deal, but I prefer the current question mark scheme since it has the overall look of a GUID. If I'mdoing avisual scan ofa WiX source file looking for GUIDs, this format stands out as being one,but is also instantly recognizable as onewhich will be allocated a real value at build time. It looked strange to me when I first saw it, but I've grown to like it. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek CiceroneSent: Tuesday, August 01, 2006 11:10To: [EMAIL PROTECTED]; 'Bob Arnson'; [EMAIL PROTECTED]Cc: wix-users@lists.sourceforge.netSubject: Re: [WiX-users] rfc: Package element changes Just a note: the Product/@Id should almost never be auto-generated because that forces major upgrades every time. But why would * be better than ----?? Thanks, Derek From: Rob Mensching [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 01, 2006 8:37 AMTo: 'Bob Arnson'; [EMAIL PROTECTED]Cc: wix-users@lists.sourceforge.netSubject: RE: [WiX-users] rfc: Package element changes I have no opinion on that. Anybody else care? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob ArnsonSent: Monday, July 31, 2006 3:39 PMTo: [EMAIL PROTECTED]Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]Subject: Re: [WiX-users] rfc: Package element changes Derek Cicerone wrote: That is an excellent point what if we keep the ???... syntax just for Product/@Id in that case and go with the recommendations below for everything else? Any chance of a different syntax? @Id="*" maybe, keeping with the wildcard scheme?-- sig://boBhttp://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add/Remove Program Icon on Windows 2000
From: Rob Mensching Sent: Monday, July 31, 2006 09:06 the add/remove program icon does not show up on Windows 2000. It is fine on Windows XP and win2K3. The icon is pointed to an icon file. Any ideas? I want to say I remember something about Win2K ARP requiring the .ico to be stored in the resource stream in a DLL (resource-only DLL is fine). It's been on my list for a very long time to add something to the WiX toolset to automatically manage resource DLLs for icons. I have an installer with ARPPRODUCTICON set to an icon file included in the binary table, and that works fine on 2000 and 2003. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and 64-bit questions
You can handle it all easily and cleanly from common source using the preprocessor todeal withthe differences. I have a WiX source which selects ona variableat the top to set up all the necessary GUIDs, target folders,'yes' or 'no'for the Win64 attribute, and so on for each of the three target architectures. The single selection variable is passed in on the candle command line. The paths to files which differ by architecture are also passed in. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly SummerlinSent: Monday, July 24, 2006 08:20To: wix-users@lists.sourceforge.netSubject: Re: [WiX-users] Wix and 64-bit questions Since most of my Wix code is just component definitions though it looks like Ill need separate sources for the 64-bit component definitions and the 32-bit component definitions since the Win64 attribute marks them as 32-bit or 64-bit, correct? In the Wix documentation for component Win64 it states: Set this attribute to 'yes' to mark this as a 64-bit component. This attribute facilitates the installation of packages that include both 32-bit and 64-bit components. If this bit is not set, the component is registered as a 32-bit component. If this is a 64-bit component replacing a 32-bit component, set this bit and assign a new GUID in the Guid attribute. So it sounds like here that I should have separate GUIDs for 32-bit and 64-bit component definitions even though the assemblies that are being deployed are exactly the same. If this is the case, then I can understand the need for separate GUIDs, but it sure makes maintaining 32-bit and 64-bit installs twice as much work. Do I need to have dual copies of my component definitions for 32 64 bit? From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Monday, July 24, 2006 10:13 AMTo: Kelly SummerlinCc: wix-users@lists.sourceforge.netSubject: Re: [WiX-users] Wix and 64-bit questions Kelly Summerlin wrote: My question is this, is it possible to use the same Wix files to build one MSI that will deploy the files and registry settings to 32-bit or 64-bit determined at runtime? No. An MSI package must be marked as 64-bit before it can install 64-bit components into the 64-bit parts of the file system and registry. See http://msdn.microsoft.com/library/default.asp?url=""> for details.You can use the same WiX source but you'll need two packages.-- sig://boBhttp://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
