Setup CodeJock 18.2.0 Bug
Printed From: Codejock Forums
Category: Codejock Products
Forum Name: General Discussion
Forum Description: Topics Related to Active-X COM Development in General
URL: http://forum.codejock.com/forum_posts.asp?TID=23506
Printed Date: 04 December 2024 at 4:12am Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Setup CodeJock 18.2.0 Bug
Posted By: Vycheslav
Subject: Setup CodeJock 18.2.0 Bug
Date Posted: 27 November 2017 at 8:22am
Setup enters invalid registry keys:
[HKEY_CLASSES_ROOT\CLSID\{1E9DC4EC-BECB-4A1B-88C0-2BCF8C0A9890}] @="Codejock.CalendarGlobalSettings.18.0.1"
[HKEY_CLASSES_ROOT\CLSID\{1DD48C87-0821-467F-900D-38764B8ED446}] @="Codejock.ChartControlGlobalSettings.18.0.1"
[HKEY_CLASSES_ROOT\CLSID\{57365410-D18F-4F58-8647-38F1AD3314C3}] @="Codejock.CommandBarsGlobalSettings.18.0.1"
And other 10 registry keys @="Codejock.DockingPaneGlobalSettings.18.0.1" @="Codejock.FlowGraphGlobalSettings.18.0.1" @="Codejock.MarkupGlobalSettings.18.0.1" @="Codejock.PropertyGridGlobalSettings.18.0.1" @="Codejock.ReportControlGlobalSettings.18.0.1" @="Codejock.ShortcutBarGlobalSettings.18.0.1" @="Codejock.SkinFrameworkGlobalSettings.18.0.1" @="Codejock.SuiteControlsGlobalSettings.18.0.1" @="Codejock.SyntaxEditGlobalSettings.18.0.1" @="Codejock.TaskPanelGlobalSettings.18.0.1"
|
Replies:
Posted By: olebed
Date Posted: 27 November 2017 at 10:49am
Hello Vyachweslav,
I have just checked and can confirm that these are from previous installation of v18.0.1. But ProdID changed to correct value and other registered controls have correct values.
Regards, Oleksandr Lebed
|
Posted By: Vycheslav
Date Posted: 28 November 2017 at 2:30am
This is very well, but current setup is invalid.
|
Posted By: olebed
Date Posted: 28 November 2017 at 10:37pm
Looks like v18.2 and v18.0.1 have the same uuid for activeX controls. I hope this will be fixed soon in next release.
Thank you for information.
|
Posted By: Vycheslav
Date Posted: 29 November 2017 at 6:29am
Problem occurs only with using both version 18.2 and 18.0.1. On developers machine we correcting it manually.
|
|