>> if you had to maintain a separate test project, it's not a big burden.
While thinking about this issue yesterday, I came to a similar conclusion.
I have a single 'toolbox' Extension project(s) to which I add different
Compiler Extension implementations as partial classes (and CAs for both
Win3
On 09-Feb-15 13:18, Phill Hogland wrote:
> MSBuild project which would do the Test, and then if no failures, build the
> Package, however my observation is that I can only get either the Test
> 'build' or the 'package' build to work.
That seems likely. MSBuild projects generally have one output so
On 09-Feb-15 14:47, Nick Ramirez wrote:
> As far as a robust test, this is pretty weak. Setting a property is just a
> small part of the install process. But the sum total of an installation is
> to put files on the system, configure the registry, install and start
> services, etc.
You're mixing un
Your comments were helpful. I think I have some ideas on how to address my
concern and take advantage of the information that you added.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Lux-and-Nit-tp7597183p7599165.html
Sent from the wix-use
It makes sense to me that lux has value when implementing a data driven CA
pattern. I don't expect lux to cover the areas that those other tools
target, but thanks for that information.
http://robmensching.com/blog/posts/2007/9/13/zataoca-custom-actions-should-be-data-driven/
--
View this mess
Lux, as I understand it, tests that a property has a particular value after a
custom action has run.
As far as a robust test, this is pretty weak. Setting a property is just a
small part of the install process. But the sum total of an installation is
to put files on the system, configure the regis
With the recent build of wix 3.10.0.1403 I was able to get my simple Lux/Nit
test project to work. Thanks! I initially used a .cmd file to call lux,
candle, light, and then nit. But I prefer to build my projects using
MSBuild, so I figured out how to use the 'Test' Target (and the
BuildTestPacka
On 27-Jan-15 16:50, Phill Hogland wrote:
> I realized that I should be using 3.10 to pick up the fix for nit. I
> installed 3.10.1124.0, but get the same errors, with the same message in the
> msi log.
That fix is still in a pull request:
https://github.com/wixtoolset/wix3/pull/160. I'll ping Rob
I realized that I should be using 3.10 to pick up the fix for nit. I
installed 3.10.1124.0, but get the same errors, with the same message in the
msi log.
SFXCA: Failed to get requested CLR info. Error code 0x80131700
--
View this message in context:
http://windows-installer-xml-wix-toolset.6
I'm sorry for the delay in getting back to this subject, but since I just
coded up my first semi-custom action (into a CompilerExtension) I wanted to
see if I could also understand how to use lux. While I have wix 3.9 RC2
installed, I am getting the same nit errors (NIT8104) posted before. I
foun
On 11-Oct-14 12:59, Phill Hogland wrote:
> This results in NIT8104: Package Failed: Fatal error during installation
Yet another bug. The Lux custom actions are written in DTF and they
aren't set up for .NET 4.0. I have a pull request ready:
https://github.com/wixtoolset/wix3/pull/160
--
sig://b
Thanks for the info.
I started over with a new VS2013 msi setup template project. I added code,
essentially from Rob's remember property pattern post, and then used the
same command line file I shared earlier. I now get further down the path
successfully producing the xxx_test.msi (and not seein
On 09-Oct-14 19:15, Phill Hogland wrote:
> I see that I still have the -ext WixUtilExtension on the above candle
> command. I removed it but Light still fails saying that 'User' Table is
> not defined. I can't find anything else in my project related to the User
> table. When I first started th
I see that I still have the -ext WixUtilExtension on the above candle
command. I removed it but Light still fails saying that 'User' Table is
not defined. I can't find anything else in my project related to the User
table. When I first started this project I added a reference to my PkgLib
in wh
Te report of Nit failing, above, is when I added the 'Test' target to my main
project without adding any Lux specific commands. So while the verbose
MSBuild log that I posted showed that it tried to collect the UnitTest wxs
and compile them, it did not run the linker and produce a different MSI
pa
On 09-Oct-14 14:11, Phill Hogland wrote:
> Since building in VS2013 with the Target "Test" fired after the Target
> "Build" results in the invalid SQL error in Nit, I created a cmd batch file
> to mimic the command line instructions in the chm. Lux and Candle succeed,
> but Light fails with LGHT01
I stripped everything out of my 'product' project except what was necessary
to do only the first test in the Simple sample.
Since building in VS2013 with the Target "Test" fired after the Target
"Build" results in the invalid SQL error in Nit, I create
I am looking for advice on how to use Lux and Nit. I have read the chm docs
and the two posts to Joy of Setups. I have also reviewed the sample
projects in the source and looked at the lux related targets in the source
code. I have tried several approaches to using Lux without success, so I
crea
18 matches
Mail list logo
