Hi,
I have some CA that executed during uninstall (just before
RemoveFiles action). My custom action need to know folder where
component was installed. The problem that
session.Format([$component]) return me empty string. (on
installation phase it contain full path to folder where component
Sorry for the delay in replying to this. I'm still working through a couple of
issues before I can give a definite answer.
Cheers,
Jeff
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: 05 August 2008 15:11
To: General discussion for
Hi all,
I have an app which includes a printer driver which means it needs admin
access to install. As it is a printer driver it can only really be
considered a 'per machine' setup as anyone could print to it.
When someone uses the printer driver it creates a per user configuration
file in
http://robmensching.com/blog/archive/2007/04/19.aspx
The above blog tells us that one of the reasons not to use managed code
for DLL CAs is because .NET Framework version 1.1 is always loaded on
Windows Server 2003 regardless of the code's required .NET version. I
know that DTF addresses the
Hello,
I've been wanting to ask this question for awhile, is there any way to
lock text boxes in wix and not make it disabled, ie. the words in it
gets grayed out and I don't want that, I really just want an un-editable
text box that gets a text path from a custom action?
Using a sunken
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 this
Ryan O'Neill wrote:
When I uninstall the app I would like to offer the option to clean these up,
so I guess the uninstall from control panel needs an elevated bootstrapper
(I'll have to look this up) as it would need to enumerate all users and
delete their AppData\MyProduct directories.
Dmitry Berkovich wrote:
The problem that
session.Format([$component]) return me empty string. (on
installation phase it contain full path to folder where component
installed).
Question : what can I do that my CA on uninstall stage will receive
the full path of folder where component
Evans, Jim wrote:
What are some of the best practices for authoring the installation of
COM components? Obviously, I know selfreg is evil. When it comes to the
registration of COM components, should you author the registry entries
within the same Windows Installer component, or as separate
Roger Yen wrote:
I've been wanting to ask this question for awhile, is there any way to
lock text boxes in wix and not make it disabled, ie. the words in it
gets grayed out and I don't want that, I really just want an un-editable
text box that gets a text path from a custom action?
MSI
You could also use Active Setup to run a tidy-up script for each user.
Take a look at http://www.appdeploy.com/articles/activesetup.asp, the
structure you'd use is the same though you won't be able to use an MSI
command line as the MSI is already uninstalled.
Cheers,
James
-Original
Bob's answer of 'don't bother' seemed more suitable, it being Friday and
just gone five PM!
Thanks chaps.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Buddell, James
Sent: 08 August 2008 17:03
To: General discussion for Windows Installer XML toolset.
MarkZune wrote:
I'm creating a user (ServiceUser) as well as specific folder permissions
during my install for ServiceUser. When I run the uninstall though,
ServiceUser is removed, but it appears the permissions that I've created
for ServiceUser are still there.
How are you creating the
Hi boB,
It happed NOT in defered CA.
Dima
On Fri, Aug 8, 2008 at 6:44 PM, Bob Arnson [EMAIL PROTECTED] wrote:
Dmitry Berkovich wrote:
The problem that
session.Format([$component]) return me empty string. (on
installation phase it contain full path to folder where component
installed).
Mat wrote:
I've been running into a problem which I haven't been able to solve
related to vista and uninstalling. I have a package which is set to
install per-machine and elevated, which requires the user to be
administrator to install the package. Under windows vista when the user
is the
Shawn Dwyer wrote:
I'm now in the process of creating our first patch, but unfortunately when I
uninstall the patch this message is being shown and the patch fails to
uninstall. I am able to uninstall the full product which removes the patch
with it.
Uninstalling a patch runs a repair of
I use one of my main installed folders and go back one level to get the
root. All installed folders become public properties (property name the
same as folder Id) available also during the uninstall if not in
deferred CA.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
I use one of my main installed folders and go back one level to get the
root. All installed folders become public properties (property name the
same as folder Id) available also during the uninstall if not in
deferred CA.
-Original Message-
From: Dmitry Berkovich [mailto:[EMAIL
Bob Arnson-6 wrote:
How are you creating the permissions?
I'm using the PermissionEx element. The [MY_PATH] folder already exists
before the install occurs. I'm also adding fileshare permissions to the same
folder. Source snippet is below:
util:Group Id=UsersGroup Name=Users/
Directory
Dmitry,
Does description below applies to your situation (from
http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx)?
Note that if a component is already installed, and is not reinstalled,
removed, or moved during the current installation, the action state of the
component is null and
Yes. DTF runs each managed custom action in its own dedicated process. Because
the process is separate and new, there is no risk of some other CLR version
already being loaded into it. Only an unmanaged stub runs in the MSI custom
action server process -- that stub coordinates the launch of the
Alex,
This is exactly what happened, my component was installed and going
to be unsiatlled. The problem that my CA need now folder where
component was installed.
I am looking the way to detect it.
Thanks,
Dima
On Fri, Aug 8, 2008 at 8:01 PM, Alexander Shevchuk
[EMAIL PROTECTED] wrote:
I'm pretty sure this has been asked on the list before, but searching
didn't yield a definitive answer for me. In my current project, I'm
working on migrating our current installer to using MSI via WiX, and I
thought I'd try WiX v3. In the project, I have several COM components
that were written
What log is saying about your component? Specifically,
Installed/Request/Action values.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dmitry Berkovich
Sent: Friday, August 08, 2008 10:20 AM
To: General discussion for Windows Installer XML toolset.
Alex,
CurrentState = Local
RequestState = Absent
Dima
On Fri, Aug 8, 2008 at 8:27 PM, Alexander Shevchuk
[EMAIL PROTECTED] wrote:
What log is saying about your component? Specifically,
Installed/Request/Action values.
-Original Message-
From: [EMAIL PROTECTED]
I am using condition NOT PATCH to change the text in UI to say Patch
instead of Repair when patch is applied. That works just fine.
Now I want to avoid installing one Registry component during patch
application but not during the repair. I used the same condition (i.e.
NOT PATCH rather than NOT
I am going to use suggestion of Tony (session.Format([directory]).
Its works on install and uninstall stages.
Dima
P.S - Tony thanks
On Fri, Aug 8, 2008 at 8:53 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote:
Alex,
CurrentState = Local
RequestState = Absent
Dima
On Fri, Aug 8, 2008 at
I have a problem where I am specifying a registry entry in a component that
writes out the INSTALLDIR property to the registry. My problem is that
patches to this MSI always reset the INSTALLDIR to the default value (the
Windows Installer default is C:\Program Files)
I need to either A) find a
I tried adding Transitive attribute to the registry component and that
deleted the component when patch was applied. Thus 'NOT PATCH' is a
correct condition since transitive components are removed when condition
changes from true to false.
However, for some reason that I would really love
Hi everyone,
Wix beginner here! I'm trying to customize the license agreement dialogbox
(LicenseAgreementDlg.wxs) in order to add a control (a combo box for
example) that lets the user choose the language in which the license
agreement is displayed (most probably English or French). So I'm
You've got a ton of options available to you; since I don't know the details of
your installation, I'll try to give you a couple options (pick one [or
something similar, or perhaps a hybrid] that makes the most sense for your
situation). If none of the below work for you, holler and I'll try
You can always use custom action to write that part of the Registry.
However that would not be politically correct. I mean, using CA when MSI
database solution is available. Unfortunately sometimes it appears as if MSI
people do everything they can to force us to use CAs even in cases which
I believe REINSTALLMODE comes into play here.
Ref: http://msdn.microsoft.com/en-us/library/aa371182(VS.85).aspx
So, in your first post, you had a non-transitive component installing a
registry key conditioned on NOT PATCH. Assuming your installation wasn't
slipstreaming (applying a
I'm writing an installer for a Visual Studio add-in which requires me to
place a file in %USERPROFILE%\Visual Studio 2005\Addins or
%USERPROFILE%\Visual Studio 2008\Addins depending on the Visual Studio
version I'm installing for. If this directory doesn't exist, it should
be created, but on
I have two questions about WixVSExtension:
1. Can you use VSTF2005_SP_LEVEL as a Boolean variable to
determine if Team Foundation Client 2005 is installed at all, regardless
of its service pack level?
2. Is there an equivalent to determine if Team Foundation Client
2008 is
35 matches
Mail list logo
