We have no plans to use
WiX v3.0 for production until next year. It won’t affect us if you switch
to v2.0 now. When we switch to WiX v3.0 it won’t be a problem to switch
to .Net 2.0 at the same time.
IMHO WiX 3.0 is not
production-ready anyway, but the closer you get to finish it, the
dangle123 ... wrote:
>
> How do I rollback an immediate (not deferred) custom action?
>
You don't. Immediate CAs shouldn't change the system, so there's nothing
to roll back.
--
sig://boB
http://bobs.org
___
WiX-users mailing list
WiX-users@lists.so
Don Tasanasanta wrote:
i have tried creating a simple
one file install that installs to appdata only and has no registry
entries but i can't get it to install with user only access. i keep
getting the same error:
"This installation is forbidden
by system policy. Contact your
I have posted this before on the WiX-users
list before, but got only one response and it was from Rob M. who
basically said that he'd like to do it but didn't think he could. Is
there anyone who is or knows of a consultant that my group can hire to
review my setup design? This is the first MSI base
How do I rollback an immediate (not deferred) custom action?
Thanks,
---Leo
From: "dangle123 ..." <[EMAIL PROTECTED]>To: wix-users@lists.sourceforge.netSubject: [WiX-users] Determine if in rollback mode from non-deferred customaction.Date: Thu, 15 Jun 2006 17:34:10 -0700MIME-Version: 1.0X-Origina
How do I check from a non-deferred custom action that an install/uninstall was rolled back?
Thanks,
--Leo
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
i have tried creating a simple one file install that
installs to appdata only and has no registry entries but i can't get it to
install with user only access. i keep getting the same
error:
"This installation is forbidden by system policy. Contact
your system administrator."
so i was won
Right now, Rob is fixing the warnings that
make ClickThrough really painful to use. These were a result of recent
schema changes. It’s some pretty exciting changes because
ClickThrough will utilize the same infrastructure as Heat. I expect the
innovation in this area to flourish once all
i've created a one
file ClickThrough install and generated the wix file associated with
it.
i'm wondering...
what exactly makes this a per-user install?
i was unable to run
the ClickThrough install due to compile errors but the wix file came out fine.
__
Don Tas
John, thanks for your comments. This
is kind of the same thought that some of us had. In reality, there’s not
a huge benefit to moving to 2.0. We wanted to do it mainly to have a consistent
build environment for our tools. Votive for the 3.0 branch will be exclusively
.NET 2.0 targeting VS
Works like a champ now! I believe I
just needed the encoding and codepage set in all the WXS files in the project for
this to work. I did take out the explicit setting of SummaryCodepage per your
recommendation also.
Your help and expertise is much
appreciated Derek!
Jon
Title: Re: [WiX-users] change install location based on privledge
Don,
You can set the Directory property using a type 51 custom
action.
You can then condition the execution of the custom action based on your
AdminUser.
Michael
-Original Message- From:
[EMAIL PROTEC
I know that directory ids can be treated like properties and I know how
to detect AdminUser
My problem is how to write the conditional that will assign my install
directory accordingly based on AdminUser.
Do I add a conditional to the directory tag?
Try to set a property with the property tag? If
Realistically, if Wix 3.0 was moved to .NET 2.0, it could still be used to
build installers for .NET 1.1 application correct? In this case, I don't think
that there would be much of an impact to any of the projects that I develop
installers for. I guess that I could also continue to use Wix 2.
I think it’s very nice that candle/light/etc
now run on either.
We too develop apps that must run on
either so we have some dev boxes that only have 1.1 on them.
Naturally this includes the automated build
servers which only have 1.1 and VS2003 on them to ensure no code references 2.0
cla
(H Y W I . P K)- H o l l y w o o d I n t e r m e d i a t e, Inc.
We Strongly believe in this companies Performance, with its 5th stright day of
climb
This one did very well during last mar keting campa ign. Very Well!
See Hot NEWS Just released
As we mentioned yesterday
S Y M B O L : H_Y_W_
Hi
Since we are using Visual Studio 2005 the .NET Framework 2.0 is
automaticaly installed. So there will be no problem for us.
Stefan
Justin Rockwood wrote:
> There has been some talk on the core team about moving Wix 3.0 over to use
> the .NET Framework 2.0 instead of 1.1. We wanted to know how
We're using v2.0.3719.0 right now and have no problems so far which require us
to update. We will eventually use WiX 3.0, but not in production this year. We
currently use Votive v2 just to have intellisense for editing WiX files. I
haven't tried Votive v3 yet.
The core v2 toolset and UI lib ar
Thanks for the all replies!
I have tested my installation on a clear VM and uninstallation was
complete. Seems my development machine is "dirty" and that was the
reason of incomplete uninstall.
Best regards,
Peter G. Sakhno
C-MAP RUSSIA Ltd
http://www.c-map.ru/
__
You can treat Directory Ids like properties if they are all in uppercase. You
can detect the
privilege level early on in the sequence and then set your product directory to
an appropriate path.
All sub-directories will get resolved as you'd expect.
Rob
Don Tasanasanta wrote:
> I would like
20 matches
Mail list logo
