Looks like you are passing your source code to the linker. That's like
passing a .cpp file to link.exe. Won't work. Try passing the .wixobj(s).
On Wed, May 9, 2012 at 6:49 AM, Charles Broadfoot <
charles.broadf...@microsoft.com> wrote:
> Its telling me that the wix tag is invalid. I pasted the o
Wow, can you point to exactly where you got the vc_red.msi? The
SuppressLooseFilePayloadGeneration was added to temporarily support some
stupidly authored MSI files in Visual Studio. The plan was they would fix
the MSIs and this attribute would be removed.
It never occured to me that they may hav
"80,81" just defaults to port 80, 81 seems to be ignored.
Having two "port" properties yields this:
'Port' is a duplicate attribute name
Creating two website elements then seems the way to go, but won't this result
in two different websites?
-
Lars Augensen
Software Engineer
-Original Messa
I am using following but its not working (at-least OS check should work but
its not):
Not Privileged
Installed OR (VersionNT=600 AND ServicePackLevel>=2) OR
(VersionNT=601 AND ServicePackLevel>=1)
Installed OR NETFRAMEWORK40CLIENT OR NETF
Thank you phil, this clears it up, I have 2 shortcuts to one exe, just with a
different argument.
Simon
-Original Message-
From: Philip Sayers [mailto:p...@cds-am.net]
Sent: 09 May 2012 15:22
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Shortcut hi
Rob Mensching-7 wrote
>
> Wow, can you point to exactly where you got the vc_red.msi? The
> SuppressLooseFilePayloadGeneration was added to temporarily support some
> stupidly authored MSI files in Visual Studio. The plan was they would fix
> the MSIs and this attribute would be removed.
>
> It
I have written a preprocessor extension that has a dependency to another
assembly. When I try to build a setup project using that extension, I
get an error saying:
In the preprocessor extension that handles prefix 'somePrefix' while
trying to call function 'someFunction' and exception has occur
The name in the error message and the name of the dll is spelled
differently, can it be as simple as that?
/Simon
On Thu, May 10, 2012 at 3:00 PM, Morten Lemvigh <
morten.lemv...@novasoftware.se> wrote:
> I have written a preprocessor extension that has a dependency to another
> assembly. When I
On 10-05-2012 14:31, Simon Dahlbacka wrote:
> The name in the error message and the name of the dll is spelled
> differently, can it be as simple as that?
Sorry, that is just a typo I introduced when replacing the original
assembly name. The names are the same in the two places.
/Morten
-
This turned out to be the best solution:
-
Lars Augensen
Software Engineer
-Original Message-
From: Lars Augensen [mailto:lars.augen...@confirmit.com]
Sent: 10. mai 2012 10:10
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multiple p
Hi,
I'm trying to create a managed bootstrap installer but the error log is telling
me it's failing to create it:
[0AFC:15D4][2012-05-10T17:38:07]: Setting string variable
'WixBundleOriginalSource' to value 'C:\temp\testbundle\Bundle.exe'
[0AFC:15D4][2012-05-10T17:38:08]: Setting string variabl
*looks sheepish*
Forgot the:
[assembly: BootstrapperApplication(typeof(TestBa.TestBa))]
All good now :)
Cheers,
Nigel
-Original Message-
From: Nigel Morse [mailto:nigel.mo...@red-gate.com]
Sent: 10 May 2012 17:46
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Managed bootstr
On 08-May-12 11:45, Gareth wrote:
> Up until now I have been able to merge VC90 merge modules of both x86 and x64
> varieties into the same package without any problem.
That's legal in an x64 package only.
--
sig://boB
http://joyofsetup.com/
-
On 07-May-12 09:51, Dmuller720 wrote:
> But the question is still, can someone help me get a picture as the image
> for a rectangular button?
Use @Bitmap="yes" and @Text="Binary/@Id of bitmap".
--
sig://boB
http://joyofsetup.com/
-
Hi,
We have a WiX project using Visual Studio 2005, with WiX 3.5, and I want
to use torch.exe to create a transform of the differences between the
english and german versions of the installer. (I am using .wxl files to
generate en-us and de-de versions of the installer.)
How do I get to the
The topic of automating Heat has come up several times on the Users list. I
haven't seen anyone post an implementation. At work I'm about to write such
an extension but /only/ concerning harvesting specific COM visible DLLs.
I'm reading about Wix Extensions and brushing up on the Component Rules
I use the WIX environment variable which you can access just like a property.
(i.e., $(WIX)). In this manner, the path to candle would be
$(WIX)bin\candle.exe.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341
I've done it and it works fine. One tricky thing was working with
PowerShell's parsing modes to get the arguments passed-in correctly (notice
the back-tick-escaped double quotes in the $msBuildArgs parameter, below).
If you manually use Candle/Light you have to worry about compiling fragments
ah
Here is what I consider a better powershell script to execute msbuild. What I
really like about this script is that it finds msbuild on its own and sets a
number of default values that can be overridden at call-time. This script is
really good for command line usage. If I just needed to automate
On 10-05-2012 14:00, Morten Lemvigh wrote:
> I have written a preprocessor extension that has a dependency to another
> assembly. When I try to build a setup project using that extension, I
> get an error saying:
>
> In the preprocessor extension that handles prefix 'somePrefix' while
> trying to c
20 matches
Mail list logo
