Codejock Forums Homepage
Forum Home Forum Home > Codejock Products > ActiveX COM > Suite Pro
  New Posts New Posts RSS Feed - Deployment and Versions
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Deployment and Versions

 Post Reply Post Reply
Author
Message
ScottW View Drop Down
Groupie
Groupie


Joined: 02 August 2005
Status: Offline
Points: 75
Post Options Post Options   Thanks (0) Thanks(0)   Quote ScottW Quote  Post ReplyReply Direct Link To This Post Topic: Deployment and Versions
    Posted: 16 January 2017 at 1:10pm
I'm not sure if I'm doing something wrong here or what, but I have run into an issue several times now where for example, new product uses 17.2 components, but an older product of ours hasn't been updated in a while and still uses 16.4 components. If you install a copy of older product after newer product is already installed, new product is now broken, I guess because when old product got installed it unregistered the newer OCX files when it registered the older ones. I am putting them always in the Windows system folder. My installer can't avoid  this using it's normal means since the new version uses different filenames from the old ones, but apparently the same GUID internally. Is there a good way to prevent these sorts of issues?

Thanks


Back to Top
ScottW View Drop Down
Groupie
Groupie


Joined: 02 August 2005
Status: Offline
Points: 75
Post Options Post Options   Thanks (0) Thanks(0)   Quote ScottW Quote  Post ReplyReply Direct Link To This Post Posted: 13 March 2017 at 1:36pm
Sorry, this was just pilot error. Move along, nothing to see here...
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.079 seconds.