[WiX-users] Files protected by windows
hi guys when im installing on win2k i get errors saying that the file being copied is being protected by windows, these files are going into the system32 folder, these files already exist on win2k but not not on others likw xp, will i need to diable these files being installed to a win2k system? Also is there a registry entry that i can check for win2k Thanks Craig0ss -- View this message in context: http://www.nabble.com/Files-protected-by-windows-tf4764277.html#a13625856 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building a patch in Visual Studio
You are correct, the MsiFileHash table is not populated for Setup and Deployment project msi's. From looking in the Patching code in WiX, it appears it will add the MsiFileHash entry for unversioned files into the transform for files that have changed when binding the transform into the patch. Have you built a patch and observed the MsiFileHash entry being added to the msi? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil Sent: Wednesday, November 07, 2007 9:40 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Building a patch in Visual Studio Visual Studio setups don't generate MsiFileHash entries for data files. Does WiX (well MsiFiler) populate these tables later? This is usually an issue when generating patches because the original install source is more likely to be required when the patch is applied. See MSDN topic Preventing a Patch from Requiring Access to the Original Installation Source. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Marcu Sent: Tuesday, November 06, 2007 11:11 AM To: Schuett, Michael; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Building a patch in Visual Studio Not possible using the Setup Deployment project. You can however build patches out of the MSI's it produces using wix v3's admin image patching features. Generate an admin image of your baseline and upgrade msi's. Call torch with -ax and the msi's in the admin layouts. Then follow the wix patch building process from there. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Schuett, Michael Sent: Tuesday, November 06, 2007 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Building a patch in Visual Studio Is it possible to build a patch inside VS2005? All I've been able to generate is a useless MSI. Thanks, Mike - 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 - 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 - 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 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building a patch in Visual Studio
Visual Studio setups don't generate MsiFileHash entries for data files. Does WiX (well MsiFiler) populate these tables later? This is usually an issue when generating patches because the original install source is more likely to be required when the patch is applied. See MSDN topic Preventing a Patch from Requiring Access to the Original Installation Source. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Marcu Sent: Tuesday, November 06, 2007 11:11 AM To: Schuett, Michael; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Building a patch in Visual Studio Not possible using the Setup Deployment project. You can however build patches out of the MSI's it produces using wix v3's admin image patching features. Generate an admin image of your baseline and upgrade msi's. Call torch with -ax and the msi's in the admin layouts. Then follow the wix patch building process from there. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Schuett, Michael Sent: Tuesday, November 06, 2007 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Building a patch in Visual Studio Is it possible to build a patch inside VS2005? All I've been able to generate is a useless MSI. Thanks, Mike - 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 - 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 - 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] Advertised feature install starting
John Hall wrote: It's an HKCU registry key that would have been created for the user who installed the application, but obviously not the user who is running. Is this the default behaviour for a key in HKCU even if the feature is not advertised? Yes, for an advertised shortcut. Also, is this the expected behaviour? I thought that a copy of the MSI was stored away in c:\Windows\Installer, so why is the system not able to use that one rather than looking for the original .msi file that the bootstrapper dropped into the temp directory. It does but something's requiring source. You can set the MSI logging policy to get a verbose log when the repair is triggered. Bob, Thanks for that - I tracked it down to a component that just contains some HKCU registry entries, and so now I understand what is happening. This was triggering a repair install. The repair install was trying to reinstall some files that were marked as companion files. It turns out that I don't need to have them as companion files any more so I've changed that and the install no longer prompts for the media and all is well. However, this installing per-user on demand could be quite useful. I would like to install some files per-user as well as the registry entries. How do I make sure the files that need to be installed are available? Currently, I have a bootstrapper that includes the .msi and .cab files as resources - it drops them into the temp directory and then deletes them again once the installation has completed. I tried including the per-user files in their own cab file and embedding them in the .msi, but this doesn't work. Regards, John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building a patch in Visual Studio
In article [EMAIL PROTECTED], Wilson, Phil [EMAIL PROTECTED] writes: Does WiX (well MsiFiler) populate these tables later? I doubt WiX populates the tables unless it is the one building the MSI. You can populate them afterwards with tools such as MsiFiler from the MSI SDK, but this is just another reason why VS.NET setup projects are lame. I filed a bug on this particular issue w/VS.NET deployment projects. They declined to fix it. -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - This SF.net email is sponsored by: 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] Files protected by windows
Anything that's protected by Windows in one version should have an official installer or merge module for other Windows versions. Use that. It's got the correct setup logic in it. If you say exactly what you're trying to do I could be more helpful. Also, by using the official installer, Microsoft can patch the product if there's a bug (security or otherwise) in it. Don't expose your users to security problems by breaking the detection logic. If the installer is running on Windows 2000, the VersionNT property is set to 500. For XP it's 501, Server 2003 is 502 and Windows Vista is 600. See 'Operating System Property Values' in the Windows Installer SDK. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig0ss Sent: 07 November 2007 11:59 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Files protected by windows hi guys when im installing on win2k i get errors saying that the file being copied is being protected by windows, these files are going into the system32 folder, these files already exist on win2k but not not on others likw xp, will i need to diable these files being installed to a win2k system? Also is there a registry entry that i can check for win2k Thanks Craig0ss -- View this message in context: http://www.nabble.com/Files-protected-by-windows-tf4764277.html#a13625856 Sent from the wix-users mailing list archive at Nabble.com. - 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 - 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] Files protected by windows
One of the ways to get an idea of what's protected on Win2k/XP/Server 2003 is to run this program below, listing what's protected on the OS you run it on. It doesn't work on Vista because the protected resource implementation is different. Otherwise you generally have to get knowledgeable about what's part of the OS (or is in a separate redist like MDAC). This is occasionally useful http://support.microsoft.com/dllhelp/ with a bit of interpretation. #include stdafx.h #include windows.h #include stdio.h #include sfc.h PROTECTED_FILE_DATA aFile = {0}; FILE *stream; int main(int argc, char* argv[]) { BOOL res = true; long i=0; stream = fopen( sfcfiles.txt, w ); while (res) { res = SfcGetNextProtectedFile (NULL, aFile) ; if (res) fprintf(stream, %S\n, aFile.FileName); } fclose (stream); return 0; } Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig0ss Sent: Wednesday, November 07, 2007 3:59 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Files protected by windows hi guys when im installing on win2k i get errors saying that the file being copied is being protected by windows, these files are going into the system32 folder, these files already exist on win2k but not not on others likw xp, will i need to diable these files being installed to a win2k system? Also is there a registry entry that i can check for win2k Thanks Craig0ss -- View this message in context: http://www.nabble.com/Files-protected-by-windows-tf4764277.html#a1362585 6 Sent from the wix-users mailing list archive at Nabble.com. - 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 - 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] IIS issues during install/uninstall
Hello all- I'm getting occasional (and increasingly frustrating) issues with IIS Web Site/applications and IIS Application Pools in IIS when using a WiX 3.0 Created MSI package where the sites/app pools are getting installed on the wrong level of the metabase then not uninstalling properly, causing reinstalls/upgrades to fail. (installing to a Windows 2003 Server x64bit running IIS 6.0) Example (using adsutil ENUM /p W3SVC/3): IIS Metabase (Correct)- W3SVC/3/Root W3SVC/3/Filters IIS Metabase (Incorrect)- W3SVC/3/Root W3SVC/3/Filters W3SVC/3/W3SVC When I look under the last path ( adsutil ENUM /p W3SVC/3/W3SVC) it is showing W3SVC/3/w3svc/3 Because of this, it is not fully uninstalling the site when the MSI is getting uninstalled. I had the same issue with App Pools in IIS to the point where I took that part out of the WiX MSI and separated it into a C# application. I don't want to do that with the website because if I do, at that point, the MSI will just be a glorified xCopy. Any help will be appreciated. Code snippet (with names slightly changed) is provided below. Thanks Pierson Fragment !-- Web Service Username/Password -- util:User Id=ProgramWebServiceUser Name=[PROGRAMSERVICE_USERNAME] Password=[PROGRAMSERVICE_PASSWORD] / !-- Components and Directory Definitions -- !-- Web Directory Properties (same for all the sites) -- iis:WebDirProperties Id=WebAppProperties AnonymousAccess=no WindowsAuthentication=yes AccessSSL=yes Execute=yes Read=yes DefaultDocuments=Default.aspx Script=yes / !-- Root Directory -- DirectoryRef Id=TARGETDIR Component Id=ProgramWebSiteComponent Guid={GUID HERE} !-- Web Settings -- iis:WebSite Id=ProgramWebSite Description=Program Website - [PROGRAMWEBSITE_STANDARD_PORT]/[PROGRAMWEBSITE_SECURE_PORT] Directory=WebDir DirProperties=WebAppProperties iis:WebAddress Id=ProgramWebSiteAddress_Standard Port=[PROGRAMWEBSITE_STANDARD_PORT] Secure=no / iis:WebAddress Id=ProgramWebSiteAddress_Secure Port=[PROGRAMWEBSITE_SECURE_PORT] Secure=yes / /iis:WebSite /Component /DirectoryRef DirectoryRef Id=TARGETDIR Component Id=WebServiceConfigComponent Guid={GUID HERE}} iis:WebServiceExtension Id=ASP.NET2.0 Allow=yes File=%WINDIR%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll Description=ASP.NET v2.0.50727 UIDeletable=no / /Component /DirectoryRef !-- Assigning all the components for the UI to a single Component Group-- ComponentGroup Id=WebSite !-- Web site components-- ComponentRef Id=ProgramWebSiteComponent / ComponentRef Id=WebServiceConfigComponent/ /ComponentGroup /Fragment - 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] Change filename at runtime
Is there a method to change the name attribute of the file element during the execution of the MSI? I'm trying to set the name attribute to [SomeProperty]-filename.exe where [SomeProperty] is a number. Instead of the file being named on the system 1-filename.exe it is named [SomeProperty]-filename.exe. Is there anyway I can do this? -- View this message in context: http://www.nabble.com/Change-filename-at-runtime-tf4767466.html#a13636340 Sent from the wix-users mailing list archive at Nabble.com. - 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] Advertised feature install starting
Hi, I am trying to build the 'toolsrc' project for WIX version 3.0. I already have windows SDK version 6 installed but it failed to build MsgGen tool because of the following error: WixBuild.Common.targets(129,5): error : Please install the Windows SDK version 6000.0.0 (Windows Vista) or higher. - 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 3.0 toolset build problem.
Hi, I tried to build the 'toolsrc' project of WIX 3.0 but I am having some trouble building the MsgGen tool. I already have windows SDK version 6 installed but am getting the following error: WixBuild.Common.targets(129,5): error : Please install the Windows SDK version 6000.0.0 (Windows Vista) or higher. What am I missing? Thanks, --Leo - 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] WIX 3.0 toolset build problem.
The WiX build tools look for the SDK in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0!InstallationFolder. If this value isn't present you need to reinstall the Windows SDK. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leo ... Sent: 07 November 2007 21:54 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WIX 3.0 toolset build problem. Hi, I tried to build the 'toolsrc' project of WIX 3.0 but I am having some trouble building the MsgGen tool. I already have windows SDK version 6 installed but am getting the following error: WixBuild.Common.targets(129,5): error : Please install the Windows SDK version 6000.0.0 (Windows Vista) or higher. What am I missing? Thanks, --Leo - 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] Re ferring to Icon in an exe - How is it done?
None of the above (er, below). It needs to be IconStrawberry.exe, no brackets. That is, an exact match for the Icon/@Id value. The file IconStrawberry.exe will be included in a stream in the installer database, and at install time will be copied into a special folder under C:\Windows\Installer (although you should not rely on this). That's why you should keep the size of this file down as far as possible. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cryptonomicon Sent: 06 November 2007 00:38 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Re ferring to Icon in an exe - How is it done? Hi Mike this is all non advertised but I still don't understand. What do I need to type? I have the file with a reference id of File_ClientExe do I use square brackets or no brackets, exclamation marks, dollar sign or hash mark. do I need to put an index to the icon and if so is the first icon icon 0 or 1, is the reference to the icon placed inside the brackets or outside [File_ClientExe],0 or [File_ClientExe,0] which of File_ClientExe, !File_ClientExe, $(File_ClientExe), #File_ClientExe ,[File_ClientExe], [!File_ClientExe] , [!File_ClientExe] ,0,[File_ClientExe] ,0,[#File_ClientExe] ,0 or a thousand other combinations do I use I am afraid I need things to be spelt out real slowly assuming I know nothing -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cryptonomicon Sent: 05 November 2007 23:49 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Re ferring to Icon in an exe - How is it done? What is teh syntax to refer to an icon in an exe? I have an exe in one fragment File Id=File_ClientExe Name=StrawberryFields.exe Source=$(var.ClientRoot)StrawberryFields.exe Checksum=no ReadOnly=yes Shortcut Id=StartMenuStrawberry Directory=DocumentMenuDir Name=StrawberryFields Client WorkingDirectory='INSTALLDIR' Icon=StrawberryFields.exe IconIndex=0 / /File that contains the icon I want to use In my main module I have an icon Icon Id=IconStrawberry.exe SourceFile=[File_ClientExe],0 / but the linker cant find the exe. I have tried a variety of formats [!File_ClientExe],0 [File_ClientExe],0 File_ClientExe,0 but am having no luck. I don't want to hard code the path to the exe Is there a definition of the language syntax somewhere - there are bits and pieces around - but I have spent three days on this and am getting nowhere -- View this message in context: http://www.nabble.com/Referring-to-Icon-in-an-exe---How-is-it-done--tf475524 1.html#a13598254 Sent from the wix-users mailing list archive at Nabble.com. - 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 - 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 -- View this message in context: http://www.nabble.com/Referring-to-Icon-in-an-exe---How-is-it-done--tf475524 1.html#a13598765 Sent from the wix-users mailing list archive at Nabble.com. - 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 - 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] WIX 3.0 toolset build problem.
I just checked and the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0!InstallationFolder has the value C:\Program Files\Microsoft SDKs\Windows\v6.0\--Leo From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: Wed, 7 Nov 2007 22:04:19 +Subject: Re: [WiX-users] WIX 3.0 toolset build problem. The WiX build tools look for the SDK in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0!InstallationFolder. If this value isn’t present you need to reinstall the Windows SDK. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leo ...Sent: 07 November 2007 21:54To: [EMAIL PROTECTED]: [WiX-users] WIX 3.0 toolset build problem. Hi,I tried to build the 'toolsrc' project of WIX 3.0 but I am having some trouble building the MsgGen tool. I already have windows SDK version 6 installed but am getting the following error:WixBuild.Common.targets(129,5): error : Please install the Windows SDK version 6000.0.0 (Windows Vista) or higher. What am I missing? Thanks,--Leo- 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] cannot sign large .msi file
I know this is not a general windows installer or code signing list, but this troublesome .msi file is generated using Wix3 and I can't imagine something like this lingering in signtool.exe and I'm just the first person to stumble upon it. I have a .wxs file which via candle and light generates a .msi file which is 293,915,648 bytes. When I try to sign it using signtool.exe, I get this: The following certificate was selected: Issued to: MyCompany Inc. Issued by: VeriSign Class 3 Code Signing 2004 CA Expires: 5/28/2008 5:59:59 PM SHA1 hash: FFF Done Adding Additional Store Attempting to sign: MyInstaller.msi SignTool Error: ISignedCode::Sign returned error: 0x80092002 An error occurred during encode or decode operation. SignTool Error: An error occurred while attempting to sign: MyInstaller.msi Number of files successfully Signed: 0 Number of warnings: 0 Number of errors: 1 The error code description translates to 'something bad happened'. When I remove enough files to get it down to 287,634,860 bytes, I can sign it. There's likely some size in the middle that's magic I would guess. The two above tests were done with the CompressionLevel=high in the .wxs file. I have tried with CompressionLevel=none, and it gives an installer in the 420MB range and it won't sign, either. I'm still messing with this to see if there is a magic number for the final file size. I know I could generate an external .cab file, but then the user will have to download both files or have some kind of self-extracting archive or... and none of those are considered acceptable by my customer. They want one file, and no extra disk space required during install. I'm using Wix 3.0.3419.0 and the signtool.exe from the latest Platform SDK. I've searched around and I have yet to find anywhere that says I can't have an .msi file this size. Not knowing the actual changes made to the file as part of the signing process, I don't know if there is an issue with the .msi file or if this is an issue with signtool. My bet is this is an issue with Wix3's generated .msi file, but again, I don't know where to start. Any and all help is appreciated. -- Shawn Edwards Beware programmers with screwdrivers. Or, for that matter, any other mixed drink. - 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] cannot sign large .msi file
In article [EMAIL PROTECTED], Shawn Edwards [EMAIL PROTECTED] writes: I have a .wxs file which via candle and light generates a .msi file which is 293,915,648 bytes. When I try to sign it using signtool.exe, I get this: The following certificate was selected: Issued to: MyCompany Inc. Issued by: VeriSign Class 3 Code Signing 2004 CA Expires: 5/28/2008 5:59:59 PM SHA1 hash: FFF You'll have to split some of the file payload out into an external CAB file and sign the CAB file separately. Its a known issue with the signing tool. -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - This SF.net email is sponsored by: 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] cannot sign large .msi file
On Nov 7, 2007 5:57 PM, Richard [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], Shawn Edwards [EMAIL PROTECTED] writes: I have a .wxs file which via candle and light generates a .msi file which is 293,915,648 bytes. When I try to sign it using signtool.exe, I get this: The following certificate was selected: Issued to: MyCompany Inc. Issued by: VeriSign Class 3 Code Signing 2004 CA Expires: 5/28/2008 5:59:59 PM SHA1 hash: FFF You'll have to split some of the file payload out into an external CAB file and sign the CAB file separately. Its a known issue with the signing tool. Thank you for your quick response! This is good and bad news; good to know that I'm not doing something wrong, but... I believe you that's it's a known problem, but my customer doesn't. They want an explanation/bug report/knowledge base article/note from Bill Gate's mom/etc. Do you know of somewhere this has been discussed in the past? Thanks again for your help. -- Shawn Edwards Beware programmers with screwdrivers. Or, for that matter, any other mixed drink. - 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] using fragment files with VisualStudio
Hi, Looking for comfortable way to add to my Wix solution, is there a way other than creating them as new project and adding it to the solution? - 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] upgrade and 3 field version numbers
Nitin wrote: I ran in some issue with upgrades, and when I checked the logs, I found that the version numbers were 4 fields ( 1.0.0.1 ). MSDN tells me that it will ignore the 4^th part, so I have changed my version to 1.0.1, which works. The problem is I show my product version (in about box) based on my .net assembly version, which has 4 fields, but for MSI, I use 3 fields, so Add/remove shows 3 fields. I would like to know why MSI doesn't support 4 field versions. Any best practices for versioning? The fourth field is for updates and is used for file versions but not for product versions. -- sig://boB http://joyofsetup.com/ - 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] WIX 3.0 toolset build problem.
Leo ... wrote: I just checked and the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0!InstallationFolder has the value C:\Program Files\Microsoft SDKs\Windows\v6.0\ Which OS/edition are you running? Is there a C:\Program Files\Microsoft SDKs\Windows\v6.0\Include directory? What does the build show for PlatformSdkIncludePath=? -- sig://boB http://joyofsetup.com/ - 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] MSI installer deployment through SMS 2003 ?
Hi guys, I developed a installer using WiX3.0 and VS2005 which is working fine on WinXP. I wanted to deploy this MSI installer through SMS 2003. How I can do this? Same MSI installer will work or modifications are required at installer level. Thanks!! VK __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - 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] cannot sign large .msi file
Kelly Leahy wrote: See where it says: *Note* When signing an executable file that is larger than approximately 300 megabytes, you should use catalog signing with the _MakeCat_ http://msdn2.microsoft.com/en-us/library/aa386967.aspx tool rather than use the SignTool tool. This is because, depending on available system resources, some applications may not be able to verify the binary signature of a large file. For more information, see KB article _95_ http://go.microsoft.com/fwlink/?linkid=84540. It also sounds like the bug that's most visible in VS2005 SP1. See http://blogs.msdn.com/heaths/archive/2007/01/11/workaround-for-error-1718.aspx, for example. -- sig://boB http://joyofsetup.com/ - 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] How to Start a Service?
I am trying to start a service Foobar.exe . I created a sample.msi using the following code. When I run sample.msi under administrator I am getting this following Error. Error 1920. Service 'Foobar.exe' (Foobar.exe) failed to start. Verify that you have sufficient privileges to start system services. MSI (s) (8C:24) [17:03:56:442]: Product: Foobar 1.0 -- Error 1920. Service 'Foobar.exe' (Foobar.exe) failed to start. Verify that you have sufficient privileges to start system services. Shall any one please let me know How to start a service? I appreciate your Help . Thanks. Sample.wxs Code for sample.msi ?xml version='1.0' encoding='windows-1252'? Wix xmlns='http://schemas.microsoft.com/wix/2003/01/wi' Product Name='Foobar 1.0' Id='223C2E86-57FE-40aa-B748-35A45FF3DF30' Language='1033' Codepage='1252' Version='1.0.0' Manufacturer='Acme Ltd.' Package Id='----' Keywords='Installer' Description=Acme's Foobar 1.0 Installer Comments='Foobar is a registered trademark of Acme Ltd.' Manufacturer='Acme Ltd.' InstallerVersion='100' Languages='1033' Compressed='yes' SummaryCodepage='1252' / Media Id='1' Cabinet='Sample.cab' EmbedCab='yes' DiskPrompt=CD-ROM #1 / Property Id='DiskPrompt' Value=Acme's Foobar 1.0 Installation [1] / Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id='Acme' Name='Acme' Directory Id='INSTALLDIR' Name='Foobar10' LongName='Foobar 1.0' Component Id='FoobarExe_Component' Guid='BF5335E2-E60D-4b38-9772-30DAE2F20C6D' SharedDllRefCount='no' KeyPath='no' NeverOverwrite='no' Permanent='no' Transitive='no' Win64='no' Location='either' File Id='FoobarExe_File' Name='Foobar.exe' Source='Foobar.exe' ReadOnly='no' Compressed='yes' KeyPath='yes' Vital='yes' Hidden='no' System='no' Checksum='no' DiskId='1' / ServiceInstall Id='FoobarExe_ServiceInstall' DisplayName='foobar Service' Name='FoobarExe' ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' / ServiceControl Id='FoobarExe_ServiceControl' Name='Foobar.exe' Start='install' Stop='uninstall' Remove='uninstall' / /Component /Directory /Directory /Directory -- View this message in context: http://www.nabble.com/How-to-Start-a-Service--tf4768465.html#a13639641 Sent from the wix-users mailing list archive at Nabble.com. - 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] Version 3.0 - Getting Started
Hi, Is there a tutorial available for Version 3? I tried following the tutorial in the online help, but I'm running into a few errors and was hoping there might be something else available. Thanks, Craig --- http://www.overlandnavigator.com Touchscreen Friendly GPS Mapping No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.15.24/1115 - Release Date: 11/7/2007 9:21 AM - 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] How to Start a Service?
In article [EMAIL PROTECTED], ar [EMAIL PROTECTED] writes: Shall any one please let me know How to start a service? Your service names don't match: ServiceInstall Id='FoobarExe_ServiceInstall' DisplayName='foobar Service' Name='FoobarExe' ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' / ServiceControl Id='FoobarExe_ServiceControl' Name='Foobar.exe' Start='install' Stop='uninstall' Remove='uninstall' / In one place you call it 'FoobarExe' and in the other place you call it 'Foobar.exe'. -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - This SF.net email is sponsored by: 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] Change filename at runtime
Matt Ziegler wrote: Is there a method to change the name attribute of the file element during the execution of the MSI? I'm trying to set the name attribute to [SomeProperty]-filename.exe where [SomeProperty] is a number. Instead of the file being named on the system 1-filename.exe it is named [SomeProperty]-filename.exe. Is there anyway I can do this? You can use CopyFile to make a copy with a name defined at runtime. You can't change the installed name; MSI relies on it to check component state. -- sig://boB http://joyofsetup.com/ - 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] Advertised feature install starting
John Hall wrote: *However, this installing per-user on demand could be quite useful. I would like to install some files per-user as well as the registry entries. How do I make sure the files that need to be installed are available?* That requires caching the real MSI and any external cabs. The .msi file that MSI caches is stripped of all embedded cabs. -- sig://boB http://joyofsetup.com/ - 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] cannot sign large .msi file
Well, I couldn't find a bug report either, but here's somebody talking about a fix they used (they used the tool from Mono with minor modifications) http://tondrej.blogspot.com/ Kelly Shawn Edwards [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 11/07/2007 08:55 PM Please respond to [EMAIL PROTECTED] To wix-users@lists.sourceforge.net cc Subject Re: [WiX-users] cannot sign large .msi file On Nov 7, 2007 5:57 PM, Richard [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], Shawn Edwards [EMAIL PROTECTED] writes: I have a .wxs file which via candle and light generates a .msi file which is 293,915,648 bytes. When I try to sign it using signtool.exe, I get this: The following certificate was selected: Issued to: MyCompany Inc. Issued by: VeriSign Class 3 Code Signing 2004 CA Expires: 5/28/2008 5:59:59 PM SHA1 hash: FFF You'll have to split some of the file payload out into an external CAB file and sign the CAB file separately. Its a known issue with the signing tool. Thank you for your quick response! This is good and bad news; good to know that I'm not doing something wrong, but... I believe you that's it's a known problem, but my customer doesn't. They want an explanation/bug report/knowledge base article/note from Bill Gate's mom/etc. Do you know of somewhere this has been discussed in the past? Thanks again for your help. -- Shawn Edwards Beware programmers with screwdrivers. Or, for that matter, any other mixed drink. - 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 ** This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Unless indicated to the contrary: it does not constitute professional advice or opinions upon which reliance may be made by the addressee or any other party, and it should be considered to be a work in progress. Unless stated otherwise, this communication does not form a prescribed statement of actuarial opinion under American Academy of Actuaries guidelines. **- 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] cannot sign large .msi file
How about the last lines in this article: http://msdn2.microsoft.com/en-us/library/aa387764.aspx See where it says: Note When signing an executable file that is larger than approximately 300 megabytes, you should use catalog signing with the MakeCat tool rather than use the SignTool tool. This is because, depending on available system resources, some applications may not be able to verify the binary signature of a large file. For more information, see KB article 95. Shawn Edwards [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 11/07/2007 08:55 PM Please respond to [EMAIL PROTECTED] To wix-users@lists.sourceforge.net cc Subject Re: [WiX-users] cannot sign large .msi file On Nov 7, 2007 5:57 PM, Richard [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], Shawn Edwards [EMAIL PROTECTED] writes: I have a .wxs file which via candle and light generates a .msi file which is 293,915,648 bytes. When I try to sign it using signtool.exe, I get this: The following certificate was selected: Issued to: MyCompany Inc. Issued by: VeriSign Class 3 Code Signing 2004 CA Expires: 5/28/2008 5:59:59 PM SHA1 hash: FFF You'll have to split some of the file payload out into an external CAB file and sign the CAB file separately. Its a known issue with the signing tool. Thank you for your quick response! This is good and bad news; good to know that I'm not doing something wrong, but... I believe you that's it's a known problem, but my customer doesn't. They want an explanation/bug report/knowledge base article/note from Bill Gate's mom/etc. Do you know of somewhere this has been discussed in the past? Thanks again for your help. -- Shawn Edwards Beware programmers with screwdrivers. Or, for that matter, any other mixed drink. - 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 ** This communication is intended solely for the addressee and is confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Unless indicated to the contrary: it does not constitute professional advice or opinions upon which reliance may be made by the addressee or any other party, and it should be considered to be a work in progress. Unless stated otherwise, this communication does not form a prescribed statement of actuarial opinion under American Academy of Actuaries guidelines. **- 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