[WiX-users] Dependent Windows Services
I never figured out a built-in way (in WIX) to start/stop dependent Windows services automagically. For example, the server has IIS installed along with SMTP POP3. When I stop IIS (via ServiceControl), the dependent services also get stopped, but when I restart IIS (via ServiceControl), the dependent services don't get started. I can include extra ServiceControl elements for all the IIS dependent services, but the MSI will throw and exception if one these dependent services hasn't been installed. In short, is there a way to achieve the above functionality magically (meaning, when I start/stop a specific service, all the dependent services would start/stop based on which service is installed)? Thanks. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Dependent Windows Services
I think that is a good idea - to invoke netstart/stop and not worry about the return code. I'll give it a shot and let everyone know how it works out... Thanks. On Nov 29, 2007 4:07 PM, Kelly Leahy [EMAIL PROTECTED] wrote: I dont' think windows even has such a feature, so I'd be surprised if MSI does. I think that's the whole reason why iisreset is a program and they don't just rely on people having to do net start / net stop commands. By the way, if you know the dependencies, you could just do net start and not check the return value, couldn't you? Or does MSI also complain when net start throws an error? Kelly *Dhaval Patel [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 11/29/2007 04:00 PM To wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net cc Subject [WiX-users] Dependent Windows Services I never figured out a built-in way (in WIX) to start/stop dependent Windows services automagically. For example, the server has IIS installed along with SMTP POP3. When I stop IIS (via ServiceControl), the dependent services also get stopped, but when I restart IIS (via ServiceControl), the dependent services don't get started. I can include extra ServiceControl elements for all the IIS dependent services, but the MSI will throw and exception if one these dependent services hasn't been installed. In short, is there a way to achieve the above functionality magically (meaning, when I start/stop a specific service, all the dependent services would start/stop based on which service is installed)? Thanks. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ 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. ** - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Xml Beautifier
Define an Xml beautifier? I take input from users and modify Xml files all the time without losing the beauty of the Xml file - beauty for me is proper indentation... On Nov 29, 2007 4:58 PM, si [EMAIL PROTECTED] wrote: Greetings, Has anyone successfully integrated an xml beautifier into WiX after XmlFile and XmlConfig have done their work? It would be nice to leave files with a cleaner appearance, especially when many changes are required and all the whitespace is lost. cheers si - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Dependent Windows Services
Using the following snippet does the trick: InstallExecuteSequence !-- Reset IIS during all maintenance-type calls -- Custom Action='ResetIIS' After='InstallInitialize'NOT Installed OR Installed OR REINSTALL/Custom /InstallExecuteSequence !-- Needed to suppress the Console Window -- Binary Id=wixca src=wixca.dll/ Property Id=QtExecCmdLine Value='[System64Folder]iisreset' / CustomAction Id='ResetIIS' Return='ignore' BinaryKey='wixca' DllEntry=CAQuietExec Execute=immediate / I wouldn't mind someone commenting on my CustomAction conditions (I am a n00b when it comes to those conditions). I have logged all scenarios (reinstall/install/uninstall) and IIS gets reset every time - of course all the dependent services get started/stopped because of the call. I guess it depends on different scenarios, too, but in my case I am creating a custom AppPool which locks the installation folder until IIS is reset. So the simple call above during Uninstall/Reinstall forces IIS to reset, there by freeing up the locked folder. Needless to mention, because the folder is locked, if someone runs the MSI to uninstall the product, the process fails, and WIX complains that access to folder is denied. It is very weird, and am not sure if other people have had similar experiences. But as pointed above, resetting IIS this way, seems to be working for me. Thanks for the input! Again, I wouldn't mind someone else verifying my Custom Action condition in the snippet above. On Nov 29, 2007 4:33 PM, Dhaval Patel [EMAIL PROTECTED] wrote: I think that is a good idea - to invoke netstart/stop and not worry about the return code. I'll give it a shot and let everyone know how it works out... Thanks. On Nov 29, 2007 4:07 PM, Kelly Leahy [EMAIL PROTECTED] wrote: I dont' think windows even has such a feature, so I'd be surprised if MSI does. I think that's the whole reason why iisreset is a program and they don't just rely on people having to do net start / net stop commands. By the way, if you know the dependencies, you could just do net start and not check the return value, couldn't you? Or does MSI also complain when net start throws an error? Kelly *Dhaval Patel [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 11/29/2007 04:00 PM To wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net cc Subject [WiX-users] Dependent Windows Services I never figured out a built-in way (in WIX) to start/stop dependent Windows services automagically. For example, the server has IIS installed along with SMTP POP3. When I stop IIS (via ServiceControl), the dependent services also get stopped, but when I restart IIS (via ServiceControl), the dependent services don't get started. I can include extra ServiceControl elements for all the IIS dependent services, but the MSI will throw and exception if one these dependent services hasn't been installed. In short, is there a way to achieve the above functionality magically (meaning, when I start/stop a specific service, all the dependent services would start/stop based on which service is installed)? Thanks. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ 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. ** - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] New Windows Group Permissions
Couple of questions: 1) Is it possible to create a new Windows group in WIX2.X? 2) We have some application-level users that need write permissions to the TempFolder for compiling Web Services' related temporary files - only issue is that I can't access the Permission element outside a CreateFolder / element. Is there a way to alter permissions on a pre-exisiting folder? Thanks in advance for any responses/ideas. - 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] How to deploy all the files inside the folder rather than specifying each files
You can use heat.exe to make your life easier. There are various posts on how to use it to obtain a WIX fragment that you can directly use in your poroject. On 7/19/07, Pierson Lee (Volt) [EMAIL PROTECTED] wrote: There is not a way to specify a directory. You will need to specify each file explicitly to have it be part of the installation *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Lingappa *Sent:* Thursday, July 19, 2007 3:48 AM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] How to deploy all the files inside the folder rather than specifying each files Hi, I need to specify contents of whole directory needs to be installed instead specifying each file names. Currently i am using like mentioned below: ... ... ... ... I need to specify all the files. Problem any file is being added to the directory again i need to add the file in the wxs source. Is there a to specify the directory instead of files? Your help will be greatly appreciate. Thanks in advance. Regards, Lingappa -- View this message in context: How to deploy all the files inside the folder rather than specifying each fileshttp://www.nabble.com/How-to-deploy-all-the-files-inside-the-folder-rather-than-specifying-each-files-tf4109546.html#a11686200 Sent from the wix-users mailing list archivehttp://www.nabble.com/wix-users-f4470.htmlat Nabble.com http://nabble.com/. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft 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 - 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] Sqlscript problem
This has been discussed extensively... What is in your .sql script file? Do you have all the batches delimited by GO statements? Use SQL Server Management Studio/Enterprise Manage to load and save your scripts. Let us all know if this helps. On 6/2/07, rajiv ramanan [EMAIL PROTECTED] wrote: Hi all, I seem to run into a problem while using the sqlscript tag. The following is the code i used and im using wix version 2.05. The script i am using is just a sample to create a table. The query is fine. When i used sqlstring the script is executed and when i used script its not working. Please help me out with this. I have tried saving the file in unicode , utf8 utf 16, ansi types also . but no results. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/01/wi; !--Wix xmlns:Sql=http://schemas.microsoft.com/wix/SqlExtension; -- Product Id=02C4F985-DFC1-4e47-B432-6D7771636894 Name='SQL app 1.0' Language='1033' Codepage='1252' UpgradeCode='16807415-8849-479d-A351-A3F570C9BF43' Version='1.0.0' Manufacturer='Cibrax Ltd.' Package Keywords='Installer' Description=SQL App 1.0 Installer Id=5FBD2673-09A8-4f13-A3B8-D731D7EE86D0 Comments='SQL app is a registered trademark of Cibrax Ltd.' Manufacturer='Cibrax Ltd.' InstallerVersion='100' Languages='1033' Compressed='yes' SummaryCodepage='1252' / Media Id='1' Cabinet='Sample.cab' EmbedCab='yes' / !--Sql:SqlDatabase Id=MySqlDatabase Database=master Server=localhost CreateOnInstall=yes ContinueOnError=yes/Sql:SqlDatabase-- Property Id='INSTALLDIR'C:\Documents and Settings\Rajiv_Ramanan\Desktop\nbs\/Property Directory Id='TARGETDIR' Name='SourceDir' !--Directory Id='ProgramFilesFolder' Name='PFiles'-- Directory Id='INSTALLDIR' Name='TestSQL' Component Id=MySqlComponent Guid=09AF7CF7-CE63-42b4-BF57-720983F8BBED KeyPath=yes File Id=one DiskId=1 Name=one.txt Source=C:\Documents and Settings\Rajiv_Ramanan\Desktop\/ CreateFolder/CreateFolder SqlDatabase Instance=sqlinstance Id=MySqlDatabase CreateOnInstall=yes ContinueOnError=yes Database=master Server=(local) !--SqlString Id=InsertAdminPerms2 ExecuteOnInstall=yes SQL =create table rajiv3(age int) /-- !--SqlScript Id=CreateTables ExecuteOnInstall=yes BinaryKey=CreateTablesBin ContinueOnError=yes /SqlScript-- /SqlDatabase SqlScript Id=CreateTables ExecuteOnInstall=yes BinaryKey=CreateTablesBin ContinueOnError=yes SqlDb=MySqlDatabase Sequence=001/SqlScript /Component /Directory /Directory !--/Directory-- Binary Id=CreateTablesBin src=C:\Documents and Settings\Rajiv_Ramanan\Desktop\SQLQuery1.sql/Binary Feature Id='Complete' Level='1' Description=Full Title=Full Installation ComponentRef Id='MySqlComponent' / /Feature /Product /Wix -- View this message in context: http://www.nabble.com/Sqlscript-problem-tf3859121.html#a10933027 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Determine IIS Application Path After Installation?
I don't think I understand your question, but if you are simply trying to reference the location where the Web app is installed, then how about using properties? You can reference properties (like INSTALLDIR or TARGETDIR [these are hypothetical names; look at the tramontana tutorial for details]) and use them later in the CustomAction. I am sure you are grabbing the metabase path somewhere - via the UI/user input... On 6/1/07, S C [EMAIL PROTECTED] wrote: I am sort-of familiar with using aspnet_regiis to set v2.0 on a particular web site. But I am dealing with a web site that is v1.1 and install a new virtual directory/webapplication as 2.0. The Metabase path for the new install could be literally anywhere, so I think I need to capture the Metabase path to a variable and then feed that to aspnet_regiis in a Custom Action. Do I need to scan the entire Metabase (yuck) to find what was just installed, and if so, how? Thanks. -- Make every IM count. Download Windows Live Messenger and join the i'm Initiative now. It's free. Make it count!http://im.live.com/messenger/im/home/?source=TAGWL_June07 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Associating Files Shortcuts (Rob's Version)
Most of my stuff gets deployed on the server side where the only users are admins and support staff. I usually point them to the config XML files in my documentation, but it is always useful to have a shortcut in the Programs Menu folder (it also minimizes documentation). Another nice functionality is to be able to associate a file with a default application; for example a *.config file gets associated with notepad.exe in my case. The WIX tutorial covers this possibility [of associating files with an application that is part of the current MSI], but leaves us wanting more. I was also able to incorporate Rob's tip on including an uninstall shortcut for the application in the Programs Menu folder (I thought it would be nice to point out this functionality on the forum since I had some hard time finding Rob's original post - maybe I need to upgrade my Google'in skills). Since I wasn't able to find any posts regarding this functionality, I thought it would be nice to make a post with both these minor enhancements. Requirement 1) Create shortcuts for the user in the Programs Menu folder that point to the Application Configuration file and allows the user to uninstall the product. 2) Associate the Application Configuration file with notepad.exe so that when the users open it, it opens in Notepad by default (you can generalize this feature and use it however you please) Solution Start off by declaring a Property that will search for notepad.exe. We will use this property at a later stage to associate the .config file with Notepad. ?xml version='1.0' encoding='windows-1252'? Wix xmlns='http://schemas.microsoft.com/wix/2003/01/wi' Product Name='FooBar 1.0' Id='YOUR-GUID' Language='1033' Codepage='1252' Version='1.0.0.0' Manufacturer='Scrooge McDuck, Inc.' UpgradeCode='YOUR-GUID' Package Id='----' Keywords='Installer' / Media Id='1' Cabinet='FDLEArchive.cab' EmbedCab='yes' DiskPrompt=CD-ROM #1 / Property Id='NOTEPADEXE' DirectorySearch Id='NotePadContainer' Path='[SystemFolder]' Depth='0' FileSearch Id='NotepadFile' Name='notepad.exe'/ /DirectorySearch /Property Now we create the Programs hierarchy as usual and then reference the 'NOTEPAD' property in our 'Verb' element (highlighted yellow). Also note that the same file is being added as a shortcut and it references the 'ShortcutFolder' (highlighted pink, or salmon for the sharp-eyed). Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id='SMFolder' Name='Scrooge' LongName='Quack Company' Directory Id='INSTALLDIR' Name='Files' LongName='Folder With Files' Component Id='AppCONFIG' Guid='YOUR-GUID' DiskId='1' File Id='AppConfigFile' Name='App.cfg' LongName ='MyFile.exe.config' Source='MyFile.exe.config' Vital='yes' Shortcut Id='ConfigEXEShortcut' Name=' ConfEXE.cfg' Directory='ShortcutFolder' LongName='Application Configuration File' Description='Lets you configure settings for the McDuck Utility.' / /File ProgId Id='XMLApp' Description='XML Configuration File' Extension Id='config' ContentType='application/config' Verb Id='Open' Sequence='10' Command='Open' Argument='%1' Target='[NOTEPADEXE]'/ /Extension /ProgId /Component /Directory /Directory /Directory /Directory Now we create the Programs Menu hierarchy. Notice that the Directory Id is 'ShortcutFolder'. Later on, the uninstaller shortcut also refers to this same Id. THIS SECTION IS COMPLETE RIP-OFF FROM ROB'S ORIGINAL POST. I lost the link to Rob's original blog post, but maybe Rob can reply with the link to his original post - he had some nice points about why he is using System64Folder. I am pretty sure it is on his web site somewhere. Directory Id=ProgramMenuFolder Name=PMFolder Directory Id='ShortcutFolder' Name='MP' LongName='My Product 1.0' Component Id='Shortcuts' Guid='YOUR-GUID' Registry Root=HKCU Key=SOFTWARE\My Company\ProductName Type=string KeyPath=yes Value=Uninstall / Shortcut Id=UninstallProduct Name=unin.msi LongName =Uninstall My Product 1.0 Target=[System64Folder]msiexec.exe Arguments =/x [ProductCode] Directory=ShortcutFolder Description=Uninstalls My Product 1.0. / RemoveFolder Id=RemoveShortcuts On=uninstall / /Component /Directory /Directory That is it! I hope this helps all the newbies (like myself) out there. If you were to install an app using
Re: [WiX-users] custom action to reg NET 2.0
Hehe... good question. I was wondering how come Don didn't ask this before. I have to write my own 'undo' Custom Action, that only runs during uninstall. The reason why these actions are safe, is because the command prompt will execute the command, and report an error (which the user is unable to see) - so there are essentially 2 cases: a) the ExeCommand in the CA succeeds, or b) the CA in the ExeCommand fails. In my case, it doesn't matter in either case, because if the COM .dll is registered, it'll be unregistered, and if the COM .dll is not registered (this must also mean that someone did something bad), the ExeCommand will still allow WIX to finish its uninstallation procedure. Here is my solution: CustomAction Id='Uninstallation' Directory='INSTALLDIR' Win64='no' ExeCommand='[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.exe /unregister [ProgramFilesFolder]MyCompany\MyProduct\MyLibrary.dll' Return='check' / InstallExecuteSequence !-- Only run before uninstallation -- Custom Action='Uninstallation' Before='RemoveFiles'Installed AND NOT REINSTALL/Custom /InstallExecuteSequence Notice that I run the 'uninstallation' CA only during uninstall, and not reinstall - you can change this behavior to your needs. Let me if this helps :) On 3/22/07, pobox77 [EMAIL PROTECTED] wrote: Hi Dhaval, Does uninstall work too? I mean will the dll also deregistered if I uninstall the package? Thanks in advance, Peter Don Tasanasanta wrote: Your solution helped me find what was wrong with mine. For some reason the CA didn't like what I was putting in for the Directory value. I put in INSTALLDIR and everything worked great. Thanks! From: Dhaval Patel [mailto: [EMAIL PROTECTED] Sent: Friday, March 09, 2007 4:59 PM To: Don Tasanasanta Subject: Re: [WiX-users] custom action to reg NET 2.0 Here is one of my CustomAction elements that I have used in different projects - I don't see anything in your CA that will not allow it to work, but maybe you want to change the ExeCommand attribute to something like I have and give it a shot: InstallExecuteSequence Custom Action='Installation' After='InstallFinalize'NOT Installed/Custom /InstallExecuteSequence CustomAction Id='Installation' Directory='INSTALLDIR' Win64='no' ExeCommand='[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.ex e /codebase [ProgramFilesFolder]MyComapny\MyProduct\MyProduct.dll' Return='check' / This seems to work just fine (i.e. it successfully registers the .dll for COM Interop in the registry). I think I had the same issue that you are having, but I figured out the solution through trial and error, and then I forgot all about it :) The problem I think is that you may think WIX will execute the CA from within the Directory ([FRAMEWORKBASEPATH]v2.0.50727 in your case) attribute, but that probably is not the case. Notice in my case how I explicitly pass all the paths to the ExeCommand attribute directly - I don't even worry about the Directory attribute (I assume you can set it to any valid DirectoryId within your current WIX project, if you decide to use the technique I am using). This is probably the reason why it is working in my case, and not yours. Let us all know if this fixes your issue :) On 3/8/07, Don Tasanasanta [EMAIL PROTECTED] wrote: I have been banging my head against this all day... I'm trying to get aspnet_regiis.exe to run and set the ASPNET version to 2.0 for my virtual directory. Here is my custom action... CustomAction Id=SetAspNet Return=asyncWait Directory=[FRAMEWORKBASEPATH]v2.0.50727 Execute=commit ExeCommand=aspnet_regiis.exe -s W3SVC/1/ROOT/MYWebsite -norestart / Where FRAMEWORKBASEPATH is the path to Framework under Microsoft.NET in the WINDOWS folder. I have also tried CustomAction Id=VIA3AdminAspNet Return=asyncWait Property=[ASPNETREGPATH] Execute=commit ExeCommand=-s W3SVC/1/ROOT/MyWebsite -norestart / Where ASPNETREGPATH is the entire path plus aspnet_regiis.exe I have also tried changing the Execute to immediate and sequencing the custom action after installfinalize. Every time I run I get a 1631 return from my custom actions. The command line works just fine when run from a cmd prompt. What am I missing here? - 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=DEVDE V ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join
Re: [WiX-users] C# .dll
Folks like me, meaning people who have minuscule experience programming in VBScript or C++. I pretty much started learning to program in C# back in 2002, graduated last year, and am currently working as a C#/ASP.NET developer. Of course I could embark on a journey to learn C++, but I think the rest of the world is moving to .NET, especially with the advent of C# 3.0 (LINQ), CLR 3.5, etc. I rather spend time on exploring new features of C# 3.0 and CLR 3.5. I am still a WIX newbie by any means - I hope I didn't offend you by saying 'people like me' :) In essence what I was trying to say is that folks who excel in C# will be able to exploit WIX's features to a greater extent. Plus I think if this happens, many developers will start adopting WIX right away. I still have a few colleagues who don't want to use just because they can't pass values read from a WIX User dialog to a C# .dll. One (hypothetical) example most people would put this functionality to use is writing their own custom SQL connection strings using the SqlConnectionStringBuilder. On 3/19/07, Rob Mensching [EMAIL PROTECTED] wrote: I haven't blogged it. This one requires more research that my recent avoid COM advertisement entry because I haven't lived it closely. I got enough reports of trickiness with managed CustomActions to just stay away. The root issue comes down to having the wrong version of the .NET Framework loaded. For example, let's say you have a 1.1 CustomAction but need to install a 2.0 Framework assembly to the GAC. My understanding was that the easy/obvious way to use the 1.1 CustomAction caused the 1.1. Framework to be loaded and that caused the 2.0 Framework install to fail later (because the 1.1. Framework won't understand it). Again, the details are fuzzy because I haven't stepped through the debugger on this issue myself. Basically, it comes down to the fact that the Windows Installer team needs to look at what managed CustomActions mean and do the right thing when looking at the complete picture. They know things about the all the different ways the Windows Installer gets invoked that you and I would struggle to think of. For example, what happens if you had a Shell Extension written in managed code then did faulted in an MSI via Extension advertisement? Do all the correct .NET Frameworks get loaded? Are you going to test it? smile/ -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Joe Kaplan Sent: Friday, March 16, 2007 11:43 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] C# .dll Hi Rob, Would you care to elaborate on this part a bit? If you already blogged it, I apologize. I've followed the evolution of this issue for a while now and I am always curious to learn more about it. To my knowledge, I don't remember you or anyone else discussing any specific issues regarding loaded the CLR into the installer process. I'm definitely of the opinion that these things are best avoided for now due to the lack of support for it at the WI level. On the other hand, I also believe it is just a matter of time before this needs to happen in a fully supported way. Basically, I'm trying to understand what the solution might look like in order to overcome some of the more subtle issues. What's so neat? :) Thanks! Joe K. - Original Message - From: Rob Mensching [EMAIL PROTECTED] To: Levi Wilson [EMAIL PROTECTED]; Dhaval Patel [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Sent: Friday, March 16, 2007 12:43 PM Subject: Re: [WiX-users] C# .dll More importantly, the Windows Installer doesn't support it today. There are actually neat problems you can introduce by loading the .NET Framework into the Windows Installer process. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson Sent: Friday, March 16, 2007 10:40 AM To: Dhaval Patel Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] C# .dll I don't know for certain, but my guess would be that there's no guarantee that the .NET Framework has been installed on the client. On 3/16/07, Dhaval Patel [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Will WIX 3.0 be adding the capability to call C# .dll files? If not, WHY? :) - 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.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash
Re: [WiX-users] Creating SqlDatabase with/without Windows Authentification
Good stuff! Thanks for sharing.
On 3/19/07, pobox77 [EMAIL PROTECTED] wrote:
Here my solution:
util:User Id=SQLUser Name=[SQLUSERNAME]
Password=[SQLUSERPASSWORD] /
...
!--database authentification, SQLUSER will be used --
!-- SQLUSERNAME and SQLUSERPASSWORD will be entered in a customized
dialog --
Component Id=CreateDBUser DiskId=1 Guid=YOURGUID
sql:SqlDatabase Id=dbUser Server=[SQLSERVER]
Database=[SQLDBNAME] CreateOnInstall=yes ConfirmOverwrite=yes
DropOnReinstall=no DropOnUninstall=no User=SQLUser
sql:SqlScript Id=CreateTablesSqlScriptUser
ContinueOnError=no
ExecuteOnInstall=yes ExecuteOnReinstall=no Sequence=002
BinaryKey=CreateTablesBin User=SQLUser /
/sql:SqlDatabase
ConditionWIN_AUTH_DB=False/Condition
/Component
!-- Windows authentification, without User attribute --
Component Id=CreateDBWindows DiskId=1 Guid=YOURGUID
sql:SqlDatabase Id=dbWindows Server=[SQLSERVER]
Database=[SQLDBNAME] CreateOnInstall=yes ConfirmOverwrite=yes
DropOnReinstall=no DropOnUninstall=no
sql:SqlScript Id=CreateTablesSqlScriptWindows
ContinueOnError=no ExecuteOnInstall=yes ExecuteOnReinstall=no
Sequence=002 BinaryKey=CreateTablesBin /
/sql:SqlDatabase
ConditionWIN_AUTH_DB=True/Condition
/Component
...
!-- this script will be used for both above --
Binary Id=CreateTablesBin SourceFile=Create XCB
Tables_Views_StoredProcedures.sql
/Binary
...
!-- the property WIN_AUTH_DB will be set using a radio button
control in the same customized dialog
as username and password --
!-- the property must be global, eg. its name uses capitals
only
--
Control Id=SecurityButtons1 Type=RadioButtonGroup X=90
Y=142 Width=197 Height=30 Property=WIN_AUTH_DB
/Control
...
RadioButtonGroup Property=WIN_AUTH_DB
RadioButton Text={\DlgFont8}amp;Integrated Security (Windows
authentification) Value=True X=0 Y=0 Width=206 Height=12 /
RadioButton Text={\DlgFont8}amp;User Name and Password
Value=False X=0 Y=15 Width=206 Height=15 /
/RadioButtonGroup
Dhaval Patel-4 wrote:
I'd be interested in seeing your solution, Peter. Can you post your
solution
on the Wix-users list for future reference? I feel this shouldn't be
hard,
but if you already have it, then why reinvent the wheel!
Thanks in advance.
On 3/13/07, pobox77 [EMAIL PROTECTED] wrote:
Thanks Dana,
I've just found the same solution about an hour ago.
Just a note for people having similar problem:
The property used by the radio button and in the condition must be a
global
property
(e.g. the name of it should only have capitals) otherwise it doesn't
work.
Peter
Dana Gutride wrote:
This is not possible within the sql database tag right now. There is
a
bug/feature request in for this exact functionality, but as far as I
can
tell, it hasn't been added yet. The only way to do this is to have
two
sqldatabase tags in separate components and then add conditions for
the
components based on the radio button's property.
Dana
On 3/13/07, pobox77 [EMAIL PROTECTED] wrote:
Sorry, the snippet was wrong formatted.
pobox77 wrote:
Hi,
I would like to create a SqlDatabase either with Username+Password
or
with
Windows authentification. I am using a radio button in a customize
dialog.
If not Windows auth. is selected, the user can enter a username
and
a
password.
How should I set the SqlDatabase component to do it? I mean, if
Windows
auth. the User=SQLUser should not be used.
Snippet:
Component Id=CreateDB DiskId=1
Guid=----
sql:SqlDatabase Id=MyDb Server=[SQLSERVER]
Database=[SQLDBNAME] CreateOnInstall=yes
ConfirmOverwrite=yes
DropOnReinstall=no DropOnUninstall=no User=SQLUser
sql:SqlScript Id=CreateTablesSqlScript
ContinueOnError=no
ExecuteOnInstall=yes ExecuteOnReinstall=no Sequence=002
BinaryKey=CreateTablesBin User=SQLUser /
/sql:SqlDatabase
/Component
Feature Id=SqlDb Title=Create Database
Description=Installing
database. Please ensure that the SQL Server is running on the
target
server. AllowAdvertise=yes TypicalDefault=install
Display=expand
Level=1
ComponentRef Id=CreateDB /
/Feature
Thanks in advance,
Peter
--
View this message in context:
http://www.nabble.com/Creating-SqlDatabase-with-without-Windows-Authentification-tf3394305.html#a9449474
Sent from the wix-users mailing list archive at Nabble.com.
-
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
Re: [WiX-users] C# .dll
Phil: My PM and all the senior engineers who interviewed me, hired me on the basis of my C# skills. I was the one who started packaging my company's deployment packages using WIX - all (and I mean ALL) the folks in my company still use XCopy and batch files. I raised this issue (calling C# .dlls from WIX) because it is something that seems eminent and invigorating. I like learning newer technologies and I ended up learning WIX myself, not because my superiors 'forced it upon me' (they are least interested in such issues anyway :)) or because it was a core requirement. I just like my packages to be deployed in an 'orderly' manner and what better than WIX to do such things!! That being said, I am not complaining that WIX doesn't support .NET .dlls - I am merely raising an issue that will be raised by others as more people start adopting WIX. I have coded in ANSI C (in college, not exaggerating) for a semester, because I was forced to. Personally I felt it was horrible, but then I also believed that I couldn't be a programmer unless I started from the ground up. Of course I could learn C++, and who knows someday I will, but at this point in time I see myself as a hardcore C# enthusiast (of course a newbie as far as my programming skills go!). Anyway, I just wanted to find out the reasons why this can't happen (at least for now), and I think Richard made some good points. I completely overlooked the issue of 'undoing' a custom action, but I was thinking more on the lines of 'if it is doable in C++, it must be a breeze to redo it in C#'. Thanks for all the replies (the issue surely raised a few eyebrows.. hehe). On 3/19/07, Levi Wilson [EMAIL PROTECTED] wrote: And C++ will NEVER die. On 3/19/07, Danish Waheed [EMAIL PROTECTED] wrote: I think one of the reasons why Windows Installer does not have lots of fancy actions is because they are not generally related to installation and hence the support for Custom Actions. You cannot include all the possible actions as there are so many types of software and so many configuration/changes required, that it is better to leave them to the developer to write custom actions for their needs. Now for .NET Custom Actions, I think it will be cool to have support for that, but at the same time, I think vbScript and Jscript are very easy to use and learn compared to C++, in case someone does not want to spend time on C++. Besides, if you know Object Oriented Programming, like C#, learning C++ is not that difficult especially if it is just for Custom Actions. It may take a bit extra time for you to write a DLL in the beginning, but once it is done, adding more functions to it is very easy. There are so many tutorials out there that you can learn from. I am not a C++ programmer by any means and most of my coding has been in C# and Java so I understand where Dhaval is coming from. But I had to write custom actions in C++ as it was not an option at several places I worked at. So if you like being a setup developer for Windows, learning C++ will definitely help you in the longer run. Now one must avoid using Custom Actions unless it is really required and is something that Windows Installer cannot do. But can you avoid it or not depends on the software you are writing setup for, I have seen a lot of products with more than 50 Custom Actions and all of them doing something that Windows Installer cannot do. Once you start working on complex software setup, things get messy very easily and the best way to handle those Custom Actions is to write Custom Action dll in C++. Just my two cents. Thanks Danish Waheed -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of [EMAIL PROTECTED] Sent: Monday, March 19, 2007 11:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] C# .dll One other concern in making custom actions in C# (or anything else) is that as Rob regularly observes, custom actions are very difficult to get right - especially when considering installation failure (rollback) and appropriate uninstall operation. Speaking for myself, I try to avoid them whenever possible. In fact I think the only custom actions I currently have in any of the installations I have generated relate to the verification at installation time of a customer entered license key. Many people seem to look at custom actions as a way to do things that aren't supported by Microsoft Installer itself. While true, it is also often true that there is a reason why Microsoft Installer doesn't currently contain built-in support for that specific action. Regards, Richard --- Original message follows --- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dhaval Patel Sent: Monday, March 19, 2007 10:45 AM To: Rob Mensching Cc: Joe Kaplan; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] C# .dll Folks like me, meaning people who have minuscule
Re: [WiX-users] C# .dll
Thanks for those words of wisdom :) On 3/19/07, Wilson, Phil [EMAIL PROTECTED] wrote: I understand, and it wasn't meant as a criticism. It just seems to be a common story that some developer on the team with some set of skills will be pressed into service as the setup guy with a different skill set requirement. Occasionally people are surprised by that difference. Setup is just copying files, right??? How hard can it be? But you volunteered, so good, and welcome to the setup club. You'll probably run into other areas where setups require a different way of thinking. (One model is that you should write setups as if you're updating the company's payroll database with no backup to correct it if you fnd out you did it wrong when it's all over.) Also, C++ will always be useful, so if you're just starting out I'd certainly recommend you learning it (include managed C++ too) because you'll stand out from all those guys who only have C#. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dhaval Patel Sent: Monday, March 19, 2007 4:20 PM To: Levi Wilson Cc: Danish Waheed; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] C# .dll Phil: My PM and all the senior engineers who interviewed me, hired me on the basis of my C# skills. I was the one who started packaging my company's deployment packages using WIX - all (and I mean ALL) the folks in my company still use XCopy and batch files. I raised this issue (calling C# .dlls from WIX) because it is something that seems eminent and invigorating. I like learning newer technologies and I ended up learning WIX myself, not because my superiors 'forced it upon me' (they are least interested in such issues anyway :)) or because it was a core requirement. I just like my packages to be deployed in an 'orderly' manner and what better than WIX to do such things!! That being said, I am not complaining that WIX doesn't support .NET .dlls - I am merely raising an issue that will be raised by others as more people start adopting WIX. I have coded in ANSI C (in college, not exaggerating) for a semester, because I was forced to. Personally I felt it was horrible, but then I also believed that I couldn't be a programmer unless I started from the ground up. Of course I could learn C++, and who knows someday I will, but at this point in time I see myself as a hardcore C# enthusiast (of course a newbie as far as my programming skills go!). Anyway, I just wanted to find out the reasons why this can't happen (at least for now), and I think Richard made some good points. I completely overlooked the issue of 'undoing' a custom action, but I was thinking more on the lines of 'if it is doable in C++, it must be a breeze to redo it in C#'. Thanks for all the replies (the issue surely raised a few eyebrows.. hehe). On 3/19/07, Levi Wilson [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: And C++ will NEVER die. On 3/19/07, Danish Waheed [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I think one of the reasons why Windows Installer does not have lots of fancy actions is because they are not generally related to installation and hence the support for Custom Actions. You cannot include all the possible actions as there are so many types of software and so many configuration/changes required, that it is better to leave them to the developer to write custom actions for their needs. Now for .NET Custom Actions, I think it will be cool to have support for that, but at the same time, I think vbScript and Jscript are very easy to use and learn compared to C++, in case someone does not want to spend time on C++. Besides, if you know Object Oriented Programming, like C#, learning C++ is not that difficult especially if it is just for Custom Actions. It may take a bit extra time for you to write a DLL in the beginning, but once it is done, adding more functions to it is very easy. There are so many tutorials out there that you can learn from. I am not a C++ programmer by any means and most of my coding has been in C# and Java so I understand where Dhaval is coming from. But I had to write custom actions in C++ as it was not an option at several places I worked at. So if you like being a setup developer for Windows, learning C++ will definitely help you in the longer run. Now one must avoid using Custom Actions unless it is really required and is something that Windows Installer cannot do. But can you avoid it or not depends on the software you are writing setup for, I have seen a lot of products with more than 50 Custom Actions and all
[WiX-users] C# .dll
Will WIX 3.0 be adding the capability to call C# .dll files? If not, WHY? :) - 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] C# .dll
I guess, I see your point, Rob. But making this functionality available would open all kinds of doors for folks like me - I get to govern 'what, how, and when' my clients install currently; our company is a 90% MS shop, and most of our server deployments have .NET installed just for that reason alone. Of course, this may mean more issues for you :) On 3/16/07, Rob Mensching [EMAIL PROTECTED] wrote: More importantly, the Windows Installer doesn't support it today. There are actually neat problems you can introduce by loading the .NET Framework into the Windows Installer process. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Levi Wilson *Sent:* Friday, March 16, 2007 10:40 AM *To:* Dhaval Patel *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] C# .dll I don't know for certain, but my guess would be that there's no guarantee that the .NET Framework has been installed on the client. On 3/16/07, *Dhaval Patel *[EMAIL PROTECTED] wrote: Will WIX 3.0 be adding the capability to call C# .dll files? If not, WHY? :) - 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 - 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] Creating SqlDatabase with/without Windows Authentification
I'd be interested in seeing your solution, Peter. Can you post your solution on the Wix-users list for future reference? I feel this shouldn't be hard, but if you already have it, then why reinvent the wheel! Thanks in advance. On 3/13/07, pobox77 [EMAIL PROTECTED] wrote: Thanks Dana, I've just found the same solution about an hour ago. Just a note for people having similar problem: The property used by the radio button and in the condition must be a global property (e.g. the name of it should only have capitals) otherwise it doesn't work. Peter Dana Gutride wrote: This is not possible within the sql database tag right now. There is a bug/feature request in for this exact functionality, but as far as I can tell, it hasn't been added yet. The only way to do this is to have two sqldatabase tags in separate components and then add conditions for the components based on the radio button's property. Dana On 3/13/07, pobox77 [EMAIL PROTECTED] wrote: Sorry, the snippet was wrong formatted. pobox77 wrote: Hi, I would like to create a SqlDatabase either with Username+Password or with Windows authentification. I am using a radio button in a customize dialog. If not Windows auth. is selected, the user can enter a username and a password. How should I set the SqlDatabase component to do it? I mean, if Windows auth. the User=SQLUser should not be used. Snippet: Component Id=CreateDB DiskId=1 Guid=---- sql:SqlDatabase Id=MyDb Server=[SQLSERVER] Database=[SQLDBNAME] CreateOnInstall=yes ConfirmOverwrite=yes DropOnReinstall=no DropOnUninstall=no User=SQLUser sql:SqlScript Id=CreateTablesSqlScript ContinueOnError=no ExecuteOnInstall=yes ExecuteOnReinstall=no Sequence=002 BinaryKey=CreateTablesBin User=SQLUser / /sql:SqlDatabase /Component Feature Id=SqlDb Title=Create Database Description=Installing database. Please ensure that the SQL Server is running on the target server. AllowAdvertise=yes TypicalDefault=install Display=expand Level=1 ComponentRef Id=CreateDB / /Feature Thanks in advance, Peter -- View this message in context: http://www.nabble.com/Creating-SqlDatabase-with-without-Windows-Authentification-tf3394305.html#a9449474 Sent from the wix-users mailing list archive at Nabble.com. - 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 - 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 -- View this message in context: http://www.nabble.com/Creating-SqlDatabase-with-without-Windows-Authentification-tf3394305.html#a9453722 Sent from the wix-users mailing list archive at Nabble.com. - 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 - 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
[WiX-users] Pre-Processor Variables
I was playing around with WIX and came across some examples on the Net that use pre-processor variables ($ sign) to set properties (at least that what I understood). Can someone throw some light on the exact behavior, syntax, and usage of the $ sign (and/or any other such variables in WIX - these remind me of $,#,etc in ASP.NET)? Some examples would help, too. Thanks in advance. - 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] Prevent Deletion of File
So I assume the components in other MSIs need to have the same GUID? Again, I don't need this functionality right now, but it'd be good to know. Thanks. On 2/14/07, Bob Arnson [EMAIL PROTECTED] wrote: Dhaval Patel wrote: I have an MSI that installs numerous files - some of these may be shared by other components on the same box at a later time. I need to ensure that these specific files are not deleted upon uninstallation of my MSI. An example would help! If the same components are shared among multiple MSIs, MSI only uninstalls them when there are no installed products using them. -- sig://boB http://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
[WiX-users] Prevent Deletion of File
I have an MSI that installs numerous files - some of these may be shared by other components on the same box at a later time. I need to ensure that these specific files are not deleted upon uninstallation of my MSI. An example would help! Thanks for the help, guys! - 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] Windows Forms App
I was able to fix this issue - my windows form reads and writes values to and from the registry... it turned out that the way WIX was creating the registry key was making it unreadable somehow. The weird part was that the form was able to read from a couple of keys (both created by WIX), but unable to read/write from the same key's sub-keys. For anyone else who has the same issue, I have found that setting the Action attribute to Action=createKeyAndRemoveKeyOnUninstall (for a type string registry key) works just fine. I don't know if this is a bug, or I just made a mistake configuring the keys. This is what I had initially when the form was crashing because WIX (or I) made the key unreadable -- this key had sub-keys and another registry key defined with the same signature: Registry Root='HKLM' Key='SOFTWARE\MyCompany\App1' Action='write' This is what fixed it (I had to set the Action to createKeyAndRemoveKeyOnUninstall for all the sub-keys and parent keys): Registry Root=HKLM Key=SOFTWARE\MyCompany\App1 Action=createKeyAndRemoveKeyOnUninstall Also, I used tallow to create the WIX fragment and one thing I noticed was that tallow doesn't decorate the Registry elements with the Action attribute, which also didn't seem to work in my case. Thanks! On 2/13/07, Johan Appelgren [EMAIL PROTECTED] wrote: On 2/14/07, Dhaval Patel [EMAIL PROTECTED] wrote: I don't know if this issue is WIX related, or something completely random. I had developed an app that was deployed using Xcopy via a batch file. Recently my PM decided to port it to WIX because of my newly gained WIX powers. Anyway, this app has a bunch of .dll files and a Windows Forms app that references a couple of these .dll files. There are no problems with the installer and everything installs just fine. But as soon as I try and launch the .exe file (the Windows Form), it crashes. The Windows Forms app has no problems, whatsoever, if deployed via Xcopy. I am not sure if how I have laid out my Components (the Name attribute for backward compatiblity, etc.) in the WIX file is screwing up somehow... This is a .NET 2.0 app being deployed on W2K3 server. I haven't tried installing it on XP. Thanks in advance, folks! How does the application crash? The exception should give you some clues to track down the problem. Although since it works when you copy the files a possible cause could be that one or more of the files are missing or were installed in the wrong location. /Johan - 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 - 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
[WiX-users] Windows Forms App
I don't know if this issue is WIX related, or something completely random. I had developed an app that was deployed using Xcopy via a batch file. Recently my PM decided to port it to WIX because of my newly gained WIX powers. Anyway, this app has a bunch of .dll files and a Windows Forms app that references a couple of these .dll files. There are no problems with the installer and everything installs just fine. But as soon as I try and launch the .exe file (the Windows Form), it crashes. The Windows Forms app has no problems, whatsoever, if deployed via Xcopy. I am not sure if how I have laid out my Components (the Name attribute for backward compatiblity, etc.) in the WIX file is screwing up somehow... This is a .NET 2.0 app being deployed on W2K3 server. I haven't tried installing it on XP. Thanks in advance, folks! - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CustomAction
Thanks so much for the replies, guys! Great help!! By the way, Levi was correct to assume that I want to run the batch file only on uninstall :). Thanks again, both of you! On 2/5/07, Levi Wilson [EMAIL PROTECTED] wrote: The condition: Installed AND NOT REINSTALL Would only execute on an Uninstall. On 2/5/07, fiordean dacian [EMAIL PROTECTED] wrote: Hi, I think Dhaval only wants its UndoActionA executed on removal, and not during the installation (otherwise it will immediately undo the effects of ActionA, right?) Recap: ActionA on install (and removal eventually) UndoActionA on uninstall only There is indeed a restriction on REMOVE property, your custom action needs to be scheduled after InstallValidate: http://msdn2.microsoft.com/en-us/library/aa368013.aspx Dacian - Original Message From: Levi Wilson [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Cc: WiX-users@lists.sourceforge.net Sent: Monday, February 5, 2007 3:40:39 PM Subject: Re: [WiX-users] CustomAction If you did it that way I think that ActionA would run both on Install AND Uninstall. To get ActionA to run Only in install, you would condition it like this: Custom Action=ActionA After=InstallFilesNOT Installed/Custom !-- Only run on Install -- Custom Action=UndoActionA After=RemoveFilesInstalled AND NOT REINSTALL/Custom !-- Only run on uninstallation -- Please correct me if I'm wrong. I think that I read somewhere in one of the WiX (or MSI?) newsgroups that you shouldn't use the REMOVE property to condition something for uninstallation. Hope this helps. On 2/5/07, fiordean dacian [EMAIL PROTECTED] wrote: Hi Dhaval, I'm new here and I have not much experience with WiX, but if my understanding is correct, here it goes: ... CustomAction Id=ActionA .../ CustomAction Id=UndoActionA .../ InstallExecuteSequence Custom Action=ActionA After=InstallFiles/ Custom Action=UndoActionA After=ActionAREMOVE=ALL/Custom /InstallExecuteSequence This will makes sure your 'UndoActionA' custom action is executed only during removal. Hope this helps, Dacian - Original Message From: Dhaval Patel [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Sent: Friday, February 2, 2007 7:30:06 PM Subject: [WiX-users] CustomAction I have been trying to find a post that would sum up how to run a CustomAction (to run a batch file) at the end of an installation, and in the same MSI, another CustomAction that would run the corresponding undo action from another batch file. So the flow would be like: Step 1) Install files Step 2) Run batch file for action A Step 3) Run batch file to undo action A Step 4) Uninstall files I have tried hard to find examples and it seems that running a batch file after install is straightforward, but what about the uninstallation phase? Specifically, what's the Event that I should tie the batch file to so that it runs only during uninstallation? Thanks in advance, folks. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel siteshttp://farechase.yahoo.com/promo-generic-14795097;_ylc=X3oDMTFtNW45amVpBF9TAzk3NDA3NTg5BF9zAzI3MTk0ODEEcG9zAzEEc2VjA21haWx0YWdsaW5lBHNsawNxMS0wNw--%0Ato find flight and hotel bargains. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Need a quick answer? Get one in minutes from people who know. Ask your question on Yahoo! Answers http://answers.yahoo.com/;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMzOTY1NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx . - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly
Re: [WiX-users] package ASP.NET application
Use tallow.exe, I believe. It should be able to create a fragment for all those files that you can use within WIX (I have never used it for files, but it worked like a charm for a huge registry entry I had to do on one of my projects recently). Again, just follow the tutorial for using tallow.exe, Oleg. Correct me if I am wrong on this one, fellow WIX users !?!? On 1/19/07, Ogurok, Oleg [EMAIL PROTECTED] wrote: Dhaval, Thanks for your help. My ASP.NET app has 150+ ASPX files. Is there a way to use wildcards in WiX to include all files as one line (*.aspx) or do I have to list all files separately as File elements? -Oleg. -- *From:* Dhaval Patel [mailto:[EMAIL PROTECTED] *Sent:* Friday, January 19, 2007 12:21 AM *To:* Ogurok, Oleg *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] package ASP.NET application See the example here: http://www.tramontana.co.hu/wix/lesson6.php#6.3 Basically, the Directory element would contain all your *.aspx, *.js, etc files. One thing the example doesn't mention is nested directories (example, you may have an App_Code, App_Themes, etc) directories - if you are using Visual Studio, Intellisense will help you figure out that you can have nested Directory elements within the main Directory element. Once you reach the root of that structure, just instantiate a Component element and fill out the remaining stuff as per your needs. Then from your WebVirtualDir, reference the main Directory ID, and from the WebSite element, reference this WebVirtualDir ID. Directory Id=WebStuff Name=WA LongName=Web Stuff !-- THIS IS A SUB DIRECTORY -- Directory Id=bin Name=bin Component Id=BinDir DiskId=1 Guid=YOURGUID-3114-4945-930D-67F73D4B65B7 File Id=ACCOMPILED Name='ACC' LongName ='App_Code.compiled' Source='Web\bin\App_Code.compiled' Vital='yes' / File Id='ACCDLL' Name='ACD' LongName='App_Code.dll' Source='Web\bin\App_Code.dll' Vital='yes' / /Component /Directory !-- THIS IS ANOTHER SUB DIRECTORY -- Directory Id='Images' Name='Images' Component Id='ImagesDir' DiskId='1' Guid='YOURGUID-ABD5-4146-A126-C23A7BD74DD0' File Id='CALGIF' Name='CAL' LongName='Calendar.GIF' Source='Web\Images\Calendar.GIF' Vital='yes' / /Component /Directory !-- HERE ARE YOUR ASPX CONFIG FILES -- Component Id=Web DiskId=1 Guid=YOURGUID-710E-4c6d-9D4C-3C4D97F67685 File Id=TestASPX Name=' TT.aspx' LongName ='Test.aspx' Source='Web\Test.aspx' Vital='yes' / File Id=WebCONFIG Name='WC.aspx' LongName =' web.config' Source='Web\web.config' Vital='yes' / /Component /Directory Component Id='WebVirtualDir' Guid='YOURGUID-D174-40d7-BC0B-73FD896E5036' WebVirtualDir Id='SomeID' Alias='WebStuff' Directory='WebStuff' WebSite='DefaultWebSite' WebApplication Id='WebApplication' Name='WebStuff' / /WebVirtualDir /Component WebSite Id='DefaultWebSite' Description='Shows Web Stuff.' WebAddress Id='AllUnassigned' Port='80'/ /WebSite Happy WIX'in :) On 1/18/07, *Ogurok, Oleg *[EMAIL PROTECTED] wrote: Hi there, I am migrating from the bult-in VS2005 web deployment project to WiX. Could someone please provide a simple example of creating an MSI package which will create a virtual directory in IIS and install all output files ( e.g. *.aspx, *.js) from a Visual Studio 2005 Web Deployment Project? I can't seem to figure out how to specify from where to copy the files. Thanks, -Oleg. - 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 - 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] package ASP.NET application
See the example here: http://www.tramontana.co.hu/wix/lesson6.php#6.3 Basically, the Directory element would contain all your *.aspx, *.js, etc files. One thing the example doesn't mention is nested directories (example, you may have an App_Code, App_Themes, etc) directories - if you are using Visual Studio, Intellisense will help you figure out that you can have nested Directory elements within the main Directory element. Once you reach the root of that structure, just instantiate a Component element and fill out the remaining stuff as per your needs. Then from your WebVirtualDir, reference the main Directory ID, and from the WebSite element, reference this WebVirtualDir ID. Directory Id=WebStuff Name=WA LongName=Web Stuff !-- THIS IS A SUB DIRECTORY -- Directory Id=bin Name=bin Component Id=BinDir DiskId=1 Guid=YOURGUID-3114-4945-930D-67F73D4B65B7 File Id=ACCOMPILED Name='ACC' LongName ='App_Code.compiled' Source='Web\bin\App_Code.compiled' Vital='yes' / File Id='ACCDLL' Name='ACD' LongName='App_Code.dll' Source='Web\bin\App_Code.dll' Vital='yes' / /Component /Directory !-- THIS IS ANOTHER SUB DIRECTORY -- Directory Id='Images' Name='Images' Component Id='ImagesDir' DiskId='1' Guid='YOURGUID-ABD5-4146-A126-C23A7BD74DD0' File Id='CALGIF' Name='CAL' LongName='Calendar.GIF' Source='Web\Images\Calendar.GIF' Vital='yes' / /Component /Directory !-- HERE ARE YOUR ASPX CONFIG FILES -- Component Id=Web DiskId=1 Guid=YOURGUID-710E-4c6d-9D4C-3C4D97F67685 File Id=TestASPX Name='TT.aspx' LongName ='Test.aspx' Source='Web\Test.aspx' Vital='yes' / File Id=WebCONFIG Name='WC.aspx' LongName =' web.config' Source='Web\web.config' Vital='yes' / /Component /Directory Component Id='WebVirtualDir' Guid='YOURGUID-D174-40d7-BC0B-73FD896E5036' WebVirtualDir Id='SomeID' Alias='WebStuff' Directory='WebStuff' WebSite='DefaultWebSite' WebApplication Id='WebApplication' Name='WebStuff' / /WebVirtualDir /Component WebSite Id='DefaultWebSite' Description='Shows Web Stuff.' WebAddress Id='AllUnassigned' Port='80'/ /WebSite Happy WIX'in :) On 1/18/07, Ogurok, Oleg [EMAIL PROTECTED] wrote: Hi there, I am migrating from the bult-in VS2005 web deployment project to WiX. Could someone please provide a simple example of creating an MSI package which will create a virtual directory in IIS and install all output files ( e.g. *.aspx, *.js) from a Visual Studio 2005 Web Deployment Project? I can't seem to figure out how to specify from where to copy the files. Thanks, -Oleg. - 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 - 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] SQL Instance
I figured out the first issue - as mentioned before, I ask for the user's credentials upon uninstallation too. The 2nd issue is still not resolved. I have tried various combinations of passing credentials, Rob, and none of them seem to work. The only action that I am able to perform successfully is the one upon installation - WIX will create and execute scripts if I pass in the credentials to a named instance of SQL Server. I have 4 properties defined: SQLUSERNAME, SQLPASSWORD, SQLSERVER, SQLINSTANCE. Just to be precise, I have tried the following: 1) SQL Server Local [unnamed] Instance (Installation WORKS if I pass all 4 properties, uninstallation FAILS). The following all fail a) UserName, Password, Blank SQLSERVER, Blank SQLINSTANCE b) UserName, Password, Machine Name as SQLSERVER, Blank SQLINSTANCE c) Blank UserName, Blank Password, Machine Name as SQLSERVER, Blank SQLINSTANCE d) Everything Blank 2) SQL Server named Instance - Everything works just fine (install as well as uninstall), assuming the user passes in the correct credentials. I would like to find out other folks' experiences on this or a possible workaround. Thanks again! On 1/14/07, Rob Mensching [EMAIL PROTECTED] wrote: 1. The Windows Installer does not persist/cache Properties for you. You need to do it yourself. There is much discussion of methods to do just that in the mailing list archive. 2. I leave the SqlDatabase/@Instance blank and that connects to the default instance in my scripts. Also, SQL seems to recognize (local) as the name of the local SQL machine. I've never tried localhost or .. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Dhaval Patel *Sent:* Sunday, January 14, 2007 5:07 PM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] SQL Instance I am very satisfied with what I have achieved with WIX over the past few weeks. Nevertheless, I have been running into road blocks while trying to execute SQL Server related tasks. 1) Upon uninstalling the product, WIX is ALWAYS unable to drop the database (and unable to execute the uninstallation script) for some reason. Installing is never a problem - but because of this anomaly, I have to set ContinueOnError attribute to yes. Quite frankly I would like to pinpoint the reason for this behavior. In the attached JPG file, I have a dialog that pops up during installation which collects user's SQL credentials which are then passed on to WIX as properties. I was under the impression that WIX caches this information (correct me if I am wrong here, folks) and will use it during uninstallation to establish a connection with SQL Server during the uninstallation phase. Anyway, I thought that this was not a feasible solution - what if the admin has changed the password: so now I present the same dialog if the user decides to remove the product (I still have to test this functionality). I would be more than happy if someone can throw some light on my assumptions and why WIX is unable to uninstall the database. 2) When my release will be deployed, it may be installed on a machine that either has a named instance of SQL Server or a default instance of SQL Server. The 4 textboxes I present to the user work just fine if the machine has a named instance of SQL Server installed (Here the user MUST type the machine name, because localhost or . don't seem to work which is not a big deal). However, the database creation and SqlScript installation phase fails if the machine has a default instance of SQL Server - for this reason I must fall back to providing the end user with batch files for the install/uninstall SQL scripts, which is quite inelegant. I have tried by passing in the machine name for SQLSERVER, and leaving the SQLINSTANCE box blank (I don't know what to pass in for the default instance of SQL Server !?!?). Again, I would appreciate if someone can provide a solution to this dilemma. Here are the Sql scripts: !-- SQL Components -- Component Id ='SqlDatabaseInstall' DiskId='1' Guid='7FE20B5C-FF37-4618-8D6F-3D04BD66E845' SqlDatabase Id='SqlInstall' ContinueOnError='yes' CreateOnInstall='no' Database='master' CreateOnReinstall='no' DropOnInstall='no' Instance='[SQLINSTANCE]' DropOnReinstall='no' User='MySqlUser' Server='[SQLSERVER]' DropOnUninstall='no' SqlScript Id='InstallScript' BinaryKey='CreateSql' ExecuteOnInstall='yes' User='MySqlUser' ContinueOnError='yes' ExecuteOnReinstall='no' ExecuteOnReInstall='no' ExecuteOnUninstall='no' / /SqlDatabase /Component Component Id ='SqlDatabaseUninstall' DiskId='1' Guid='25CF21B9-DC63-4ac1-9E16-D3B73F5302DF' SqlDatabase Id='SqlUninstall' ContinueOnError='yes' CreateOnInstall='no' Database='master' CreateOnReinstall='no' CreateOnUninstall='no' DropOnInstall='no' Instance='[SQLINSTANCE]' DropOnReinstall='no' User='MySqlUser' Server='[SQLSERVER]' DropOnUninstall='no' SqlScript Id='UninstallScript
[WiX-users] SQL Instance
I am very satisfied with what I have achieved with WIX over the past few weeks. Nevertheless, I have been running into road blocks while trying to execute SQL Server related tasks. 1) Upon uninstalling the product, WIX is ALWAYS unable to drop the database (and unable to execute the uninstallation script) for some reason. Installing is never a problem - but because of this anomaly, I have to set ContinueOnError attribute to yes. Quite frankly I would like to pinpoint the reason for this behavior. In the attached JPG file, I have a dialog that pops up during installation which collects user's SQL credentials which are then passed on to WIX as properties. I was under the impression that WIX caches this information (correct me if I am wrong here, folks) and will use it during uninstallation to establish a connection with SQL Server during the uninstallation phase. Anyway, I thought that this was not a feasible solution - what if the admin has changed the password: so now I present the same dialog if the user decides to remove the product (I still have to test this functionality). I would be more than happy if someone can throw some light on my assumptions and why WIX is unable to uninstall the database. 2) When my release will be deployed, it may be installed on a machine that either has a named instance of SQL Server or a default instance of SQL Server. The 4 textboxes I present to the user work just fine if the machine has a named instance of SQL Server installed (Here the user MUST type the machine name, because localhost or . don't seem to work which is not a big deal). However, the database creation and SqlScript installation phase fails if the machine has a default instance of SQL Server - for this reason I must fall back to providing the end user with batch files for the install/uninstall SQL scripts, which is quite inelegant. I have tried by passing in the machine name for SQLSERVER, and leaving the SQLINSTANCE box blank (I don't know what to pass in for the default instance of SQL Server !?!?). Again, I would appreciate if someone can provide a solution to this dilemma. Here are the Sql scripts: !-- SQL Components -- Component Id ='SqlDatabaseInstall' DiskId='1' Guid='7FE20B5C-FF37-4618-8D6F-3D04BD66E845' SqlDatabase Id='SqlInstall' ContinueOnError='yes' CreateOnInstall='no' Database='master' CreateOnReinstall='no' DropOnInstall='no' Instance='[SQLINSTANCE]' DropOnReinstall='no' User='MySqlUser' Server='[SQLSERVER]' DropOnUninstall='no' SqlScript Id='InstallScript' BinaryKey='CreateSql' ExecuteOnInstall='yes' User='MySqlUser' ContinueOnError='yes' ExecuteOnReinstall='no' ExecuteOnReInstall='no' ExecuteOnUninstall='no' / /SqlDatabase /Component Component Id ='SqlDatabaseUninstall' DiskId='1' Guid='25CF21B9-DC63-4ac1-9E16-D3B73F5302DF' SqlDatabase Id='SqlUninstall' ContinueOnError='yes' CreateOnInstall='no' Database='master' CreateOnReinstall='no' CreateOnUninstall='no' DropOnInstall='no' Instance='[SQLINSTANCE]' DropOnReinstall='no' User='MySqlUser' Server='[SQLSERVER]' DropOnUninstall='no' SqlScript Id='UninstallScript' BinaryKey='RemoveSql' ExecuteOnInstall='no' User='MySqlUser' ExecuteOnReInstall='no' ContinueOnError='yes' ExecuteOnReinstall='no' ExecuteOnUninstall='yes' / /SqlDatabase /Component !-- Path to Sql scripts -- Binary Id='CreateSql' SourceFile='Database.sql' / Binary Id='RemoveSql' SourceFile='Drop.sql'/ Thanks in advance! attachment: SQL.JPG - 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
[WiX-users] SQL Script
I am a WIX newbie and I think I have been able to grasp most of the functionality via trial and error over the last week or so. Nevertheless, making this SQL script execute has been driving me nuts. I am hoping one of you experienced folks will be able to help me out. I have attached an image of the error I receive upon installation and here is the exact text of the error: Failed to execute SQL string, error detail: Could not find stored procedure 'C'., SQL Key: Script SQL string: CThe very first line I had in my SQL script is: CREATE TABLE [dbo].[DataMerge]Before that I had the line: USE TABLE [MergeFiles] and I received this error - Failed to execute SQL string, error detail: Could not find stored procedure 'U'., SQL Key: Script SQL string: UIt seems that no matter what I put in the my sql script, it errors out on the first character. Here is my WIX code:Component Id ='SqlDatabase' DiskId='1' Guid='7FE20B5C-FF37-4618-8D6F-3D04BD66E845'SqlDatabase Id='Sql' ContinueOnError='no' CreateOnInstall='yes' Database='MergeNist' CreateOnReinstall='no' DropOnUninstall='yes' Instance='[SQLINSTANCE]' DropOnReinstall='no' User='MySqlUser' Server='[SQLSERVER]' SqlScript Id='Script' BinaryKey='CreateSql' ExecuteOnInstall='yes' / /SqlDatabase/Component!-- Path to Sql script --Binary Id='CreateSql' SourceFile='Database.sql' /Let me know if I am missing anything. It'd be thrilling for my entire team if I get this to work. I am able to create a virtual directory, a Windows user, install a service, and various assmeblies to the GAC. This is the only thing that's not working. Thanks in advance! _ All-in-one security and maintenance for your PC. Get a free 90-day trial! http://www.windowsonecare.com/purchase/trial.aspx?sc_cid=wl_wlmailattachment: error.jpg - 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
