Success!
Alex Shevchuk wrote:
> OK, here is the problem. Upgrade/@Id must have the same value as
> Product/@UpgradeCode.
Thank you, Alex. That was the problem. FindRelatedProducts is working and
only one entry exists in the Add or Remove Programs table after the
installation of the new version.
Alex Shevchuk wrote:
> Well, if per-user/per-machine context did not change, I can only
> suggest comparing your upgrade steps to steps in here:
> ...from-msi-to-wix-part-8-major-upgrade.aspx
I worked through that page of instructions. That resulted in a few changes.
In the Package element I adde
Schaff, Stephen wrote:
> That fixed it! Thanks!
I think you replied to the wrong message, Stephen. The 'two entries' problem
continues.
--
Charles
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances
Alex Shevchuk wrote:
> Product/@Version must be changed as well and whatever is used as a
> value for Product/@Version must be used for UpgradeVesrion/@Minimum
> where Property="NEWERVERSIONDETECTED".
I neglected to show that in my initial message. It uses the same binder as
the Upgrade elements:
Wilson, Phil wrote:
> That means it didn't find the previous version for some reason
> otherwise it would mention the ProductCode guid of the discovered
> product. What's actually in the Upgrade table in the MSI file? I'm
> wondering if the version range is really correct.
>From Orca, here are the
Wilson, Phil wrote:
> Get an MSI log to see what's going on. Look at all instances of
> FindRelatedProducts to see if it's detecting your older product.
There are two sections of FindRelatedProducts in the log for the 1.1 version
upgrade installation.
MSI (c) (28:8C) [18:56:27:953]: Doing action
I have been testing the major upgrade procedure under WiX Version 3.0.5217.0
and Windows XP. I install version 1.0 of my application successfully. (It
has the required Upgrade element.) To prepare for the next version of my
application I increment the FILEVERSION, PRODUCTVERSION and FileVersion
ce I ran through the compression levels on the .msi
build of one of my programs.
Compression Level > Time (seconds) > File Size (MB)
none > 11 > 6.05
mszip > 11 > 2.25 (default)
low > 11 > 1.91
medium > 12 > 1.81
high > 14 > 1.73
That's quite a space sa
d registry entry. Perhaps a registry cleaner
will scrub it away. Few, if any, users will notice.
george_r wrote:
> Chuck, try:
> 1
That's what InstallScope=perMachine does and from
http://www.joyofsetup.com/2008/04/01/new-wix-feature-setting-package-installation-scope/:
"If
My application installs on a per-machine basis so that it is available to
all users. I have InstallPrivileges=elevated and InstallScope=perMachine. In
addition, the installer creates some registry entries for my application in
HKLM because I have specified Root=HKMU.
I would like to set some d
ter that everything works just fine.
I checked the log files and from what I can tell there are no errors...I
just don't understand why its giving me the message and how to fix it. Any
help would be appreciated.
--
Thanks,
Chuck Hanna
---
been installed properly and everything works!!
Any ideas of what might be this issue would be greatly appreciated.
Thanx
Chuck
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 e
ing as
Administrator. I know it is failing because I have the exact same code
that the CA calls wrapped up as an exe and if I run it as admin and
then look at the output from both it is different.
Any other thoughts would be greatly appreciated.
Thanx
Chuck
> I suspect you're misunder
k with ocx controls.
Thanx
Chuck
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief su
to run as an Administrator?
Thanx
Chuck
> A couple or four things:=20
> 1) Does "early in the installation process" mean in the UI
sequence?=20
> 2) Manifests target executables, not Dlls - they run with the
level of
> the exe that loads them.=20
> 3) If the setup.exe isn
the CA fails.
Any thoughts on this would be greatly appreciated.
Thanx
Chuck
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinio
Bob,
Thanx for your quick response...
Why is it not recommended and what about it is difficult to get right?
Cheers
Chuck
Bob Arnson wrote:
> Chuck wrote:
>> Is it possible to call a third party dll, included in my installer as
>> a binary file only, from a custom action that
Is it possible to call a third party dll, included in my installer as a
binary file only, from a custom action that is in a C++ dll?
If that isn't possible is that anyway to access a 3rd party dll from my
custom action prior to the installation of files?
Thanx
Please enter your registration code.
{\WixUI_Font_Title}Registration Code
I know that the dll is being called properly as I can see it in the
install log file and I can write out to file in the dll when it gets called.
Any thoughts or ideas wo
more dynamic so that it can find the
installed executable and launch it. I've got to get this installer
finished today but if you have any other ideas I'd love to here them.
I've never run into this problem before??
Thanx for all you help!
Cheers
Chuck
Bob Arnson wr
value 1.
Property(C): INSTALLDIR = C:\Test foo\
INSTALLDIR is correct and all of my application files where installed
there. The 1631 error is ERROR_CREATE_FAILED...The Windows Installer
service failed to start... Sounds like MSI is try to start again...not
start my app?? HMMM.
Chuck
Bob
)
1
Where fooexe is the id of my primary executable. Like I said, this
works as long as the user doesn't change the installation folder?
I'll generate a log file as soon as I get a chance...probably later today.
Chuck
Bob Arnson wrote:
> Chuck wrote:
would cause this to happen would be greatly appreciated.
Cheers
Chuck
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT
nce
I have the Custom Action set to run After="LaunchConditions".
Cheers
Chuck
Bob Arnson wrote:
Chuck wrote:
Thanx for getting back to me...do you have any idea which version of
Wix the bug was fixed in?
I'm not sure of the exact number. It was fixed either
greatly appreciated.
Cheers
Chuck Hatt
Senior Software Engineer
Sourcerer.com
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on
25 matches
Mail list logo
