microsoft.public.windows.msi Google Group

Re: Custom Action to Restart an App.

ph...@wonderware.nospam.com (Wilson, Phil) — Mon, 08 Mrz. 2010 18:12:45 UT

I don't think that helps. The repair is initiated when you (for example) use
a shortcut, and it happens before your app even starts. Do you really need
those HKCU registry items for a per-machine install?

Re: Custom Action Condition - AllUsers vs NOT REINSTALL...

ph...@wonderware.nospam.com (Wilson, Phil) — Mon, 08 Mrz. 2010 18:09:05 UT

Have a condition of Not Installed on your custom actions, then they run only
on first install.

Re: Custom Action to Restart an App.

fyodor...@gmail.com (Fyodor Koryazhkin) — Sat, 06 Mrz. 2010 14:37:37 UT

Hi,
I guess it will be quite difficult to distinguish between regular
maintenance mode and your case where the maintenance mode is initiated
by msiexec service or application. Moreover killing application from
outside is not a good practice since some user data may be lost.
I think that you should revise the way your application is installed.

Custom Action to Restart an App.

mawa...@rcn.com (Superfreak3) — Fri, 05 Mrz. 2010 22:08:08 UT

Hi all,
Our app requires an Admin to install, but when a Standard User
attempts to launch our app., Windows Installer repair is initiated to
write some HKCU keys, etc.
What I need to do is, during this repair as a Standard User, kill the
app that was initiated to start the repair and restart it.
First, I'm wondering if I'm going to be able to do this in User

Re: Custom Action Condition - AllUsers vs NOT REINSTALL...

mawa...@rcn.com (Superfreak3) — Fri, 05 Mrz. 2010 15:41:22 UT

Oh, I think OK. After checking my script I see that the action I was
concerned about is wrapped in a NOT PATCH block so it isn't currently
set to run during a patch.

Re: Custom Action Condition - AllUsers vs NOT REINSTALL...

mawa...@rcn.com (Superfreak3) — Fri, 05 Mrz. 2010 15:26:07 UT

Can't quite remember, but I think they were 1723. I killed the
virtual image I was testing on so I can't recreate since I already
changed the install to condition NOT REINSTALL.
My only concern is that if I Patch, these actions will not run I don't
think, correct? The one action I'm not too concerned because it just

Re: Custom Action Condition - AllUsers vs NOT REINSTALL...

sebast...@instyler.com (Sebastian Brand) — Fri, 05 Mrz. 2010 07:40:16 UT

It depends on your custom actions I think. If their action is not
required in a reinstall use the NOT REINSTALL attempt.
When in repair mode, I think Privileged is handled the same way as in
first installation so that wouldn't help either.
What are the CA errors anyway?
Best regards,
Sebastian Brand

Custom Action Condition - AllUsers vs NOT REINSTALL...

mawa...@rcn.com (Superfreak3) — Thu, 04 Mrz. 2010 22:05:52 UT

Hi there,
I'm testing my install on a Windows 7 machine and we do require admin
rights to install. With that, there is no problem.
Now, when a standard user log in, some User registry keys and the like
have to be 'repaired' or placed for that user. During this repair, I'm
getting two Custom Action errors that I think are related to rights

Re: Creating .ini File in Windows 7 AllUsers Profile Area - Not seeing after install....

mawa...@rcn.com (Superfreak3) — Thu, 04 Mrz. 2010 22:05:05 UT

It created it in ProgramData!!

Creating .ini File in Windows 7 AllUsers Profile Area - Not seeing after install....

mawa...@rcn.com (Superfreak3) — Thu, 04 Mrz. 2010 20:09:22 UT

Hi all,
I'm trying to create and .ini file in the AllUsers area of Windows 7
with our application installation. We currently use a Wise product
and the .ini is set to be created in the followig location...
Windows
Profiles
All Users
Application Data
OurCompany
Our Product

Re: Custom Action DLL created with Visual Studio 2008 crashing...

ph...@wonderware.nospam.com (Wilson, Phil) — Wed, 03 Mrz. 2010 17:54:58 UT

I am guessing that hardcore originals are using a newsgroup client such as
Outlook Express, Windows Mail, or any number of other 3rd party usenet
tools. In those cases you'd write one messqage and post it to
microsoft.public.windows.msi and microsoft.public.platformsdk.m si exactly
like sending an email to multiple people. However I think that a lot of

Re: Multi instance upgrade

hclnospamal...@newsgroup.nospam (Adrian Accinelli) — Wed, 03 Mrz. 2010 16:48:06 UT

Did you try modifying the ActionProperty value so that it only has the
ProductCode of the instance you want to remove? If you do this before
RemoveExistingProducts action is scheduled it shouldn't know about the
second instance and thus not act upon it.
Sincerely,
Adrian Accinelli

Re: Custom Action DLL created with Visual Studio 2008 crashing...

mawa...@rcn.com (Superfreak3) — Wed, 03 Mrz. 2010 13:31:11 UT

On Mar 2, 12:47 pm, "Wilson, Phil" <ph...@wonderware.nospam.com>
wrote:
I'm not quite sure what that means. I try to find the relevant groups
and post to them.
How does one get around duplicate posting as I don't know who
frequents what groups?

Multi instance upgrade

fyodor...@gmail.com (Fyodor Koryazhkin) — Tue, 02 Mrz. 2010 21:30:43 UT

Hi everybody,
The MSDN documentation says that to create multi instance installation
the instance transforms that change product code should be used and
actually this should be sufficient. But following this scenario I have a
problem on major upgrade.
Let say I have two instances installed on the computer and want to

Re: Custom Action DLL created with Visual Studio 2008 crashing...

ph...@wonderware.nospam.com (Wilson, Phil) — Tue, 02 Mrz. 2010 17:47:31 UT

You should post your message once to all the relevant groups.