This is how things are setup:
All assemblies reference the same AssemblyVersion.cs.
CruiseControl runs a .cmd batch file that executes sed and updates the version
infos in the file using the build number from CruiseControl.
CruiceControl then starts an MSBuild task that compiles and packages the b
If the version info that shows up in the output from heat is something you
provide as an input to your build, you could replace it in heat with
"$(var." or"$(env." entries where you supply those inputs to candle or the
build environment, as appropriate. That would "automate" that part of the
proces
As I understand it, a feature can have only one parent.
If you want to use control events, something like this (borrowed from Arun)
should work:
In the
Possibly even better (instead of the above), if you want just the PKGTYPE
prop
I need COM/Interop registration.
Yesterday I harvested my assemblies with HEAT, cleaned up the output and use
that as a separate .wxs. It works, but still requires that I update the version
info for the assemblies manually in the file before a release. Well, I guess I
could use sed to replace t
If you want to change features according to user's slection, there are two
ways:first, use , however this tag is useful only before
CustomizeDlg closes. If you want to change after that, there is another way:
use
2009-11-27
salever.lee
发件人： akihiro.shib...@jp.yokogawa.com
What kind of registration do you need? COM/interop registration? Or just the
ability of the two assemblies to find each other when installed into the
same directory?
-Original Message-
From: Asker Brodersen [mailto:asker.broder...@esri-sgroup.se]
Sent: Thursday, November 26, 2009 1:09 AM
The advantages of a "data-driven" design instead of a procedural design boil
down to two:
1- Resiliency: you can effect installations and removals without requiring a
"working state" of some obscure part of the ecosystem which usually includes
the program you are installing/removing. This means yo
Hello Blair,
Leaving registry keys behind isn't the biggest issue, and I could deal
with leaving some things behind if they didn't replace existing
values. But as I wrote in an earlier post, my application deals in the
improvement of the experience dealing with files outside the
applications insta
I browsed to the CUB that was in the WiX directory. Is that not the latest?
--- On Wed, 11/25/09, Rob Mensching wrote:
> From: Rob Mensching
> Subject: Re: [WiX-users] IIS Extension - ICE68 Validation Error
> To: chr...@deploymentengineering.com, "General discussion for Windows
> Installer X
>Orca thinks that the patch is OK, but when you apply it nothing changes?
>This smells like a component-rule violation.
>After applying the patch, run a repair of the product. Is the product correct
>then?
Cheers for the suggestion, but the same result. Running repair on the original
product s
Hi,
I'm trying to have WIX register my assemblies, but when I do the install they
are only copied to the right location, not registered. What's the correct way
of doing this, I don't want them in the GAC?
This is what I'm doing (two different attempts):
Looking around the net I've see
That log entry simply says that the custom action ran and returned a status
of success.
The fact that the custom action is in a merge module shouldn't affect its
operation unless it is either reading or writing database tables from the
merge module, in which case it should have been written to kno
12 matches
Mail list logo
