Re: [WiX-users] How to make the custom action run under LocalSystem account?
Yes! After I set ALLUSERS=1, it runs as local system and delete the remote folder. When the system account go through network, it is using the computer account (MachineName$). And my folder is granting permission to MachineName$. Thanks, -Elfe -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-make-the-custom-action-run-under-LocalSystem-account-tp5474012p5481429.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] powershell is faling at Add-PSSnapin Microsoft.SharePoint.PowerShell is failing.
Hi all,
Please try to understand the problem and give some solution.
I am executing the powershell exe as vbscript CA as follows.
Function f1()
MsgBox(exe started)
Set objShell = CreateObject(Wscript.Shell)
vPSscrIpt = powershell.exe -NoExit c:\yyy\aa.ps1
objShell.Run vPSscrIpt
End Function
aa.ps1 content:
Set-ExecutionPolicy RemoteSigned
$ver = $host | select version
if ($ver.Version.Major -gt 1) {$Host.Runspace.ThreadOptions =
ReuseThread}
if ((Get-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction
SilentlyContinue) -eq $null) {
Add-PSSnapin Microsoft.SharePoint.PowerShell
}
#Add-PsSnapin Microsoft.SharePoint.PowerShell
Set-location $home
$sapp = Get-SPEnterpriseSearchServiceApplication –Identity “Search Service
Application”
New-SPEnterpriseSearchCrawlContentSource –SearchApplication $sapp –Name “c1”
–Type Custom –StartAddress protocol://servername –CrawlPriority Normal
–MaxPageEnumerationDepth 1 –MaxSiteEnumerationDepth 1
I decalred the Custom action as follows.
CustomAction Id=f1 BinaryKey=ca VBScriptCall=f1 Execute=deferred
Impersonate=no /
Executing the custom action in installExecute seq as follows.
Custom Action=f1 Before=ProcessComponents1/Custom
But this custom action is not able to registering the sharepoint snapin to
the powershell. Add-PSSnapin Microsoft.SharePoint.PowerShell is failing.
but If I run the vbscript manually it is executing successfully.
Please tell me some suggestion ...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/powershell-is-faling-at-Add-PSSnapin-Microsoft-SharePoint-PowerShell-is-failing-tp5481703p5481703.html
Sent from the wix-users mailing list archive at Nabble.com.
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Comparison of PatchWiz and WiX v3 Patch Build
Hello WiX users, Since I have just read this article http://blogs.msdn.com/b/heaths/archive/2010/08/24/comparison-of-patchwiz-and-wix-v3-patch-build.aspx and I need to create patches I have the question if they is any disadvantage of using the WiX patching System (with Pyro) in comparison to the MS patchwiz one? Especially interesting would be if someone stumbled over any limitations where it can not be used? I have searched the mailing list and read several blog post but could not find any limitations, but I may have missed one. As far as I have read from some blog post and the documentation it is also possible to create a patch if the installation (or even both installation?) was not created with WiX. Are they any drawbacks when doing so? Any hints and answers are welcome. Best regards, Tobias -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Newbie x64 msi question
Hi, I have recently made a 64 bit MSI from a single source and I started out by following http://blogs.msdn.com/b/astebner/archive/2007/08/09/4317654.aspx The trick to make it easy is the -arch command (or setting the processor type in votive), but you also need to do a few other things. I conditionally set the product code and product name ... ?if $(var.Platform)=x64 ? ?define displayName = Product name (x64) ? ?define productCode = A guid ? ?else? ?define displayName = Product name (x86) ? ?define productCode = Another guid ? ?endif? Product Id=$(var.productCode) Language=0 Manufacturer=Company Name=$(var.displayName) Version=8.5.$(var.buildNumber) Codepage=0 UpgradeCode=Yet another guid, these things get everywhere Set the Platform attribute on the Package Element with the built in variable... Platform=$(var.Platform) Then I have a conditional root directory structure as programs should be installed under ProgramFiles64Folder on 64 bit windows... ?if $(var.Platform)=x64 ? Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Directory Id=CompanyProgramsDir Name=SDL /Directory /Directory /Directory ?else ? Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=CompanyProgramsDir Name=SDL /Directory /Directory /Directory ?endif ? The rest of the directory structure is based off a DirectoryRef Id=CompanyProgramsDir so doesn't need to be duplicated. All components in the MSI have * as the component guid, so the conditional root folders above mean that the 32 and 64 bit MSIs will have different component guids. I also have a launch condition that stops the 32 bit MSI being installed on 64 bit windows, which it sounds you don't need. It all seems to be working so far. Dave -Original Message- From: Andres Juarez [mailto:andresj_...@hotmail.com] Sent: 30 August 2010 06:37 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Newbie x64 msi question Hi Bob, In your post http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/. Use the -arch switch and you get smart defaults. So, running candle with teh -arch switch does take care of marking the components at 64 bits, but if using the same Wix source file for the 32 and 64 bits installer with the only difference of the candle -arh switch, the Components GUIDS for the 64 and 32 bits installer are all the same. The two installers cannot install in the same box since the launch conditios are mutually exclusive. Do we still need to have unique GUIDS per components, I am almost sure we do, but just asking. Thanks Andres Date: Sat, 7 Aug 2010 10:56:31 -0400 From: b...@joyofsetup.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Newbie x64 msi question On 8/4/2010 9:57 AM, Pally Sandher wrote: You need to set the Win64 attribute on your components. If it's not set they default to 32-bit components in an x64 package. An easy way to do it is to use a pre-processor variable set to no or yes whether you're building x86 or x64 packages respectively. Then you can simply use something like Win64=$(var.is64bit) in all the components you need to. See http://wix.sourceforge.net/manual-wix3/preprocessor.htm Unnecessary: See http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/. Use the -arch switch and you get smart defaults. -- sig://boB http://joyofsetup.com/ -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users /pre BR style=font-size:4px; a href = http://www.sdl.com;img src=http://www.sdl.com/images/email logo_150dpi-01.png alt=www.sdl.com border=0//a BR font face=arial size=2a href = http://www.sdl.com; style=color:005740; font-weight: boldwww.sdl.com/a/font BR BR font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that
Re: [WiX-users] How to set Manufacturer, Name and Title using Heat
Wix elements are in the wix namespace. Add xmlns:wix=http://schemas.microsoft.com/wix/2006/wi; and then wix: prefixes to your wix elements. -Original Message- From: Satyaprakash J [mailto:sat...@smartek21.com] Sent: 30 August 2010 10:35 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to set Manufacturer, Name and Title using Heat Hi, I am using the following xslt file for the -t option in heat. But it does not set the Manufacturer, Name and Title. Kindly let me know if I am missing something. ?xml version=1.0 encoding=utf-8? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:output omit-xml-declaration=yes indent=yes/ !-- -- xsl:param name=pManufacturer select='IV'/ xsl:param name=pName select='MT'/ xsl:param name=pTitle select='RunwayMT'/ !-- -- xsl:template match=node()|@* xsl:copy xsl:apply-templates select=node()|@*/ /xsl:copy /xsl:template !-- -- xsl:template match=Product/@Manufacturer xsl:attribute name=Manufacturer xsl:value-of select=$pManufacturer/ /xsl:attribute /xsl:template xsl:template match=Product/@Name xsl:attribute name=Name xsl:value-of select=$pName/ /xsl:attribute /xsl:template xsl:template match=Product/Feature/@Title xsl:attribute name=Title xsl:value-of select=$pTitle/ /xsl:attribute /xsl:template /xsl:stylesheet Thanks Satyaprakash J -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, August 26, 2010 4:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to set Manufacturer, Name and Title using Heat You can use heat's -t switch to pass an xslt file that will be applied to the heat output. -Original Message- From: Satyaprakash J [mailto:sat...@smartek21.com] Sent: 26 August 2010 11:43 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to set Manufacturer, Name and Title using Heat Hi, I am using Heat to generate the wxs file. In the generated file we have Manufacturer=PUT-COMPANY-NAME-HERE Name=PUT-PRODUCT-NAME-HERE and Title=PUT-FEATURE-TITLE-HERE. I would like to know how the Manufacturer, Name and Title can be set automatically using heat. Thanks Satyaprakash J -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users /pre BR style=font-size:4px; a href = http://www.sdl.com;img src=http://www.sdl.com/images/email logo_150dpi-01.png alt=www.sdl.com border=0//a BR font face=arial size=2a href = http://www.sdl.com; style=color:005740; font-weight: boldwww.sdl.com/a/font BR BR font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.BR SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.BR Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. /font -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help me for using 'Heat' to generate script (.wxs file) from CAB files directly? Thanks in advance!
It's not supported directly. You'll need to either extract the files first or write a heat extension. -Original Message- From: Xu, Jun [mailto:jun...@ebay.com] Sent: 30 August 2010 11:44 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Help me for using 'Heat' to generate script (.wxs file) from CAB files directly? Thanks in advance! Hi, Can anyone please help me for how to use 'Heat' to generate script (.wxs file) from CAB files directly? Thanks a lot! Best Regards Thank you! Xu, Jun (James) -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users /pre BR style=font-size:4px; a href = http://www.sdl.com;img src=http://www.sdl.com/images/email logo_150dpi-01.png alt=www.sdl.com border=0//a BR font face=arial size=2a href = http://www.sdl.com; style=color:005740; font-weight: boldwww.sdl.com/a/font BR BR font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.BR SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.BR Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. /font -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to change an entry using XmlConfig
Hi all, I am not an expert on Xml, let alone XPath, so I am running into this problem. With my application the following NHibernate.config file is used: ?xml version=1.0 encoding=utf-8 ? hibernate-configuration xmlns=urn:nhibernate-configuration-2.2 session-factory property name=connection.providerNHibernate.Connection.DriverConnectionProvider/property property name=proxyfactory.factory_classNHibernate.ByteCode.LinFu.ProxyFactoryFactory, NHibernate.ByteCode.LinFu/property property name=connection.driver_classNHibernate.Driver.MySqlDataDriver/property property name=connection.connection_stringDatabase=schemaname;Data Source=localhost;User Id=username;Password=password/property property name=dialectNHibernate.Dialect.MySQLDialect /property /session-factory /hibernate-configuration The configuration file is set up to be used from the Visual Studio environment. In my Wix file, I have the following entry: util:XmlConfig Id='MySqlConnectionProperty' File='[INSTALLDIR]\NHibernate.config' Action='create' ElementPath='//hibernate-configuration/session-factory/propert...@name=connection.connection_string\]' Node='value' Value='Database=[MYSQLSCHEMA];Data Source=[MYSQLHOSTNAME];User Id=[MYSQLUSERNAME];Password=[MYSQLPASSWORD]' Sequence='1' On='install'/ With this XmlConfig entry, I try to modify the value of the connection string in the NHibernate.config file according to the settings specified by the user during the installation. The MYSQLxxx parameters are collected in one of the custom dialogs. During the run of the Xml linker, the following error occurs: LGHT0204 : ICE03: Invalid format string; Table: XmlConfig, Column: ElementPath, Key(s): MySqlConnectionProperty Can anyone help me out here? Thanks in advance, Met vriendelijke groeten / With kind regards, Alexander op de Weegh Office: +31(0)226-335023 Mobile: +31(0)6-20138301 IPA Total Productivity Kosterij 4 1721 PN Broek op Langedijk The Netherlands www.ipa-tp.nl of kijkt u eens op www.blean.nl van onze partner B-Lean voor het trainen en implementeren van productiemethodieken en het verbeteren van uw productiviteit. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Preprocessor Extension question
There's a static method called Preprocessor.GetSourceLineNumbers that accepts an XmlNode object. It's used by WiX as Candle is looking through your markup. I'm not sure that you'll be able to use it very easily. If you don't mind my asking, what is it you're trying to achieve? Preprocessor extensions don't have elements that need to be parsed. Do you instead mean to say that you're creating a compiler extension? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Preprocessor-Extension-question-tp5480707p5482348.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Call Custom Action before Install Initialize
So, this is a sort of validation to make sure the database type they've selected is truly installed? In that case, you could call your custom action when the user clicks the Next button on your dialog. You can do that by adding a Publish element inside the button control, setting its Event attribute to DoAction and its Value attribute to the name of your custom action. The custom action can display the error message, maybe using System.Windows.Forms.MessageBox (DTF's session.Message won't work here for displaying an error message since the CA is being called from DoAction). And then return ActionResult.Failure. I guess this all assumes you're using C# for the custom action. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Call-Custom-Action-before-Install-Initialize-tp5478782p5482397.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapping and Burn
Have you guys tried using NSIS http://nsis.sourceforge.net/Main_Page ? On Aug 30, 2010, at 11:36 AM, Christopher Painter wrote: I've looked at dotNetInstaller and while it looks very interesting, there is no way you are going to learn that tool and get a working bootstrapper in 15 minutes. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: dB. dbl...@dblock.org To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Mon, August 30, 2010 8:23:36 AM Subject: Re: [WiX-users] Bootstrapping and Burn http://dotnetinstaller.codeplex.com will get you there in 15 minutes or so. dB. @ dblock.org Moscow|Geneva|Seattle|New York -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Monday, August 30, 2010 4:46 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapping and Burn Hi, I realise Burn has been removed from WiX 3.5, but I'm wondering if the Visual Studio bootstrapper would be a good substitute or if I should wait for a 3.6 snapshot. My main requirement is a single file that users can download to do the installation, since I hate having a setup.exe and MSI file because it's confusing and seems unnecessary. The only component of Burn I've ever used before is setupbld, but I'm wondering - will the output of Burn be a single exe, or will it be like VS where you have to package lots of MSIs and an exe into a zip file for distribution? -- Bruce Cran -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapping and Burn
On Tue, 31 Aug 2010 06:22:56 -0700 (PDT) Christopher Painter chr...@deploymentengineering.com wrote: NSIS? Sorry, I'd rather go to the dentist. You *really* don't like it, do you? :) I don't understand why not; I consider it better than InstallShield for example where you end up having to install InstallScript engine updates before you can even launch the main installer. -- Bruce Cran -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Problem loading solution after upgrading from Wix 3.0 to 3.5.2020
One or more projects in the solution where not loaded correctly. Please see the Output Window for details. C:\Projects\GVR\Src Versie 6.1\GVR\Setups\GVR\GVR.wixproj : error : Error HRESULT E_FAIL has been returned from a call to a COM component. After a manual reload Loading C:\Projects\GVR\Src Versie 6.1\GVR\Setups\GVR\GVR.wixproj ... Project loaded. More details Wix build 3.5.2020 There are three setups in solution, but only one fails. Wix projects are located in a Solution folder called Setups I'm also using Resharper + Resharper for StyleCop A reinstall of Wix didn't help -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] powershell is faling at Add-PSSnapin Microsoft.SharePoint.PowerShell is failing.
First, if the execution policy doesn't already allow the execution of scripts,
your Set-ExecutionPolicy will never be executed. You can't execute a script to
allow the execution of scripts.
Are you running into a 32/64 bit issue? The Microsoft.SharePoint.PowerShell
snap-in is only registered for 64bit PowerShell and I believe that the VBScript
CA will be running in a 32 bit environment which will get you 32 bit PowerShell.
-Original Message-
From: MYFLEX [mailto:shrinuen...@gmail.com]
Sent: Tuesday, August 31, 2010 4:44 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] powershell is faling at Add-PSSnapin
Microsoft.SharePoint.PowerShell is failing.
Hi all,
Please try to understand the problem and give some solution.
I am executing the powershell exe as vbscript CA as follows.
Function f1()
MsgBox(exe started)
Set objShell = CreateObject(Wscript.Shell)
vPSscrIpt = powershell.exe -NoExit c:\yyy\aa.ps1
objShell.Run vPSscrIpt
End Function
aa.ps1 content:
Set-ExecutionPolicy RemoteSigned
$ver = $host | select version
if ($ver.Version.Major -gt 1) {$Host.Runspace.ThreadOptions =
ReuseThread}
if ((Get-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction
SilentlyContinue) -eq $null) {
Add-PSSnapin Microsoft.SharePoint.PowerShell
}
#Add-PsSnapin Microsoft.SharePoint.PowerShell
Set-location $home
$sapp = Get-SPEnterpriseSearchServiceApplication –Identity “Search
Service
Application”
New-SPEnterpriseSearchCrawlContentSource –SearchApplication $sapp –Name
“c1”
–Type Custom –StartAddress protocol://servername –CrawlPriority Normal
–MaxPageEnumerationDepth 1 –MaxSiteEnumerationDepth 1
I decalred the Custom action as follows.
CustomAction Id=f1 BinaryKey=ca VBScriptCall=f1
Execute=deferred
Impersonate=no /
Executing the custom action in installExecute seq as follows.
Custom Action=f1 Before=ProcessComponents1/Custom
But this custom action is not able to registering the sharepoint snapin
to
the powershell. Add-PSSnapin Microsoft.SharePoint.PowerShell is
failing.
but If I run the vbscript manually it is executing successfully.
Please tell me some suggestion ...
--
View this message in context: http://windows-installer-xml-wix-
toolset.687559.n2.nabble.com/powershell-is-faling-at-Add-PSSnapin-
Microsoft-SharePoint-PowerShell-is-failing-tp5481703p5481703.html
Sent from the wix-users mailing list archive at Nabble.com.
---
---
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapping and Burn
On Tue, 31 Aug 2010 09:10:20 -0400 Goryuk, Alex agor...@rosettastone.com wrote: Have you guys tried using NSIS http://nsis.sourceforge.net/Main_Page ? I've used NSIS in the past, but I have a set of existing MSI files that I just want to package up into a single exe along with the Visual C++ 2010 runtime and the .NET Framework 4 Client Profile. I've got dotNetInstaller working so I'll use that, and re-evaluate my decision once Burn comes along. [snip 4 sourceforge footers] Is there any way to get Sourceforge to remove the excess footers? It's annoying using web interfaces to the mailing list because of all the extra text. -- Bruce Cran -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapping and Burn
I don't want to hijack the list but your understanding of IntallScript is outdated by nearly a half decade. InstallShield hasn't required you to bootstrap the InstallScript engine for about 5 releases now. Also you don't even have to use InstallScript with Basic MSI projects and I don't. I tend to use WiXExtensions and C#/DTF custom actions now and only when absolutely needed. If you are talking about legacy InstallScript projects, I don't use that anymore either. I prefer the declarative approach of Windows Installer using either WiX or InstallShield as my authoring tool. I don't like NSIS because it's a procedural programming language that goes against leverage the benefits of Windows Installer. The same can be said of legacy InstallScript projects. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Bruce Cran br...@cran.org.uk To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Cc: chr...@deploymentengineering.com Sent: Tue, August 31, 2010 8:49:20 AM Subject: Re: [WiX-users] Bootstrapping and Burn On Tue, 31 Aug 2010 06:22:56 -0700 (PDT) Christopher Painter chr...@deploymentengineering.com wrote: NSIS? Sorry, I'd rather go to the dentist. You *really* don't like it, do you? :) I don't understand why not; I consider it better than InstallShield for example where you end up having to install InstallScript engine updates before you can even launch the main installer. -- Bruce Cran -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapping and Burn
For the same reason why you'd use MSI standard actions and WiXExtensions over writing your own CA's. Just as they have a data model and have been well tested, so do InstallShield setup prerequisites. Basically InstallShield's setup.exe already provides me with things like: self extracting code signing manifesting web download multiple instance servicing language selection package caching running packages before the install running packages only if features are selected patch invocation silent execution and so on. It gives me the ability to extend this with open PRQ files ( XSD based XML documents that describe packages. ) http://blog.deploymentengineering.com/2006/11/using-installshield-12-to-install-net.html It would take me an inordinate amount of time in any programming language to implement all of this and make sure it's extendable and bullet proof. Don't believe me? How many years has burn been in development? That said, I'm very interested in seeing Burn come to life. I will evaluate it against InstallShield and decide which one is better for my needs. Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Goryuk, Alex agor...@rosettastone.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, August 31, 2010 8:34:49 AM Subject: Re: [WiX-users] Bootstrapping and Burn Interesting reaction, care to explain why you wouldn't use NSIS as a bootstrapper? Out of the following: http://www.installsite.org/pages/en/msi/tips.htm#Launchers http://makemsi-manual.dennisbareis.com/bootstrapper_exe_programs.htm InstallShield's bootstrapper I haven't found a single one that can be automated, scripted, pass parameters to the bootstrapper, currently updated by the community / open source and works on every platform that currently exists and with the extensibility of NSIS. Alex On Aug 31, 2010, at 9:22 AM, Christopher Painter wrote: NSIS? Sorry, I'd rather go to the dentist. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Goryuk, Alex agor...@rosettastone.commailto:agor...@rosettastone.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Sent: Tue, August 31, 2010 8:10:20 AM Subject: Re: [WiX-users] Bootstrapping and Burn Have you guys tried using NSIS http://nsis.sourceforge.net/Main_Page ? On Aug 30, 2010, at 11:36 AM, Christopher Painter wrote: I've looked at dotNetInstaller and while it looks very interesting, there is no way you are going to learn that tool and get a working bootstrapper in 15 minutes. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: dB. dbl...@dblock.orgmailto:dbl...@dblock.org To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Sent: Mon, August 30, 2010 8:23:36 AM Subject: Re: [WiX-users] Bootstrapping and Burn http://dotnetinstaller.codeplex.com will get you there in 15 minutes or so. dB. @ dblock.orghttp://dblock.org Moscow|Geneva|Seattle|New York -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Monday, August 30, 2010 4:46 AM To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapping and Burn Hi, I realise Burn has been removed from WiX 3.5, but I'm wondering if the Visual Studio bootstrapper would be a good substitute or if I should wait for a 3.6 snapshot. My main requirement is a single file that users can download to do the installation, since I hate having a setup.exe and MSI file because it's confusing and seems unnecessary. The only component of Burn I've ever used before is setupbld, but I'm wondering - will the output of Burn be a single exe, or will it be like VS where you have to package lots of MSIs and an exe into a zip file for distribution? -- Bruce Cran -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sell apps to
Re: [WiX-users] Bootstrapping and Burn
Thank you for the feedback, really appreciate it. After talking to InstallShield tech support, we were told features we were looking for aren't supported and there's no guarantee they'd implement them anytime soon. Also, we decided to move away from InstallShield because of customizability/source control/internationalization issues. Just FYI, most of the items on the your list are either supported by NSIS by default or easily written yourself and it's not hard to learn. I wrote a rather complicated bootstrapper ( to learn NSIS ) and it took only a few days :) I agree that InstallShield has tons of companies using it and they seem solid. I will not agree it's bulletproof, we've found bugs that are still not fixed ( several years later ). Alex On Aug 31, 2010, at 11:28 AM, Christopher Painter wrote: For the same reason why you'd use MSI standard actions and WiXExtensions over writing your own CA's. Just as they have a data model and have been well tested, so do InstallShield setup prerequisites. Basically InstallShield's setup.exe already provides me with things like: self extracting code signing manifesting web download multiple instance servicing language selection package caching running packages before the install running packages only if features are selected patch invocation silent execution and so on. It gives me the ability to extend this with open PRQ files ( XSD based XML documents that describe packages. ) http://blog.deploymentengineering.com/2006/11/using-installshield-12-to-install-net.html It would take me an inordinate amount of time in any programming language to implement all of this and make sure it's extendable and bullet proof. Don't believe me? How many years has burn been in development? That said, I'm very interested in seeing Burn come to life. I will evaluate it against InstallShield and decide which one is better for my needs. Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Goryuk, Alex agor...@rosettastone.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, August 31, 2010 8:34:49 AM Subject: Re: [WiX-users] Bootstrapping and Burn Interesting reaction, care to explain why you wouldn't use NSIS as a bootstrapper? Out of the following: http://www.installsite.org/pages/en/msi/tips.htm#Launchers http://makemsi-manual.dennisbareis.com/bootstrapper_exe_programs.htm InstallShield's bootstrapper I haven't found a single one that can be automated, scripted, pass parameters to the bootstrapper, currently updated by the community / open source and works on every platform that currently exists and with the extensibility of NSIS. Alex On Aug 31, 2010, at 9:22 AM, Christopher Painter wrote: NSIS? Sorry, I'd rather go to the dentist. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Goryuk, Alex agor...@rosettastone.commailto:agor...@rosettastone.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Sent: Tue, August 31, 2010 8:10:20 AM Subject: Re: [WiX-users] Bootstrapping and Burn Have you guys tried using NSIS http://nsis.sourceforge.net/Main_Page ? On Aug 30, 2010, at 11:36 AM, Christopher Painter wrote: I've looked at dotNetInstaller and while it looks very interesting, there is no way you are going to learn that tool and get a working bootstrapper in 15 minutes. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: dB. dbl...@dblock.orgmailto:dbl...@dblock.org To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Sent: Mon, August 30, 2010 8:23:36 AM Subject: Re: [WiX-users] Bootstrapping and Burn http://dotnetinstaller.codeplex.com will get you there in 15 minutes or so. dB. @ dblock.orghttp://dblock.org Moscow|Geneva|Seattle|New York -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Monday, August 30, 2010 4:46 AM To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapping and Burn Hi, I realise Burn has been removed from WiX 3.5, but I'm wondering if the Visual Studio bootstrapper would be a good substitute or if I should wait for a 3.6 snapshot. My main requirement is a single file that users can download to do the installation, since I hate having a setup.exe and MSI file because it's confusing and seems
Re: [WiX-users] Newbie x64 msi question
Do component GUIDs have to be different? -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Tuesday, August 31, 2010 03:54 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Newbie x64 msi question Hi, I have recently made a 64 bit MSI from a single source and I started out by following http://blogs.msdn.com/b/astebner/archive/2007/08/09/4317654.aspx The trick to make it easy is the -arch command (or setting the processor type in votive), but you also need to do a few other things. I conditionally set the product code and product name ... ?if $(var.Platform)=x64 ? ?define displayName = Product name (x64) ? ?define productCode = A guid ? ?else? ?define displayName = Product name (x86) ? ?define productCode = Another guid ? ?endif? Product Id=$(var.productCode) Language=0 Manufacturer=Company Name=$(var.displayName) Version=8.5.$(var.buildNumber) Codepage=0 UpgradeCode=Yet another guid, these things get everywhere Set the Platform attribute on the Package Element with the built in variable... Platform=$(var.Platform) Then I have a conditional root directory structure as programs should be installed under ProgramFiles64Folder on 64 bit windows... ?if $(var.Platform)=x64 ? Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFiles64Folder Directory Id=CompanyProgramsDir Name=SDL /Directory /Directory /Directory ?else ? Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=CompanyProgramsDir Name=SDL /Directory /Directory /Directory ?endif ? The rest of the directory structure is based off a DirectoryRef Id=CompanyProgramsDir so doesn't need to be duplicated. All components in the MSI have * as the component guid, so the conditional root folders above mean that the 32 and 64 bit MSIs will have different component guids. I also have a launch condition that stops the 32 bit MSI being installed on 64 bit windows, which it sounds you don't need. It all seems to be working so far. Dave -Original Message- From: Andres Juarez [mailto:andresj_...@hotmail.com] Sent: 30 August 2010 06:37 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Newbie x64 msi question Hi Bob, In your post http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/. Use the -arch switch and you get smart defaults. So, running candle with teh -arch switch does take care of marking the components at 64 bits, but if using the same Wix source file for the 32 and 64 bits installer with the only difference of the candle -arh switch, the Components GUIDS for the 64 and 32 bits installer are all the same. The two installers cannot install in the same box since the launch conditios are mutually exclusive. Do we still need to have unique GUIDS per components, I am almost sure we do, but just asking. Thanks Andres Date: Sat, 7 Aug 2010 10:56:31 -0400 From: b...@joyofsetup.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Newbie x64 msi question On 8/4/2010 9:57 AM, Pally Sandher wrote: You need to set the Win64 attribute on your components. If it's not set they default to 32-bit components in an x64 package. An easy way to do it is to use a pre-processor variable set to no or yes whether you're building x86 or x64 packages respectively. Then you can simply use something like Win64=$(var.is64bit) in all the components you need to. See http://wix.sourceforge.net/manual-wix3/preprocessor.htm Unnecessary: See http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/. Use the -arch switch and you get smart defaults. -- sig://boB http://joyofsetup.com/ -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users /pre BR style=font-size:4px; a href = http://www.sdl.com;img src=http://www.sdl.com/images/email logo_150dpi-01.png alt=www.sdl.com border=0//a BR font face=arial size=2a href = http://www.sdl.com; style=color:005740;
Re: [WiX-users] How to make the custom action run under LocalSystem account?
If you're in an environment where the system account presents machine credentials to the network that'll often work, and if you know that's always the case everywhere you install then that'll be fine. Phil Wilson -Original Message- From: Elfe Xu [mailto:elf...@microsoft.com] Sent: Tuesday, August 31, 2010 12:01 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to make the custom action run under LocalSystem account? Yes! After I set ALLUSERS=1, it runs as local system and delete the remote folder. When the system account go through network, it is using the computer account (MachineName$). And my folder is granting permission to MachineName$. Thanks, -Elfe -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-make-the-custom-action-run-under-LocalSystem-account-tp5474012p5481429.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to change an entry using XmlConfig
In your Value= line you will need to escape the square brackets. XMLConfig mentions this in the Value Attribute Description column. Opening bracket - [\[] Closing bracket - [\]] -Original Message- From: Alexander op de Weegh [mailto:alexan...@ipa-tp.nl] Sent: Tuesday, August 31, 2010 3:50 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to change an entry using XmlConfig Hi all, I am not an expert on Xml, let alone XPath, so I am running into this problem. With my application the following NHibernate.config file is used: ?xml version=1.0 encoding=utf-8 ? hibernate-configuration xmlns=urn:nhibernate-configuration-2.2 session-factory property name=connection.providerNHibernate.Connection.DriverConnectionProvide r/property property name=proxyfactory.factory_classNHibernate.ByteCode.LinFu.ProxyFactory Factory, NHibernate.ByteCode.LinFu/property property name=connection.driver_classNHibernate.Driver.MySqlDataDriver/proper ty property name=connection.connection_stringDatabase=schemaname;Data Source=localhost;User Id=username;Password=password/property property name=dialectNHibernate.Dialect.MySQLDialect /property /session-factory /hibernate-configuration The configuration file is set up to be used from the Visual Studio environment. In my Wix file, I have the following entry: util:XmlConfig Id='MySqlConnectionProperty' File='[INSTALLDIR]\NHibernate.config' Action='create' ElementPath='//hibernate-configuration/session-factory/propert...@name= connection.connection_string\]' Node='value' Value='Database=[MYSQLSCHEMA];Data Source=[MYSQLHOSTNAME];User Id=[MYSQLUSERNAME];Password=[MYSQLPASSWORD]' Sequence='1' On='install'/ With this XmlConfig entry, I try to modify the value of the connection string in the NHibernate.config file according to the settings specified by the user during the installation. The MYSQLxxx parameters are collected in one of the custom dialogs. During the run of the Xml linker, the following error occurs: LGHT0204 : ICE03: Invalid format string; Table: XmlConfig, Column: ElementPath, Key(s): MySqlConnectionProperty Can anyone help me out here? Thanks in advance, Met vriendelijke groeten / With kind regards, Alexander op de Weegh Office: +31(0)226-335023 Mobile: +31(0)6-20138301 IPA Total Productivity Kosterij 4 1721 PN Broek op Langedijk The Netherlands www.ipa-tp.nl of kijkt u eens op www.blean.nl van onze partner B-Lean voor het trainen en implementeren van productiemethodieken en het verbeteren van uw productiviteit. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat.exe does not export COM information for a .NET component dll
Hi, I am using WIX 3.0 to export the COM registry setting from a managed component dll but I only get a file without the COM information. I can use regasm to registery this dll. I use the same heat.exe to export another .net component dll successfully. The only difference of these two dlls are the first one (where heat fails) depends on an interop assembly exported from a tlb file, while the latter (where heat succeeds) does not. Can anybody tell why heat cannot export COM information for the first one? Thanks Leon -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Default Install Drive to be Largest Free Space Drive of Physical Disk
Hello, By defaul in wix (I am using 3.5) the drive letter is selected to the largest available in PC (may be a USB). How can I make sure my installer will do the same (defaul to largest free space drive) but on my physica disk. Please advise. Thanks, Prabhat -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Default-Install-Drive-to-be-Largest-Free-Space-Drive-of-Physical-Disk-tp5484492p5484492.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Default Install Drive to be Largest Free Space Drive of Physical Disk
That is handled by the ROOTDRIVE property. Not sure you can avoid USB drives, though. http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx -Original Message- From: Prabhat_IE [mailto:prabhat.n...@gmail.com] Sent: Tuesday, August 31, 2010 2:00 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Default Install Drive to be Largest Free Space Drive of Physical Disk Hello, By defaul in wix (I am using 3.5) the drive letter is selected to the largest available in PC (may be a USB). How can I make sure my installer will do the same (defaul to largest free space drive) but on my physica disk. Please advise. Thanks, Prabhat -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Default-In stall-Drive-to-be-Largest-Free-Space-Drive-of-Physical-Disk-tp5484492p54 84492.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat.exe does not export COM information for a .NET component dll
On 10-08-31 3:25 PM, Lian Jiang wrote: Hi, I am using WIX 3.0 to export the COM registry setting from a managed component dll but I only get a file without the COM information. I can use regasm to registery this dll. I use the same heat.exe to export another .net component dll successfully. The only difference of these two dlls are the first one (where heat fails) depends on an interop assembly exported from a tlb file, while the latter (where heat succeeds) does not. Can anybody tell why heat cannot export COM information for the first one? I had this problem when heat could not load the DLL due to missing dependencies. If your component depends on something in another directory, you should add it to the path. Not sure if that is the correct solution, but it was the one I found anyway. -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] IIsExtension Catch-22
Hey all, I've got a MSI that installs a virtual directory using the iis:WebVirtualDir element to an existing web site. Install works great. However, if someone manually deletes the web site, the MSI won't uninstall because it can't find stuff. The errors from the log are below: ConfigureIIsExec: A matching web object in memory was found, but the web object in memory has no associated base ConfigureIIsExec: Error 0x80070002: Failed to find Web base ConfigureIIsExec: Error 0x80070002: Failed to get base of web for WebDir ConfigureIIsExec: Error 0x80070002: failed while processing WebDirs MSI (s) (B0!84) [17:42:28:079]: Product: HelloWorld -- Error 26003. Failed while processing WebDirs. (-2147024894 ) Error 26003. Failed while processing WebDirs. (-2147024894 ) Is there a way to tell the iis:Web* elements to just ignore the error(s) since the metabase entries are already gone? - Ed -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Paraffin 3.5 - Now with better Minor Update Support
Hello my fellow WiXers! It's time for another update to my Paraffin tool which makes managing your fragments easier. With 3.5 I've implemented the trick outline by Vagmi Mudumbai (http://geekswithblogs.net/Vagmi.Mudumbai/archive/2006/06/11/81426.aspx) of allowing minor upgrades (AKA patches) to remove files by setting the transitive bit on the component and adding a conditional element that evaluates to false. Component Id=comp_F5B392C05B5249C2AB34810BE4A6163F Guid=FD9D7BF4-550A-47E2-85A3-634D77F609FB Transitive=yes File Id=file_81DD236ED61B4BBEB445FAB9E9C2DAB2 Checksum=yes KeyPath=yes Source=.\Temp\a.exe / Condition1 = 0/Condition /Component But what about those zero length files you'll need? I've got you covered. When you specify the -PatchUpdate switch, you can add the new -PatchCreateFiles switch and Paraffin will create the zero byte files for you. Don't worry, when you rerun Paraffin again with -PatchUpdate, if the zero byte file is there, Paraffin checks if the Transitive attribute is set and makes sure to keep everything straight. While you could keep those zero byte files in your version control system, which seems a little odd to me since they are, well, no longer needed. Because Paraffin knows which files have been deleted with the Transitive attribute on the Component element you can recreate the zero byte files at any time by using -PatchUpdate file.wxs as the command line. The idea is that you'll run this as part of your build so you never have to worry about those zero byte files. More about what's new: http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/08/31/paraffin-3-5-now-with-better-minor-upgrade-support.aspx Download the bits and source: http://www.wintellect.com/CS/files/folders/18310/download.aspx As always, let me know if there are any features you'd like to see in Paraffin (or bugs you find!). If you haven't heard of Paraffin before, read this http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/08/31/zen-of-paraffin.aspx. John Wintellect http://www.wintellect.com +1-877-968-5528 -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapping and Burn
That's unfair to dotNetInstaller at least. NSIS doesn't quote qualify as a bootstrapper in my book despite several nice tutorials about how to use it as such. NSIS bundles bootstrapper responsibilities together with the installer responsibilities and falls short with anything beyond the relatively basic scenarios. You can squeeze more with complex scripting, but it's just a glorified batch file, something you'll enjoy only if your last assignment was programming a VAX. Try making sense of an NSIS script written by a setup developer after a year or two of work! InstallShield bootstrapper in the recent versions of InstallShield is actually pretty good. I would feel major heartburn paying $ for a bootstrapper though, given the quality and feature set of the free options (I really think there's only one free option - dotNetInstaller, but I am bias being its maintainer and funding most of its development). We do all like the idea of Burn. It promises some nice features like a single progress bar. But I wonder how much I'll really care when it's out - installation is not a feature of my product just like driving is not a feature of my car. cheers -dB. dB. @ dblock.org Moscow|Geneva|Seattle|New York -Original Message- From: Goryuk, Alex [mailto:agor...@rosettastone.com] Sent: Tuesday, August 31, 2010 9:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrapping and Burn Interesting reaction, care to explain why you wouldn't use NSIS as a bootstrapper? Out of the following: http://www.installsite.org/pages/en/msi/tips.htm#Launchers http://makemsi-manual.dennisbareis.com/bootstrapper_exe_programs.htm InstallShield's bootstrapper I haven't found a single one that can be automated, scripted, pass parameters to the bootstrapper, currently updated by the community / open source and works on every platform that currently exists and with the extensibility of NSIS. Alex On Aug 31, 2010, at 9:22 AM, Christopher Painter wrote: NSIS? Sorry, I'd rather go to the dentist. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Goryuk, Alex agor...@rosettastone.commailto:agor...@rosettastone.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Sent: Tue, August 31, 2010 8:10:20 AM Subject: Re: [WiX-users] Bootstrapping and Burn Have you guys tried using NSIS http://nsis.sourceforge.net/Main_Page ? On Aug 30, 2010, at 11:36 AM, Christopher Painter wrote: I've looked at dotNetInstaller and while it looks very interesting, there is no way you are going to learn that tool and get a working bootstrapper in 15 minutes. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: dB. dbl...@dblock.orgmailto:dbl...@dblock.org To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Sent: Mon, August 30, 2010 8:23:36 AM Subject: Re: [WiX-users] Bootstrapping and Burn http://dotnetinstaller.codeplex.com will get you there in 15 minutes or so. dB. @ dblock.orghttp://dblock.org Moscow|Geneva|Seattle|New York -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Monday, August 30, 2010 4:46 AM To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapping and Burn Hi, I realise Burn has been removed from WiX 3.5, but I'm wondering if the Visual Studio bootstrapper would be a good substitute or if I should wait for a 3.6 snapshot. My main requirement is a single file that users can download to do the installation, since I hate having a setup.exe and MSI file because it's confusing and seems unnecessary. The only component of Burn I've ever used before is setupbld, but I'm wondering - will the output of Burn be a single exe, or will it be like VS where you have to package lots of MSIs and an exe into a zip file for distribution? -- Bruce Cran -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be
[WiX-users] Context menu handler registration on 64 bit
This has probably been asked before (but I can't find a good way to search this list?): I've created my wix installer (with a bit of help from heat on the COM dll) which installs a simple shell folder context menu extension. It all works great on x86, but on x64 the context menu items don't show up... Is there anything special (like elevation etc) I need to take into account when installing a shell extension on x64? Anybody dealt with this before (I'm sure!)? Thanks, Mike -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Default Install Drive to be Largest Free Space Drive of Physical Disk
By default WiX will choose the largest free space available drive (including USB). But I need to eliminate USB. Is that possible or any one has implemented that? Thanks, Prabhat -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Default-Install-Drive-to-be-Largest-Free-Space-Drive-of-Physical-Disk-tp5484492p5485557.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
