microsoft.public.platformsdk.msi Google Group

What can go wrong if msi installations will be patched with xcopy?

2009-11-24T18:33:45Z

Hi,
I try to use as much as possible MSI based installations for our software
products.
Now colleagues have implemented a patch tool which updates installed
products (1st install by msi) with an batch-file.
They update several files, kill running processes, stop/restart services,
execute sql scripts and register com servers with this tool.

RE: Tooltips won't show when MsiInstallProduct employed

2009-11-24T13:23:01Z

A similar problemobserved with the DirectoryCombo control. It won't show the
directory list if the package is launched by MsiInstallProduct yet it works
fine when CreateProcess used.

Tooltips won't show when MsiInstallProduct employed

2009-11-23T11:25:01Z

Hello,
I have made a simple MSI package which shows a dialog with single editbox.
The Help column of the editbox in the Control table contains "Nonsensical
tooltip text.|" (export below).
Dialog_ Control Type X Y Width Height Attributes Property Text Control_Next Help
TooltipTestDlg Edit Edit 10 10 80 17 3 EditProperty Text Close Nonsensical

Re: Minor upgrade as MSI on server with previous version of MSI &

2009-11-21T06:25:01Z

Hi Jie Wang,
Do you have any update on this issue.

RE: Error 2755

2009-11-21T01:49:02Z

And to give a bit of a context - this is windows XP SP1, VersionMsi = 3.01.

Error 2755

2009-11-21T01:26:01Z

Can someone help with the following error.
MSI (c) (D8:8C) [17:35:38:343]: Note: 1: 2755 2: 1 3:
C:\DOCUME~1\ADMINI~1\LOCALS~1\ Temp\00003abe\VMware Tools.msi
DEBUG: Error 2755: Server returned unexpected error 1 attempting to install
package C:\DOCUME~1\ADMINI~1\LOCALS~1\ Temp\00003abe\VMware Tools.msi.

Re: CustomAction help

2009-11-20T22:27:19Z

[Please do not mail me a copy of your followup]
"Micus" <N...@nowhere.com> spake the secret code
<uRTfRNKZKHA.5...@TK2MSFTNGP02 .phx.gbl> thusly:
The main thing you're bashing your head against here is the silly
constraints imposed on CAs by the VS.NET deployment project model.
The architecture I would use for your problem is this:

Re: Where did the "please wait..." message in setup.exe go?

2009-11-20T17:45:10Z

No it's not the same setup.exe, that's the point.

Re: Where did the "please wait..." message in setup.exe go?

2009-11-20T15:43:02Z

Ok, I have sent it.
Thanks,
Mike

Re: Where did the "please wait..." message in setup.exe go?

2009-11-20T11:56:57Z

Hello Mike,
Can you just send me (jiewan at msft) the setup.exe file (just that one
file and you'll probably need to rename and compress it to avoid antivirus
software killing it) so I can take a look and make sure what exactly it is?
Since I still don't know what it's made of (Visual Studio 2005 Setup

Re: CustomAction help

2009-11-20T04:12:01Z

If I recall correctly (it's a bit hazy), in order to get the right
privileges for Vista, when using the older Visual Studio deployment projects,
you have to manually adjust the custom action type. This because, as Phil
mentioned, the older setup projects don’t set it correctly.
So, after creating the msi file, you have to manually adjust the custom

Re: Where did the "please wait..." message in setup.exe go?

2009-11-20T02:46:03Z

Yes, I would guess that is the same setup.exe that visual studio uses. I
don't think .net comes into - at least I am not use .net for anything.
Still my question is what happened to the "please wait..." message box? I am
thinking that it must be something that I can re-activeate because it seems
hard to believe it would be removed. Without it there is nothing on the

Re: Where did the "please wait..." message in setup.exe go?

2009-11-19T21:11:08Z

That makes sense -- source for that version of setup.exe & msistuff.exe were
part of the Platform SDK at one time. I've used them on several occasions
for my setup projects.

Re: HKEY_CURRENT_USER vs HKCU

2009-11-19T20:36:09Z

Writing to HKLM is generally a better choice. For a multi-user app, these
would be the default set of registry items. The app can then copy these to
HKCU and update them as required when the user first runs the app. HKLM is
readable for limited users. There isn't really a practical way to populate

Re: Where did the "please wait..." message in setup.exe go?

2009-11-19T20:25:47Z

That sounds like the one specifically designed to download MSI files from an
internet location:
[link]
using msistuff etc.