Hi Able,
I just want to be clear, so sorry for the longwinded answer.
The major change that affects people who are building customizations for Desktop at 10 is that these customizations are no longer loaded through component categories in the registry, but instead through product specific configuration files (ecfg). The point of the article is to say that if you have an existing dll that always �??just worked�?� and you want to try it in 10 �??as is�?� then here is how you can create an ecfg file for that dll. Try it, if it works, great!
There is a good chance that if you just create the proper ecfg file, it might just work. (No guarantees) If it does work we still recommend that you recompile, but at least for now things are working, and you can spend more time on your migration process. If you built your dll in VB6, please migrate to a supported development language. If you built it in any other language recompile and certify. If it doesn�??t work or have problems, then you must recompile.
The deployment mechanism is the same for dlls that are compiled at the current release or older ones. The only additional step you have to do in 10 is that your setup program needs to put the ecfg file in the right spot on the target machine.
So in your situation, you could try to use the VB6 dll without recompiling against 10. Or you could compile your VB6 dll against 10. (Either way this would not be supported, because at 10 VB6 is not longer supported). Then you would run ESRIRegAsm against your reg file to create an ecfg file.
To deploy you can deploy like you always have done. Since it is a VB6 dll and VB6 dlls do not support category registration, you might have used a reg file to register the dll and category information. You could use regsvr32 to register the dll, or you could use this same reg file to register the dll, but you don�??t need the category information in the reg file, that is all in the ecfg file, which you copy over to the CATID folder.
Hope this helps.
