Gonna sound nuts... How does one go and force the registered major & minor version to change in a compiled VB ocx?

My goal is to create a simple ocx with the major version > 9 and minor version > 9. However, setting those properties doesn't seem to affect the version information that is registered. For example, I set major to 25 and minor to 11 & compiled the ocx.

You do see those settings in the file properties page when right clicking on the ocx file. But that's not where I wanted it to show -- just don't care.

But when I use OLE/COM Object viewer, look at registry or add ocx to a new project & look at the vbp file, all show version 1.0, i.e.,
Object={D5538258-61AF-4E1D-B111-CCEE41090734}#1.0#0; Project1.ocx

I did manage to get it to go to version 1.1 by adding new public methods. However, that pattern didn't pan out because I can't get the stupid thing past 1.1

Why do I want to do this? For personal education and a test for something else I'm working on.