Merge Modules in SkinFramework 17.2

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   We had recently upgraded our software to use SkinFramework 17.2.0 from 16.4.0.
We have an installshield project that handles bundling everything up for installation. I had gone through and removed the 16.4.0 merge modules and added the 17.2.0 ones.

We are having an issue where the ocx files are not being registered properly after we run the installation. If we regsvr32 manually on each of the ocx's that we use, everything works properly.

I did a bit of digging and opened the old 16.4.0 merge modules in installshield, and then compared the 17.2.0 modules.

In the 16.4.0 msm files, there is registry information under HKEY_CLASSES_ROOT that contains class id's. I assume this is what installshield installs into the registry for these components.

In the 17.2.0 msm files, there are no registry keys whatsoever, so I am pretty sure that is the problem. Is this intentional on Codejock's part?

We have a workaround to extract the registry information from an OCX and create a registry file, and manually add the OCX's to our install.. but before I do that I wanted to see if this was a known issue and if new merge modules were on the way. I would much rather use an msm than manually add the ocx components and have separate registry files for each one.

Any information is appreciated!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
jbachTT Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 13 May 2016 Location: Tempe, AZ Status: Offline Points: 2	Post Options Post Reply Quote jbachTT Report Post Thanks(0) Quote Reply Topic: Merge Modules in SkinFramework 17.2 Posted: 13 May 2016 at 2:47pm
	We had recently upgraded our software to use SkinFramework 17.2.0 from 16.4.0. We have an installshield project that handles bundling everything up for installation. I had gone through and removed the 16.4.0 merge modules and added the 17.2.0 ones. We are having an issue where the ocx files are not being registered properly after we run the installation. If we regsvr32 manually on each of the ocx's that we use, everything works properly. I did a bit of digging and opened the old 16.4.0 merge modules in installshield, and then compared the 17.2.0 modules. In the 16.4.0 msm files, there is registry information under HKEY_CLASSES_ROOT that contains class id's. I assume this is what installshield installs into the registry for these components. In the 17.2.0 msm files, there are no registry keys whatsoever, so I am pretty sure that is the problem. Is this intentional on Codejock's part? We have a workaround to extract the registry information from an OCX and create a registry file, and manually add the OCX's to our install.. but before I do that I wanted to see if this was a known issue and if new merge modules were on the way. I would much rather use an msm than manually add the ocx components and have separate registry files for each one. Any information is appreciated!
	Jonathan Bach Software Developer Tyler Technologies

csware Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 08 March 2008 Location: Germany Status: Offline Points: 10	Post Options Post Reply Quote csware Report Post Thanks(0) Quote Reply Posted: 15 May 2016 at 11:48am
	Hello Team, this is not only a problem at the skin framework. I encountered that the SyntaxEdit Control does not self register when using the msm. At the moment i'm not sure wether this problem exists in other MergeModules. Pls have a look at the msm files and correct them.
	Product: Xtreme SuitePro (ActiveX) version 17.2.0 Platform: Windows 10 (64 Bit) Language: Visual Basic 6.0 SP 6a