I'd suggest, uninstall/re-install rather than repair but having said that I
don't see why it would break with update 1.
-Original Message-
From: George Fleming [mailto:gef...@microsoft.com]
Sent: 06 March 2013 23:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [
I should have been more explicit, I mean write a CA to do whatever your
powershell script is doing - just calling powershell from a CA would probably
have the same issue as just calling the script from a standard CA (as you have
found out).
Neil
-Original Message-
From: Steven Ogilvie
On 06-Mar-13 16:08, Perry Taylor wrote:
>
This component needs a GUID because automatic GUIDs aren't supported
with only shortcuts.
--
sig://boB
http://joyofsetup.com/
--
Symantec Endpoint Protection 12 positioned as
I am using Wix 2.0 to author an MSI in which I have an edit control which
restricts the number of characters to say 100. Now the thing is in a corner
case test scenario when I copy paste text > 100 characters the installer is
unhappy and throws an error dialog saying something on the lines of "u
Hi Jacob,
Thanks for the reply..
I need to have single Instance MSI as a package.And based on your reply
,Seams like it should be property driven. And Can you point out me some
"remember me pattern and conditions on the components" and how some
components can be filtered(skipped) from harvest.wx
Do you need to support multiple instances on the same box?
If yes, you need to look at instance transforms. If no, then property drive the
install using the remember me pattern and conditions on the components for each
instance. If the differences are all config based, you could use ca's to writ
Hi we have requirement such that need to create a single MSI package of a web
application for all the Environments(UAT,DEV,TEST,PROD) such that we pass
parameter(Environment) to MSI Installer during installation;based on that we
need to get those Environment files(config files) installed and filter
Not a typo. I want to go from VS2010 Ultimate SP1 to VS2012 Ultimate Update 1.
I did try to "repair" install Wix 3.7.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, March 06, 2013 1:45 PM
To: General discussion for Windows Installer XML toolset.
ROFTLMAO!
Yes, it's unfortunatly named.
There is a DTF.chm in the start menu via WiX. I've blogged a lot about it
and in a nutshell it's the gold standard for writing any kind of managed
code interoping with MSI. ( Build, Tools, Custom Actions...)
Yes, we did the same with WiX 3.5 and it worked fine, now with WiX 3.6 and
3.7 it doesn't. I have set the property to empty, and now it happens to work
with the latest WiX as well.
Thank you for pointing this to me!
I have no knowledge of how to using "burn" to accomplish our nested
installat
I did a custom action:
[CustomAction]
public static ActionResult InstallNServiceBusLicense(Session session)
{
try
{
if (session == null)
{
throw new ArgumentNullException("session");
}
string tempString = GetSe
I'd have to agree with Chris write a proper custom action using DTF (see DTF
Documentation in the WiX install - basically C# custom actions but with all the
hard work done for you), running scripts it notoriously hard (well it was for
vbscripts and I am not sure powershell is any better).
I am
I'm guessing a typo and the first one should be VS2008SP1 not 2012, if so the
when you go from 2008 to 2012 the easiest option is to reinstall WiX as it
needs to register with Visual Studio.
Neil
-Original Message-
From: George Fleming [mailto:gef...@microsoft.com]
Sent: 06 March 2013
You need to get more information about what the powershell script is actually
doing while it is doing it. For example, if you know that the Install-License
cmdlet is supposed to change the registry, then update your script to write out
the appropriate registry information immediately after the I
The 64 bit MSI is checking the 64 bit registry for the POWERSHELL exe via
Win64=yes
The Custom action now has DllEntry="CAQuietExec64"
If I take the custom action value and run it in a CMD prompt it works, which
means the Powershell PS1 script is good, and the custom action value is good as
wel
In light.exe I am receiving the following error and do not know why.
C:\VDSBeta\VDSInstaller\rcr.vds.wxs(23) : error LGHT0230 : The Component/@Guid
attribute's value '*' is not valid for this component because it does not meet
the criteria for having an automatically generated guid. Components u
Just use the ~ operator to do a case insensitive comparison.
CREATETABLE~="yes"
Btw, they called public properties not global properties.
From: "George Fleming"
Sent: Wednesday, March 06, 2013 1:33 PM
To: "wix-users@lists.sourceforge.net"
Subject: [WiX
Hosting the PowerShell engine is not an easy thing to do. If you must use the
provided cmdlet then the easiest way to execute it will be with a script.
You'll just need to find out what it is doing and get your bitness all sorted
out.
Edwin G. Castro
Software Developer - Staff
Digital Channels
What is DTF, I googled it but I don't think you mean what urban slang came up
with ;)
We are using NServiceBus as a service bus... its core dll has PowerShell
cmdlets within, we need to use one of its cmdlets to register its license into
the registry
I tried running a C# custom action and was
The log suggests that it executed now but it didn't produce any output. You may
want to write some output so that you can determine what is going on. Perhaps
you can have powershell write out the registry information so that you can data
in the msi log?
Also, now that you got 64-bit powershell
I guess I have to wonder
Why run PowerShell period?
I mean, DTF is very powerful and robust. It's also possible to use DTF to
write a managed custom action and call PowerShell code from there.
The only argument I ever here for PowerShell is it's for guys who know how
to script. These "sc
This is driving me crazy, how hard is it to run a PowerShell script...
If I run it in a CMD prompt PowerShell.exe .\RegisterLicense.xml it works!!!
My dev machine is Window 7 64 bit
This DLL is not our DLL it is a 3rd party dll NServiceBus.Core.dll we can not
change it... they have the PowerShel
Use ~=
-Original Message-
From: George Fleming [mailto:gef...@microsoft.com]
Sent: Wednesday, March 06, 2013 1:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How do i convert a global property string value to
uppercase (or lowercase)?
I have a global property that's modi
I have been using VS2010SP1 with Wix3.7, and everything works. Recently, I
installed VS2012. When I tried to open the installer solution using VS2012, I
got a warning that .wixproj is not supported, and the wix project does not
load. I re-installed Wix3.7, but that did not help. I also notic
I have a global property that's modifiable by the user via command line
parameter. How do I convert it to uppercase before using it in a Condition
statement?
For example, if global is "CREATETABLE", I could do something like this:
It would be nice if I could convert it to uppercase, and just
Looking back at your original email I see the following:
The DllEntry="CAQuietExec" attribute is putting you in 32-bit land.
You need to use DllEntry="CAQuietExec" for 32-bit and DllEntry="CAQuietExec64"
for 64-bit.
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 50
In this case it is a 64 bit MSI (our services installer has a 32 bit and a 64
bit MSI based on the bitness of the OS, in this case testing with 64 bit MSI)
since the path is:
MSI (s) (30:B0) [12:56:34:248]: Executing op:
CustomActionSchedule(Action=CA_NSERVICEBUSLICENSE.CA23A0DC_B2DE_4F2C_9E74_
The useLegacyV2RuntimeActivationPolicy="true" is what allows .NET 4 to load
.NET 2 assemblies so you need that. You don't want to remove it.
I assume you checked the system where the MSI is installing so my next guess is
that 64-bit powershell has the configuration file while 32-bit powershell d
Hmm
Your right I have PS version 3 but the powershell config is loading .NET 4
So why is it still failing? Is it because of the legacyV2 is set to true?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: March-06-1
My guess would be that you have PowerShell v3 installed on your system. Check
the value of the $PSVersionTable variable in PowerShell as that will give you
detailed version information for PowerShell.
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 50
You didn't clear it, you set it to a space. We're you doing the same in the old
install?
Also, is there a reason you didn't use burn and avoid all of hacks around
nested installs?
On Mar 6, 2013, at 3:44 AM, "msporek" wrote:
> It is done on purpose, because this MSI is specific in the sense, t
It is done on purpose, because this MSI is specific in the sense, that we use
it launch uninstallation of other MSI components that our product chains -
and those other MSI components are not shown in ARP. What I mean is that we
have just a single entry in ARP for this specific MSI, and when you cl
32 matches
Mail list logo
