http://forum.codejock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Mon, 20 Apr 2026 20:14:48 +0000 Mon, 13 Mar 2017 13:36:26 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 forum.codejock.com/RSS_post_feed.asp?TID=23245 http://forum.codejock.com/forum_images/codejock-logo.gif http://forum.codejock.com/ http://forum.codejock.com/forum_posts.asp?TID=23245&PID=75623&title=deployment-and-versions#75623 Author: ScottW
Subject: 23245
Posted: 13 March 2017 at 1:36pm

Sorry, this was just pilot error. Move along, nothing to see here...
]]> Mon, 13 Mar 2017 13:36:26 +0000 http://forum.codejock.com/forum_posts.asp?TID=23245&PID=75623&title=deployment-and-versions#75623 http://forum.codejock.com/forum_posts.asp?TID=23245&PID=75497&title=deployment-and-versions#75497 Author: ScottW
Subject: 23245
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


]]> Mon, 16 Jan 2017 13:10:54 +0000 http://forum.codejock.com/forum_posts.asp?TID=23245&PID=75497&title=deployment-and-versions#75497