Using SDK 2006.4 and trying to base our package on "ProjectBase" it seems we
have to redistribute & intall ProjectAggregator2.msi... Am I right?
However whenever I try to msiexec /qb /i ProjectAggregator2.msi
I get the following error message: "Microsoft Visual Studio
ProjectAggregator2 can only be installed on machines with Visual Studio 2005
installed."
I tried this with "Visual Studio 2005 Professional" installed
on Windows Server 2003 system (and SDK not installed yet)
on Windows XP Pro X64 system (with SDK actually already installed)
on Windows XP (x86) system (with SDK actually already installed)
...
I always get same message!
Note: log /i*v didn't help me much:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - -
MSI (s) (A8:8C) [11:25:04:310]: Doing action: LaunchConditions
MSI (s) (A8:8C) [11:25:04:310]: Note: 1: 2205 2: 3: ActionText
Action start 11:25:04: INSTALL.
Action start 11:25:04: LaunchConditions.
MSI (s) (A8:8C) [11:25:07:123]: Note: 1: 2205 2: 3: Error
MSI (s) (A8:8C) [11:25:07:123]: Note: 1: 2228 2: 3: Error 4: SELECT
`Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (A8:8C) [11:25:07:123]: Product: Microsoft Visual Studio
ProjectAggregator2 -- Microsoft Visual Studio ProjectAggregator2 can only be
installed on machines with Visual Studio 2005 installed.
MSI (c) (B0:0C) [11:25:04:310]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
Microsoft Visual Studio ProjectAggregator2 can only be installed on machines
with Visual Studio 2005 installed.
Action ended 11:25:07: LaunchConditions. Return value 3.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - -
Can anyone tell me how this can be worked around...?
(the obvious work around that consists on installing SDK is not accepatble
since we should not install SDK along with our package once it is release to
public)
DRS.
Regards.
SYB.DRS - 03 May 2006 16:25 GMT
Ooops... I have partialy figured out the answer:
The MSI has a built in pre-condition that ensures that
[HKLM\SOFTWARE\Microsoft\VisualStudio\8.0] InstallDir != ""
unfortunately, for x64 (Amd64) platforms,
the HKLM registry hive path contains an aditional
"Wow6432Node" since VS is still a 32 bit application!
Thus, the existing key to check for on Amd64 platforms is
[HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0] InstallDir != ""
Could this be fixed for next release!
NOTE: RegPkg also fails to take into account platform and create keys in
[HKLM\SOFTWARE\Microsoft\VisualStudio\8.0XXX]
rather than
[HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0XXX]
The reason why I failed to install on raw XP is still unclear I may have
mistyped something, however a simple double click on MSI works ...
DRS.
Regards.
SYB.DRS - 03 May 2006 16:56 GMT
CORRECTION again!
it seems that double click on MSI also works on Amd64 plaforms!
It is just that MSIExec only works with /r or /f
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
Could this be a security issue, I mean something preventing silent install
so that user is aware of install?
I still need to work around that!
This is to uggly to have that additional gauge popup during our product
install!
MS. could you provide some way silenlty install this? (may be an MSM?)
DRS.
Apologizes.