This is not a question but rather a finding of something in case any one else runs across the same problem.
When using "CreateObject" in VB 2012 of an unmanaged com object on a system that was configured with a fresh install of Win8 / VS 2012, the "Cannot create ActiveX component" error will be encountered when the targeted framework is 4.0 or earlier. Targeting 4.5 results in a VSHost32.exe error. Not an issue specific to a single system since it occurs on multiple systems starting with complete clean installs of Win8/VS2012 (issue may or may not apply to VS 2010 on Win8 - didn't bother testing that given time involved to repeatedly install everything)
The above error applies only when running the code in debug mode via the IDE. If the code is compiled and then run, no error occurs and everything works correctly.
Occurs on both 32 and 64 bit Win8 systems.
Running the identical code on a Win7 / VS 2012 system - no problems are encountered
The problem does not occur on a Win8 system which was upgraded from a Win7/VS 2012 (32 or 64 bit) indicating that something is being carried over that is not getting included on a clean Win8 install (which includes any new system using Win8 on which VS 2012 is being installed)
Just to avoid needless suggestions, there is no question the component was properly registered and project settings were identical in all cases. Method of registration used for the component was both using a setup installer for an app that uses the component as well as Regsvr32 when only registering the component on its own.
Karl Timmermans - The Claxton Group
Outlook Import/Export Hints/Tips
Contact import/export/data management tools for Outlook '2000/2010 -
ContactGenie.com