Re: [WiX-users] Create files on install
I'm new too, so I'm gonna be verbose. Here's the steps I took using VS2008. Create a new WiX installer project. Add a new project to the solution - C#/VB/C++ custom action project. Add the code to the custom action project to generate the file you want. Compile the custom action project. Reference the custom action from within your WiX markup. Binary Id=myAction SourceFile=..\CustomAction1\bin\Debug\CustomAction1.CA.dll / Use the CustomAction element and specify the call. CustomAction Id=DoMyAction BinaryKey=myAction DllEntry=CustomAction1 Execute=deferred Return=check Impersonate=no/ Ensure the call is only run on install. InstallExecuteSequence Custom After=InstallFiles Action=DoMyActionNOT Installed AND NOT PATCH/Custom /InstallExecuteSequence -Original Message- From: AxiomaticImpact [mailto:ke...@legendary-immersion.com] Sent: 11 November 2011 19:15 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Create files on install Yeah, I want to generate a file upon installation. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Create-files-o n-install-tp6986046p6986480.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Create files on install
Do you mean create as in generate a file (you could use a custom action to do that) or create as in here is my file, put it in that directory which is much simpler and just requires a reference to a file. To dump, add something like this to a directory, but I think it's all in the .chm so you probably mean custom action. Directory ... Component Id='CMP_Default_MDB' Guid='*' File Id='FILE_Default_MDB' Source='Default.mdb' KeyPath=yes Vital=yes ReadOnly=no Hidden=no/ /Component /Directory If it's a custom action you want then I'll see if I can distil you an example. -Original Message- From: AxiomaticImpact [mailto:ke...@legendary-immersion.com] Sent: 11 November 2011 17:02 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Create files on install I'm new to WiX, and I can't seem to find it in the documentation. I'd like to create a file during installation. What's the best way to do this? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Create-files-o n-install-tp6986046p6986046.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VB6 Component Questions - JSBtnBar.ocx
Right, finally got round to implementing what you mentioned, Thank-You for your response, all is pretty much well, though the application is not loading fully, the COM components appear to be reasonably happy with their new home. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 08 October 2011 17:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VB6 Component Questions - JSBtnBar.ocx 0. heat is not perfect. Sometimes (particularly for complex COM goo like old VB requires) you have to fix it up yourself. 1. I take the heat output and clean it so it doesn't look so messy. Then I include that cleaned up file in my setup like I'd include any file I wrote from scratch. 2. heat did not correctly associate the TypeLib with the File it needs. Try nesting the TypeLib element under the File it belongs to. 3. It looks like heat got confused and tried to put a File Property reference in there instead of a Directory reference. Change those values to point to the correct Directory/@Id. 4. Personally, when getting that deep into COM goo, I spend a little time on MSDN refreshing my memory of all the registration. Then I go make sure all the registration is correct. COM can get complex quickly, but if you keep it simple the Class, ProgId, TypeLib and Interface elements make it look really pretty (better than tons of RegistryX elements smile/). On Mon, Oct 3, 2011 at 2:13 AM, David Birch (XStream Software) dav...@vale2000.com wrote: Hi all. I have one very old installer file and 2 patches created with vb6 and InstallShield. My task is to form a single, shiny new installer, without using any of the original source code (which is AWOL). I've started with a fresh XP virtual machine, using DefenseWall (a host intrusion protection system) I have identified the files that the original installer installed. A lot of it was put into the SystemFolder. I've copied it all into a subfolder in my project named SystemFolder, which itself is a child of assets. Then I've gone ahead and run `heat dir assets\SystemFolder -gg -sfrag -template fragment -svb6 -out vb6file.wxs`. I have tried copying and pasting all the components from vb6file.wxs between Directory Id=SystemFolder /Directoryof an existing (an up until that point, functional project) but am receiving a few errors, that I've been unable to troubleshoot. Firstly, and perhaps most importantly, what is the correct way to include the output file? Second, the errors begin with ... The typelib element is non-advertised and therefor require a parent File element ... which appears to originate with a component by the name of JSBtnBar.ocx. I also have 3 lots of ... The TypeLib/@HelpDirectory attribute's value, '!filBFDE46EC343B0E499B5B2D6EA1A0CC52', is not a legal identifier. Identifiers may contain ASCII characters A-Z, a-z, digits, underscores (_), or periods (.). Every identifier must begin with either a letter or an underscore. ... with various differing value's. Also, throughout the file, there are many '!fil...' RegistryValue/@Value 's that aren't mentioned, that look a little unwelcoming to my untrained eye. Please cast your expert eyes over this and point me in the right direction (help!). Kind regards, David Birch -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA#174; Conference 2012 Save $700 by Nov 18 Register now#33; http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] VB6 Component Questions - JSBtnBar.ocx
Hi all. I have one very old installer file and 2 patches created with vb6 and InstallShield. My task is to form a single, shiny new installer, without using any of the original source code (which is AWOL). I've started with a fresh XP virtual machine, using DefenseWall (a host intrusion protection system) I have identified the files that the original installer installed. A lot of it was put into the SystemFolder. I've copied it all into a subfolder in my project named SystemFolder, which itself is a child of assets. Then I've gone ahead and run `heat dir assets\SystemFolder -gg -sfrag -template fragment -svb6 -out vb6file.wxs`. I have tried copying and pasting all the components from vb6file.wxs between Directory Id=SystemFolder /Directoryof an existing (an up until that point, functional project) but am receiving a few errors, that I've been unable to troubleshoot. Firstly, and perhaps most importantly, what is the correct way to include the output file? Second, the errors begin with ... The typelib element is non-advertised and therefor require a parent File element ... which appears to originate with a component by the name of JSBtnBar.ocx. I also have 3 lots of ... The TypeLib/@HelpDirectory attribute's value, '!filBFDE46EC343B0E499B5B2D6EA1A0CC52', is not a legal identifier. Identifiers may contain ASCII characters A-Z, a-z, digits, underscores (_), or periods (.). Every identifier must begin with either a letter or an underscore. ... with various differing value's. Also, throughout the file, there are many '!fil...' RegistryValue/@Value 's that aren't mentioned, that look a little unwelcoming to my untrained eye. Please cast your expert eyes over this and point me in the right direction (help!). Kind regards, David Birch -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
