471,582 Members | 1,451 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,582 software developers and data experts.

Where to go with Windows Installer 3.0 problems in VS 2005?

I'm having several issues with Windows Setup Projects in VS 2005 and need to
find a resource that might be able to help me work around some of the short
comings of Windows Setup Projects (Windows Installer 3.0).

My specific issues:
1. DetectNewerInstalledVersion = False, still detects a version and refuses
to install even with UpgradeCode = same and ProductCode being difference.
2. DeleteAtUninstall doesn't work if = False (some BS Windows Logo
requirement -- so why even provide an option if MS don't allow it?)

As it stands right now, Windows Installer 3.0 packaged with VS 2005 clearly
is NOT ready for prime time and can't even handle the basic tasks. Should I
be going back to InstallShield??

If someone can point me in the right direction, I'd appreciate it.

Rob.
Dec 21 '05 #1
1 1777
joe
Since last week we have windows installer problems. It's not possible to
install or change software because of the installer problem. We've repaired
the installer but after a few days the installer is corrupt again. It seems
that the updates of Windows XP causes this problem. Pc's on which we've
deactivated the automatic update still work fine.
"Rob R. Ainscough" wrote:
I'm having several issues with Windows Setup Projects in VS 2005 and need to
find a resource that might be able to help me work around some of the short
comings of Windows Setup Projects (Windows Installer 3.0).

My specific issues:
1. DetectNewerInstalledVersion = False, still detects a version and refuses
to install even with UpgradeCode = same and ProductCode being difference.
2. DeleteAtUninstall doesn't work if = False (some BS Windows Logo
requirement -- so why even provide an option if MS don't allow it?)

As it stands right now, Windows Installer 3.0 packaged with VS 2005 clearly
is NOT ready for prime time and can't even handle the basic tasks. Should I
be going back to InstallShield??

If someone can point me in the right direction, I'd appreciate it.

Rob.

Dec 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by S Moran | last post: by
3 posts views Thread by Claire | last post: by
12 posts views Thread by Alan M Dunsmuir | last post: by
5 posts views Thread by ....DotNet4Ever.... | last post: by
reply views Thread by XIAOLAOHU | last post: by
reply views Thread by leo001 | last post: by
reply views Thread by lumer26 | last post: by
1 post views Thread by lumer26 | last post: by
reply views Thread by lumer26 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.