My GAC assembly contains user registration information and I don't want this
information to be lost even if the program is uninstalled.
--
View this message in context:
http://www.nabble.com/Permanent-assembly-in-GAC-tf1904577.html#a5264263
Sent from the wix-devs forum at Nabble.com.
It sounds like a good
thing to support somehow. I'm not sure that looking for a random
property, is a good way to go about it. Can you open a bug on Source
Forge to track the issue, so we don't lose it?
After that, we have
this problem in a few places where pieces of data need to be
c
Interesting, I don't know anything about that kind of set up. I'll have to
look into it.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Monday, July 10, 2006 6:55 PM
To: [EMAIL PROTECTED]
Cc: Albert van Peppen; Wix-Devs; wix-users@lists.
Rob Mensching wrote:
> [robmen] I truly hope it won't come to that. Creating a separate project
> would essentially fork the development of the WiX toolset.
It shouldn't. I assume Frederik was talking about something like the
NAnt-Contrib project. It serves the same purpose as an incubator or l
> I'd love to be able to contribute to WiX (in particular
> MSBuild support and Votive) but the hoop-jumping
> required to complete the assignment agreement totally
> put me off.
I know what you are saying here. The assignment agreement has been
something I've been arguing against since the begi
> I think it would be worth creating a space where people
> can contribute their own additions to WiX that are of
> signification value but did not make it through the legal
> process. A WiX-contrib project, or something like that.
[robmen] I truly hope it won't come to that. Creating a separat
Rob,
I'd love to be able to contribute to WiX (in particular MSBuild support
and Votive) but the hoop-jumping required to complete the assignment
agreement totally put me off.
Why the requirement for us to print off and post a piece of paper to
Microsoft? All other open source projects I've work
Frederik Carlier wrote:
> I think it would be worth creating a space where people can contribute
> their own additions to WiX that are of signification value but did not
> make it through the legal process. A WiX-contrib project, or something
> like that.
>
So go ahead and create it.
> I still
I think it would be worth creating a space where people can contribute
their own additions to WiX that are of signification value but did not
make it through the legal process. A WiX-contrib project, or something
like that.
I still think the "single copyright owner" argument is void; anyone is
fre
Currently, the database custom actions have the option to connect using Integrated Authentication or SQL Server Authentication. The way the choice is made is determined is based on the presence of a SQLUser tag within the SQLDatabase tag.
Our UI allows the user to choose between the two, settin
Can you give a little more information about your requirements? The things
that you're suggesting here break component rules and you should really not
be doing them. The GAC is versioned, so it's possible to install more than
one version of the assembly to the GAC. If the assembly was installed to
1. I suggest
removing the Sequence numbers. Use Before/After attributes instead.
2. I believe
that AppSearch is scheduled before LaunchConditions today. I don't think
you need to sequence them or specify Overridable. If my memory is
incorrect, you can simply say "AppSearch Before
Adding wix-users to this topic – I just
noticed it was sent to wix-devs. Please only use wix-devs for discussions
of code and other internals of the WiX toolset, all discussion about using the
toolset should go to wix-users.
It’s not necessary to have this
authoring:
The reason we wanted this functionality is because we are
trying to create wixlibs that are very specific. So for example, I've got
a wixlib and all it does is check to see if the target machine has some other
application installed on it. So here is that wxs file:
I see the problem now. Since the
AppSearch action is a standard action – the wix toolset defines the
overridable sequencing for the action. You can’t specify
Overridable=”yes” because its already been declared. You can
override the standard sequencing already though, so setting the attri
3.0.1828.0 (it's in the subject of the
email).
From: Derek Cicerone
[mailto:[EMAIL PROTECTED] Sent: Monday, July 10, 2006
1:03 PMTo: Wilson, Brad;
wix-devs@lists.sourceforge.netSubject: RE: [WiX-devs] WiX v3.0.1828.0
Overridable attribute causing buildbreak.
What version of
candle/WiX
What version of candle/WiX are you using?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Brad
Sent: Monday, July 10, 2006 9:09
AM
To: wix-devs@lists.sourceforge.net
Subject: [WiX-devs] WiX
v3.0.1828.0 Overridable attribute causing buildbreak.
I'm
First, if you have a patch to the code, please start the discussion on the
wix-devs mailing list about that patch. There should be no confusion about
that. We talk about the code on wix-devs.
Now, Pedrum is still waiting for an answer for his last patch... but I'll
get to that (hopefully, this
I'm trying to use
the overridable attribute in some WixLibs that i've created but when trying to
do so, I am receiving the following error at candle time:
candle.exe -nologo -w3 -v0 -dReleaseBuild=Yes ..\ca_ICServerCheck.wxs
-ext "ININ.WiXExtensions.I3WiXExtensions,
ININ.WiXExtensions"
..\
Bugs item #1519658, was opened at 2006-07-09 22:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1519658&group_id=105970
Please note that this message will contain a full copy
I agree I don't mind sacrificing my own rights, but I can't really speak for my employer...On 7/10/06, Albert van Peppen <
[EMAIL PROTECTED]> wrote:Same here; all my work is property of the company I work for. But it is possible for me to donate my bugfixes/enhangements back to the community un
Same here; all my work is property of the company I work for. But it is
possible for me to donate my bugfixes/enhangements back to the community under
strict guidelines.
So, on to of that there is this agreement.
Nonetheless I think it would be far more easier for a lot of people if they got
a
22 matches
Mail list logo
