Solution of controls on registration and licensing issues: catclaw2000
In view of the authorization issues trapped in Microsoft controls, it is difficult to find a solution on the Internet, and the two-day forum does not stop netizens in question similar problems, and write this article, with 飨 vckbase All netizens. Everyone knows that for ordinary OCX controls, when we publish, use the installation software to copy to the target machine and then register (or register with regsvr32)
It is ok.
But some controls provided by Microsoft, such as Microsoft Ado Control, Microsoft DataGrid Control, etc., often discovered that in the development of machines are used, but use the normal release process, publish them to the target machine, will appear "
No registration category
"of
Tip, software cannot be used, and so on.
The reason is that Microsoft adds the licensing mechanism (License) in order to prevent its software from being illegally released; if the development environment needs to be licensed, and in the target code environment, the application can be used normally Can't be opened by other development tools; why do I violate the original idea of Microsoft? I will not know. Let us enter the topic and talk about how to solve this problem.
First, you must figure out the storage location of the license information, tell you, just in the hkey_classes_root / licenses directory. Next, I need to know which control is used by the registration information. Under the VS.NET mounting disk, there is a registration file VB6Controls.reg to record the license information of most of the controls of VB6, below The content of this file:
Regedit
HKEY_CLASSES_ROOT / LICENSES = licensing: Copying The Keys May Be a Violation of Established CopyRights.
// Masked Edit Control 6.0 license Key
HKEY_CLASS_ROOT / LICENSES / BC96F860-9928-11CF-8AFA-00AA00C00905 = mmimfflflmqmlfffrlnmofhfkgrlmmfmqkqj
// Chart Control 6.0 (OLEDB) License Key
HKEY_CLASS_ROOT / LICENSEES / 12B142A4-BD51-11D1-8C08-0000F8754DA1 = AADHGAFABAFAJHCHNBCHEHFAMBFBBACHMFMB
// Common Dialog Control 6.0 License Key
HKEY_CLASS_ROOT / LICENS / 4D553650-6ABE-11CF-8ADB-00AA00C00905 = GFJMRFKFIFKMKFFRLMMMHMNLULKMFMQKQJ
// Ado Data Control 6.0 (OLEDB) License Key
HKEY_CLASS_ROOT / LICENSES / C4145310-469C-11D1-B182-00A0C922E820 = Konhqhioohihphkouimonhqhvnwiqhhnjti
// Common Controls-3 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 38911DA0-E448-11D0-84A3-00DD01104159 = MCPCHCDCHJCJCCCLIDCGCGCGCHDQDCJHCOJPD // Windows Common Controls-2 5.0 (SP2) License Key
HKEY_CLASS_ROOT / LICENSES / 9E799BF1-8817-11CF-958F-0020AFC28C3B = uqpqnqkjujkjjjjqwktjrjkjtkupsjnjtoun
// Windows Common Controls License Key
HKEY_CLASS_ROOT / LICENSES / 57CBF9E0-6AA7-11CF-8ADB-00AA00C00905 = aahakhchghkhfhamghhbhbhkbpgfhahlfle
// Data Bound Grid Control 5.0 (SP3) License Key
HKEY_CLASS_ROOT / LICENSES / 556C75F1-EFBC-11CF-B9F3-00A0247033C4 = xybiedobrqsprbijaegcbislrsiucfjdhisl
// Data Bound List Controls 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 096EFC40-6ABF-11CF-850C-08002B30345D = KNSGIGMNMNGNIGTHMGPNINRMUMHGKGRLRK
// Internet Transfer Control 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 78E1BDD1-9941-11CF-9756-00AA00C00908 = YJRJVQKJLQQJNQKJVPRQSJNJVKUKNJPJTUN
// MultiMedia Control 6.0 license Key
HKEY_CLASS_ROOT / LICENSES / B1EFCCF0-6AC1-11CF-8ADB-00AA00C00905 = qqkjvqpqmqjjpqjjvpqqkqmqvkyPoQjquoun
// Chart Control 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 7C35CA30-D112-11CF-8E72-00A0C90F26F8 = WHMHMHOHMHIRHKOUIMHIHIHWIWIWINHLOSMSL
// Windows Common Controls-2 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 4F86BADF-9F77-11D1-B1B7-0000F8753F5D = iPlpwpnippopupiivJrioppisjsjlpiiokuj
// Windows Common Controls 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / ED4B87C4-9F76-11D1-8BF7-0000F8754DA1 = knlgnmntggninthpgmnngrhqhnnnjnslsh
// Comm Control 6.0 license Key
HKEY_CLASS_ROOT / LICENSES / 4250E830-6AC2-11CF-8ADB-00AA00C00905 = kjljvjjjoquqmjjvpqqqqmqykoqjquoun
// DataGrid Control 6.0 (OLEDB) License Key
HKEY_CLASS_ROOT / LICENSES / CDE57A55-8B86-11D0-B3C6-00A0C90AEA82 = Ekpkhddkjkekpdjkqemkfkldoeoefkfdjfqe // DataList Control 6.0 (OLEDB) License Key
HKEY_CLASS_ROOT / LICENSES / A133F000-CCB0-11D0-A316-00AA00688B10 = CibbcimbpihbbbbnhdbeidiockcMCBBDBGDOC
// dbwin license key
HKEY_CLASS_ROOT / LICENSES / D015B071-D2ED-11D0-A31A-00AA00688B10 = gjdcfjpcmjicjcdcoihceChjlioiccechepd
// MSDBRPT LICENSE Key
HKEY_CLASS_ROOT / LICENSES / 9DF1A470-BA8E-11D0-849C-00A0C90DC8A9 = cchcqjejhcgcqcfjpdfcdjkckikchcojpd
// FlexGrid Control 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 1F3D5522-3F42-11D1-B2FA-00A0C908FB55 = gcfjdjecpchcncdjpdejijgcrdoijjfcieod
// MAPI Controls 6.0 license Key
HKEY_CLASS_ROOT / LICENSES / 899B3E80-6AC6-11CF-8ADB-00AA00C00905 = wjsjjjlqmjpjrjjvpqqkqmqukyPoQjquoun
// msrdo 2.0 license key
HKEY_CLASS_ROOT / licensees / b1692f60-23b0-11d0-8e95-00a0c90f26f8 = mjjjccncgjijrcfjpdfjfcejpdkdkcgjojpd
// RemoteData Control 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 43478D75-78E0-11CF-8E78-00A0D100038E = IMSHoHOHPHLMNHIMUINMPHMMUIMINHLMSMSL
// Windowless Controls 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 80E80EF0-DBBE-11D0-BCE2-00A0C90DCA10 = qijimitpmpnpxplpvjnikpkpqoxjmpkpoivj
// PictureClip Control 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / 6FB38640-6AC7-11CF-8ADB-00AA00C00905 = GDJKOKGDLDIKHDDDPJKKEKGKNESJIKDKOIOH
// Rich TextBox Control 6.0 License Key
HKEY_CLASS_ROOT / LICENSES / DC4D7920-6AC8-11CF-8ADB-00AA00C00905 = iokouhloohrojhhtnooiokomiwnmohosmsl
// Sheridan Tab Control License Key
HKEY_CLASS_ROOT / LICENSES / 190B7910-992A-11CF-8AFA-00AA00C00905 = gclClcejjcmjdccoikjlcecoiijjcjng
// sysinfo control 6.0 license key
HKEY_CLASS_ROOT / LICENSES / E32E2733-1BC5-11D0-B8C3-00A0C90DCA10 = KMHFIMLFLMMFPFFMSGFMHMRIMNGHMOFLHSG // Winsock Control 6.0 license Key
HKEY_CLASS_ROOT / LICENSES / 2C49F800-C2DD-11CF-9AD6-0080C7E7B78D = mlrljgrlhltlngjlthrligklpkrhllglthrk
Usually we can resolve our control license issues as long as we import this file into the registry of the target machine. However, there are two problems in my use:
This note is inaccurate, that is, it may be a license for a control, but with this license is not at all, I don't know whether it is Microsoft's deliberate or wrong, such as FlexGrid Control 6.0 license should be: hkey_classes_root / licenses / 72e67120 -5959-11CF-91F6-C2863C385E30 = ibcbbbebqbdbciebmcobmbhifcmciibblgmf
Licensing information is incomplete, that is, some controls have nothing in this file;
Then what do we do? ING .... A head, there is, since we already know that it is in the registry, and in the development machine, it does not directly guide the registration information in the entire license content on the development machine, and then import On the target machine, it is not only a fish :) Oh, everyone understand?
For the first time, write articles, the mistakes are inevitable, welcome to the fingers. Also, this article is only for learning exchanges, and I hope that the copyright of Microsoft will not violate.