The footer of each message sent has a link to
https://lists.sourceforge.net/lists/listinfo/wix-users which has the
unsubscribe method.
Chris
On Wed, Nov 18, 2009 at 10:22 AM, Robert O'Brien <
robert.obr...@microsoft.com> wrote:
> Been trying various supported subscription configuration options,
t) as all other code :)
> So I think it is not a point.
>
> 2009/7/16 Christopher Karper
>
> > Scripting CAs are generally considered more brittle than any other kind
> of
> > CA, so they are not as preferred, IMO.
> >
> > However, that being said, I don&#x
Scripting CAs are generally considered more brittle than any other kind of
CA, so they are not as preferred, IMO.
However, that being said, I don't think that adding a Python script
interpreter would be a terrible burden. I wouldn't make it part of the
distribution, but you should be able to easi
You have a boolean operator right in that very example... I'm just winging
this, but try:
On Wed, Jul 1, 2009 at 12:21 AM, sandun css wrote:
> Hi,
>
> I have some conditions in my msi, like the following,
>
>
>
>
>
>
>
>
> But I need to run these conditions only if a certain parameter
was installed.
> Are there ways to see if MMC 3.0 is installed on the operating systems
> that don't come with it?
>
> Brant Gurganus
> http://gurganus.name/brant
>
>
>
> On Sun, Jun 28, 2009 at 10:43 PM, Christopher
> Karper wrote:
> > You'll need to fol
You'll need to follow the manual registration process, and build the
registry entries yourself. There is no extension to handle this as-is. A
search on MSDN should get you the results you need, depending on the
platform you used to develop the snap in.
Heat may be able to harvest the registry in
IMO, you should do this as a build step before packaging with WiX. It's
trivial to accomplish with MSBuild and the MSBuild Community Tasks.
Chris
On Mon, Jun 15, 2009 at 8:26 PM, Pankaj Agrawal (Infosys Technologies Ltd) <
v-pa...@microsoft.com> wrote:
> Just to correct my query I don't want to
no help.
Thanks for your time. :-)
Chris
On Sat, Jun 6, 2009 at 12:13 AM, Rob Mensching wrote:
> The error message should tell you the source line number. What version
> of the WiX toolset are you using? Is there more to the error message?
>
> Christopher Karper wrote:
> > err
error LGHT0311: A string was provided which doesn't match the specified
database codepage '1252'. Either set your database codepage to match these
characters, or change these characters to ones that exist in the database's
codepage.
How do I find the non compliant string? The error points to the
Thank you for that. How do you use "MyName" though, do you use it as if it
were a property from within the merge module?
Chris
On Thu, May 28, 2009 at 10:20 AM, Antony Walmsley <
antony.sourcefo...@gmail.com> wrote:
> We do this for our merge modules :
>
> In the MSI xml, set up PropertyName wi
I've also never seen any solid instructions or advice on how to use a
configurable merge module. No one seems to actually know how.
Chris
On Wed, May 27, 2009 at 10:21 PM, Rob Mensching wrote:
> The Merge Module would need to have a public Property and you'd have to
> refer to it with its modu
Very good, I will do. Thank you for your help.
On Wed, Apr 29, 2009 at 8:45 PM, Bob Arnson wrote:
> Christopher Karper wrote:
> > I believe I am using version 3.0.4917.0... I know it's a little old
> now,
> > but I have trouble getting new software on the bui
trouble getting new software on the build server, so it's more
expedient to keep the older edition. This problem persisted through
several different versions.
On Tue, Apr 28, 2009 at 8:55 PM, Bob Arnson wrote:
> Christopher Karper wrote:
> >>
> '..\..\..\
c-key-token of the assembly reference from
> your extension to wix.dll. If you're building the extension against wix.dll
> with one key but then trying to run it with wix.dll with a different key,
> the assembly loading may succeed but the types won't resolve as the sa
fuslogvw says binding was successful.
Any ideas?
On Sat, Apr 25, 2009 at 11:32 AM, Bob Arnson wrote:
> Christopher Karper wrote:
> > 5.) I build the Installer project using the WixExtension... I get a
> candle
> > error "candle.exe(0,0): error CNDL0144: The extensio
I've been struggling with this issue for some weeks now, and I've continued
to back burner it, but can't do that anymore.
I've built a WixExtension, and use it in several installers. But I keep
running into problems with Votive / MSBuild loading the extension I've
built. I'm guessing I'm having
You don't have to permanently install it, but you need to extract it from
the binary table. It can't be used by anything until it's pulled out and
put on the file system.
Chris
On Sat, Apr 4, 2009 at 6:37 AM, Michael wrote:
> Thanks Rob Mensching,
> But, I don't want to copy this file to com
> >
> > On Fri, Apr 3, 2009 at 9:13 PM, Eric Brown (REDMOND)
> > wrote:
> >> Multiple times. It always comes back yellow. There's no tooltip to
> provide any further feedback. (Also, I've tried this with a separate dummy
> project - I get the same pr
r 3, 2009 at 1:24 PM, Eric Brown (REDMOND) <
eric.br...@microsoft.com> wrote:
> Also, there is that yellow warning icon on the project reference. I don't
> know what that means, and I can't find a reference in the documentation.
>
> -Original Message-
&g
I use spaces in my project names and project references, and they're all
fine.
I suspect his problem is something else. I'm not sure what that is, since
this exact scenario, even down to the environment seems to match.
Chris
On Fri, Apr 3, 2009 at 12:29 PM, Eric Brown (REDMOND) <
eric.br...@micr
You can use msbuild properties (such as $(Platform)) in the output file
name... However, there's an open bug against Votive that it escapes the
control characters for now. If you open the project file directly and make
your change, it works.
I use it like this today.
Chris
On Tue, Mar 31, 2009
I was under the impression that the WixPSExtension was specifically to
register power shell extensions, and wouldn't support generic MMC plugins.
I just did my registration manually. I could be wrong though, maybe things
have changed since my MMC extension installer was written.
Chris
On Tue, M
This exists now, if not through the menu... right click the project you
want to build, and choose Build.
It will only build the clicked project. You can Clean and Rebuild this way
as well.
Chris
On Wed, Mar 25, 2009 at 5:54 PM, Rob Mensching wrote:
> Sounds like a reasonable feature reques
window.open() is using the OM from the browser, which isn't available in
MSI. These are shell based scripts, and you'll need to look up the
reference for that, MSDN probably has all the info you'll want.
On Thu, Mar 19, 2009 at 8:39 AM, ron cooper wrote:
> Dear All,
>
> I have in .wxs file :
>
If you're using Votive, you can just omit this attribute entirely and just
use the x86/x64 configurations to build...
On Tue, Mar 17, 2009 at 9:29 AM, troy hostetter wrote:
> Getting a type mismatch on this:
>
> Win64="$(loc.Win64)"
>
> Here's the error:
>
> Error407The Component/@Win64 a
sure why it would work compared to any other method, but there
you go.
Chris
On Tue, Mar 10, 2009 at 3:06 PM, Christopher Karper <
christopher.kar...@gmail.com> wrote:
> I'm actually carrying around the native file as an embedded resource in my
> managed .dll. It deploys it d
d executes...
Then, somewhere between the end of the native function, and the return to
managed code, it blows up rundll32.exe
Not really even sure where to go next to gather more info.
Chris
On Tue, Mar 10, 2009 at 2:41 PM, Richard wrote:
>
> In article ,
> Christopher Karper writes
I have a CA written in C#, which is pInvoking a native dll that I'm
supplying. This doesn't work in an installer when I'm actually installing.
I can run a test that calls the function from outside the installer DB, and
it works fine, but when running in the context of the actual installer, I'm
g
1.) session["PropertyName"] will access the property you're looking for.
2.) Call session.DoAction("ActionName", CAData)
3.) I don't know that you can. Can't you just put that in the CAData?
Chris
On Thu, Mar 5, 2009 at 1:19 PM, mkk wrote:
>
> I have a few questions.
>
> 1. In my immediate
You can't do this from within the installer, as MSI won't allow multiple
simultaneous installations. Read up on Bootstrappers, that will get you
what you need.
Chris
On Fri, Feb 27, 2009 at 6:36 AM, Prabhakaran Paulraj <
prabhakaran_paul...@dynamicbi.com> wrote:
> Hi Everyone,
>
> I am a newbie
I've been using the MessageBox / Attach method, and that has been working
fine for me. I'm using a release that's 2-3 weeks old, but no issues here.
Chris
On Wed, Feb 25, 2009 at 4:26 PM, Christopher Painter <
chr...@deploymentengineering.com> wrote:
>
> Is anyone having problems having trouble
I didn't think there was going to be a guaranteed dependency on the
framework. Won't VS2010 still be able to build native code applications?
Chris
On Thu, Feb 12, 2009 at 9:44 AM, Christopher Painter <
chr...@deploymentengineering.com> wrote:
> Personally, I'd rather see a full blown extensible
her.
>
> Feel free to open a feature request to have them added, that way it won't
> be forgotten.
>
> -Original Message-
> From: Christopher Karper [mailto:christopher.kar...@gmail.com]
> Sent: Tuesday, February 10, 2009 12:15
> To: General discussion for Window
l Message-
> From: Christopher Karper [mailto:christopher.kar...@gmail.com]
> Sent: Tuesday, February 10, 2009 11:41
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] CA Tools distro
>
> Why aren't the the tools used for CA creation distributed
Why aren't the the tools used for CA creation distributed in the binaries
release?
I always have trouble building from source, and I can't use the signed
version, but I need to use the MSBuild tasks, etc.
Is there a reason why these can't be added in the SDK folders?
Chris
--
x64 or x86 appropriately and map it to the *SAME*
> binary file. I can do this because my binaries are platform agnostic.
>
> I was hoping there was something easier however.
>
>
> --Peter
>
> -Original Message-
> From: Christopher Karper [mailto:christopher.kar...@g
MSI requires that the installer be marked as 32-bit or 64-bit.I just
made one WXS file that will work for both, then I set my target directory to
the correct place for that platform.
Chris
On Tue, Jan 27, 2009 at 3:09 PM, Peter Oehlert <
poehl...@securityinnovation.com> wrote:
> I'm doing du
I'm just starting the localization stuff, so I'll take whatever
reccomendation you have. Is the MUI pack stuff supported by WiX in any
way, or do I just need to go google up info on that as a seperate tech?
Chris
On Thu, Jan 22, 2009 at 8:55 PM, Bob Arnson wrote:
> Christopher
I've read through the help and my list archive, and I'm a little stuck.
It seems to me that there are 2 approaches to building localized
installers...
1.) Build an installer for each supported culture-language.. This is what
Votive defaults to when you add .wxl files.
2.) Build a language neutra
Can you use the uninstall string to run Windows Installer in non basic mode?
On Tue, Jan 13, 2009 at 1:32 PM, Richard wrote:
>
> In article <
> de33023b477fe44eaa71983f5279f6ce50fc39e...@na-exmsg-c102.redmond.corp.microsoft.com
> >,
> Rob Mensching writes:
>
> > Nope, ARP runs the Windows
Double post and ignore the replies?Stay classy, Rishi...
On Mon, Jan 12, 2009 at 2:37 PM, wrote:
>
> Hi
>
> I am new to Wix and would like to know the advantages it has over visual
> studio windows installer.
>
> Thanks in advance.
>
>
> Rishi
>
>
>
> This e-mail and any files transmitted wi
L Strings
> Action ended 12:46:12: ExecuteSqlStrings. Return value 1.
> Action ended 12:46:12: InstallSqlData. Return value 1.
> ...
>
> And, as you can see, the value passed to the deferred action is still
> SqlMasterDB, not SqlMasterDBAuth.
> Hence, I can see my DBs being att
You're not using SqlString items to do these?SqlScript doesn't format.
Chris
On Tue, Dec 16, 2008 at 6:40 PM, Kevin Fischer
wrote:
>
> I'm already using SqlScript elements to load them as a file.
>
> Kevin> Date: Tue, 16 Dec 2008 18:23:30 -0500> From:
> christopher.kar...@gmail.com> To: wix-
You either need to load them as SqlScript elements from a file, or escape
the square brackets according to Formatted String rules. I think it's [\[]
and [\]], but you'll want to double check that.
Or, you could always wing it, and just run without brackets. You may find
it works just fine.
Chr
At the bottom of *ever single message* is this link:
https://lists.sourceforge.net/lists/listinfo/wix-users
Go there, look at the area under "*WiX-users Subscribers*" and you can
unsubscribe...
Chris
On Tue, Dec 16, 2008 at 4:27 PM, Sangeetha Haudakari (Excell Data
Corporation) wrote:
> I want
This is a little crazy, so I'll try to be as clear as possible...
Here's the pertinent section of my DB installer:
USESQLAUTH=1
First, I create a User entity using the possibly supplied properties. Then
I cre
Which version of the .NET runtime are you using? Make sure you're not
running under 3.0 or newer for Windows 2000.
Chris
On Thu, Dec 4, 2008 at 3:22 PM, hegsie <[EMAIL PROTECTED]> wrote:
>
> Hi I have a couple of C# custom actions written in wix v3, they seem to
> work
> fine when they are run
Derr, sorry, this was supposed to be just to Rob. :-D
Chris
On Wed, Nov 19, 2008 at 2:26 PM, Christopher Karper <
[EMAIL PROTECTED]> wrote:
> Heya Rob,
> I asked once before, but I guess I got lost in the crush... I have
> improvements to submit, where should I send them?
&g
Heya Rob,
I asked once before, but I guess I got lost in the crush... I have
improvements to submit, where should I send them?
I've added some things to heat, and I'd be willing to muck around in there a
bit more if there are any serious issues pending. I also would like to make
some changes to
I will help you.
Chris
On Wed, Nov 19, 2008 at 2:12 PM, Eitan Behar <[EMAIL PROTECTED]> wrote:
> Well, not good, not good, what would u suggest? A bright idea might save my
> day
>
>
> -Original Message-
> From: Rob Mensching [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 19,
: [WiX-users] Debugging a DTF Managed Custom Action
>
> What I did when debugging some of my DTF code was put a call to
> Debugger.Launch() right at the beginning of my custom action. At that
> point, I could easily attach and step through the code with the debugger.
>
>
There is a way using Environment variables to set a breakpoint, but I've
found that to be more trouble than it's worth. You can put a call at the
beginning of your CA to MessageBox.Show, and then when that pops up, you can
attach to the process then. Make sure you attach to the CA managed
process
I don't think this is possible with MSI. The SQL Server installer does
this, but I believe that's a custom rolled deal, not using the standard
installer.
Chris
On Mon, Nov 3, 2008 at 1:07 AM, Mazin Sayid Ali <[EMAIL PROTECTED]>wrote:
> Hi
>
> I'm new to WIX. I'm trying to create a progress bar
x64 MSI which can access both 64-bit & 32-bit
> > system directories which WIN64DUALFOLDERS won't touch but as stated
> > before you will get ICE80 errors for every 32-bit directory you
> > reference.
> >
> > Why does your application have 32-bit & 64-bit compon
(at least for this product) seems to be a cleaner
> approach. Is there some gotcha I'm missing here?
>
> Christopher Karper wrote:
>
>> If you need a mixed installer, then you have to make it a 64 bit
>> installer. It doesn't make sense to install 64 bit components
If you need a mixed installer, then you have to make it a 64 bit
installer. It doesn't make sense to install 64 bit components on a 32 bit
system anyway, so just don't include those components in your 32 bit
installer, or alternately, don't offer a 32 bit installer. In some
corporate environmen
I made installer projects using Votive, then just build those as part of my
solution build. Simple and easy.
Chris
On Tue, Oct 14, 2008 at 12:41 AM, Alex Ivanoff <[EMAIL PROTECTED]>wrote:
> I wander if anyone can share their experience with building WiX projects
> with Team Build. What targets
If you are just looking for the feature to exist on disc, then you can use
two separate .wxs files to build two installers. If you want them to live
under the same application in ARP, then you're going to need to build one
.wxs file, with 2 features in it. You can set up a feature to not be
visi
The 3.0 and 3.5 framework versions use the 2.0 runtime. They're just
library and syntax additions. I would suggest trying to reinstall the v2 of
NetFx, then reinstall Wix 3.
I don't know for sure what's causing it, or if that will fix it, but it'd be
a great first shot since you're apparently ha
lement?
>
> Thanks,
> Ravit
> -Original Message-
> From: Christopher Karper [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 25, 2008 6:25 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] how to use WIX write registry values t
You shouldn't directly access the Wow6432Node, just set up your registry
access like a 32 bit program would expect, then mark the component
containing those registry items as Is64Bit="No"...
That should set you up.
Chris
On Thu, Sep 25, 2008 at 5:13 AM, Ravit Shapira <
[EMAIL PROTECTED]> wrote:
s, I have added Platfrom attribte as
> x64 and in Component , added one attribute Win64='yes'. But it is giving
> error as mentioned below.
>
> An unexpected Win32 exception with error code 0x654 occurred:
>
> Please help.
>
> Regards
> Sandeep
>
>
> -Or
Sandeep
>
> -----Original Message-
> From: Christopher Karper [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 24, 2008 12:20 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Registey Key Issue
>
> If you create a 32 bit insta
If you create a 32 bit installer, it will run in the 32 bit space, which can
not access outside the Wow6432Node...
If you need to write outside of that area, you'll need to create a seperate
installer for a 64-bit version, and mark the component that contains your
registry edits as a 64-bit compon
In all likelihood, your problem is that your CA is being modularized when
compiled, but maybe not to the standard you're expecting. If you look at
your .msm in Orca, you'll see the actual name it's been given. I believe
you can suppress the modularization if that's your wish. Or you can at
leas
This will allow you to have one installer definition, but not a single
installer. You will still need to build for 32-bit and 64-bit version of
the MSI. To the OP... Why not just make a 32 bit installer, and not
restrict it if you don't care which platform you're installing to. a 32 bit
instal
e:
> That's not what I am trying to accomplish. I need a list of all
> properties available during an immediate CA. I don't know the property
> names ahead of time. Thx.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
>
The way I handled this for my DBScript piece was to load the file into a
temporary table in an immediate action, then use the table entries in the
deferred CA. By loading the file immediately, you have access to all the
properties, and can store it post-process. Then your deferred action can
use
If you are going to use a hybrid approach, then merge modules will get you
what you want. If you can implement Wi across the board, then you should
use .wixlibs. They're much better for your mental health, and more capable
to boot.
Give us more information, and there are plenty of people here wh
You'll need to copy the UI code from the extension and customize it yourself
in your project. You don't need to rebuild the extension, just stop using
it, and code the UI yourself.
Chris
On Thu, Aug 28, 2008 at 7:58 AM, Sean Farrow
<[EMAIL PROTECTED]>wrote:
> Hi:
> I need to delete the start me
> I think there may be something wrong with my machine. Maybe some mixed
> paths. I'll try to build wix from source and debug heat to get that
> exception.
>
> Will post the results if anything useful shows up.
>
> Thanks,
>
> Pedro
>
> On Tue, Aug 26, 2008 a
It's implemented, but any error in building your solution will make the
project harvester fail and pretty well hide the info. Try just running
msbuild from the command line on the file you're trying to harvest, and make
sure you clear out any errors from there. If your projects require
variable
m
> pissing about with C++ (although I'd prefer to avoid that :P)
>
> Sorry if I'm asking obvious questions - I'm new to Wix, and I couldn't find
> much documentation on v3.
>
> Cheers,
> Adam
>
> -Original Message-
> From: [EMAIL PROTECTED]
I see this question a lot out here, and this was actually the very first
thing that brought me to this group. There is nothing built in to
facilitate this, and you will need to use a CA to get it done. However,
since so many people have implemented it before, you may be able to find
something ou
n
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
> Karper
> Sent: Monday, August 11, 2008 8:10 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Dynamically naming a
how to assign SqlString explicit scripts, and not reading the
> scripts from a .sql file in the Binary table.
>
> Thanks in advance,
>
> Eitan
>
>
>
> On Fri, Aug 8, 2008 at 12:40 AM, Christopher Karper <
> [EMAIL PROTECTED]> wrote:
>
> > There is not any
As long as your entire organization is using Wix to build their
deployments.
Chris
On Mon, Aug 11, 2008 at 1:22 AM, Blair Murri <[EMAIL PROTECTED]> wrote:
> I don't know if anyone has mentioned this already, but the Windows
> Installer team has been trying to deprecate Merge Modules almost ever
You'll probably want to include both controls on the form, and just
show/hide based on the radio box selection. That would be much easier than
trying to load new text into the box, IMO.
Chris
On Fri, Aug 8, 2008 at 8:38 PM, Alireza Keyvani <[EMAIL PROTECTED]>wrote:
> Hi everyone,
>
>
>
> Wix be
I don't think so. Changing the usual behavior of the UI is generally
considered poor practice. If something looks like an editable textbox, it
*should* be an editable textbox.
Chris
On Fri, Aug 8, 2008 at 11:19 AM, Roger Yen <[EMAIL PROTECTED]> wrote:
> Hello,
>
>
>
> I've been wanting to ask
There is not anything built in to Wix right now that will let you use
variables in SqlScripts. You can load them into SqlString elements and use
the normal [property] syntax.
You can build a CA that will do this as well, which is what I did.
Good luck!
Chris
On Thu, Aug 7, 2008 at 5:01 PM, Nic
Wix v4? Did I miss something?
On Wed, Aug 6, 2008 at 12:07 PM, Neil Sleightholm <[EMAIL PROTECTED]>wrote:
> I don't believe the element supports formatted strings, if
> you are using WiX v4 try using the element. Otherwise you
> will need to do it with a custom action.
>
> Neil
>
> -Origin
I use the regex search and replace too. Which harvester are you using? I
can take a look to see how hard it would be to add support for that, but as
far as I know, these things are not currently possible, and no one is
working on heat other than myself.
Chris
On Wed, Aug 6, 2008 at 12:01 PM,
modularization. Do you mean
> something like this?:
>
>
>
> On Tue, Aug 5, 2008 at 4:45 PM, Christopher Karper <
> [EMAIL PROTECTED]> wrote:
>
> > You're probably facing the same issue I did.. There's currently a bug
> that
> > binder variables need t
You're probably facing the same issue I did.. There's currently a bug that
binder variables need the fully modularized id in merge modules. I don't
know if there's a way to pass this in to SnapIn extension, but you can try
modularizing the file key yourself as a workaround.
Chris
On Tue, Aug 5,
L PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Christopher Karper
> Sent: Thursday, July 31, 2008 19:48
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Binder variables from Votive
>
> It's in the merge module itself. I would have
Yeah, you can do it. You'll have to manually create your tasks and schedule
them in each of your project files. That's essentially duplicating what's
int he project files for Votive. I would say, even though it's going to be
some work, you'd still be better served by building Votive projects and
It's in the merge module itself. I would have expected it to get
modularized like all of my other file/component references, but alas,
alack... it was not to be.
Chris
On Thu, Jul 31, 2008 at 5:40 PM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Christopher Karper wrote:
> >
uot;$(var.UPGRADE_CODE)"
> Version="!(bind.FileVersion.foo.exe)">
>
> Can you verify whether that works for you?
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Christopher Karper
> Sent: Thursda
3.0.4325
On Thu, Jul 31, 2008 at 1:51 PM, Rob Mensching
<[EMAIL PROTECTED]>wrote:
> What version of the WiX toolset?
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Christopher Karper
> Sent: Thursday, July 31,
Bob Arnson <[EMAIL PROTECTED]> wrote:
> Christopher Karper wrote:
> > I still can't get any of these binder variables to work. Does anyone
> have
> > some time to take a look at it? Thanks in advance. :-D
> >
>
> Two random things to try:
>
> 1. Rename the
I just subscribe and use gmail to sort mine. :-)
I think a lot of people here use Nabble, maybe you'd have better luck with
that?
Chris
On Thu, Jul 31, 2008 at 11:08 AM, Zane Zeeh <[EMAIL PROTECTED]> wrote:
> Is there some secret to searching through the wix-users mail archive? I get
> no resu
InstallUtil is a DLL that uses the installer classes compiled into your
managed service. So, none of the service deployment information is going to
be in the file generated by dark. You will have to look up the
ServiceInstall element, and enter the same information you have in the self
installer.
Other installers won't use the same CustomAction to install the service. I
know the ones emitted by the VS deployments use InstallUtil to self
register. You'll need to kind of "translate" the decompiled .wxs into Wix
speak.
And I wouldn't see why you'd need two different files for the deploymen
to the root
> of it.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Christopher Karper
> Sent: Thursday, July 24, 2008 14:12
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Binder va
Use the Win64="no" attribute on the containing Component.
Chris
On Mon, Jul 28, 2008 at 3:29 PM, Nilkund Aseef <
[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a requirement that my 64 bit msi should create registry entries on
> the Wow6432Node.
>
> In my wix file, I have the following logic
>
>
OK, so I fixed the problem with the heat project harvester. How do I submit
these changes to you Wix fellows for review and possible inclusion?
Chris
On Fri, Jul 25, 2008 at 3:37 PM, Christopher Karper <
[EMAIL PROTECTED]> wrote:
> Actually, I'm looking at it right now. The p
something ) for quite a while now.
>
>
> -----Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Christopher Karper
> Sent: Friday, July 25, 2008 10:06
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] De
.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Christopher Karper
> Sent: Friday, July 25, 2008 08:56
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Dependency Management
>
> This is
This is a source of lots of hot discussion on the list right now. There is
nothing that can automatically manage things for you the way you would be
used to with Visual Studio. The Windows Installer is a mighty finicky
beasty, and adhering to all of it's rules makes development such a thing a
ver
ng <[EMAIL PROTECTED]>
wrote:
> More likely than not, your "FileId" is wrong. A bug is open on the fact
> that the binder doesn't fail when it hits an unknown binder variable.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED]
1 - 100 of 185 matches
Mail list logo
