Scenario:
I have a visual basic application that uses a custom ocx control. When I build the application the TBSMidiIO.ocx get converted to AxInterop.TBSMidiIOLib.dll and Interop.TBSMidiIOLib.dll. I installed the published application on a test machine with prerequisites. When I double click the application shortcut, the application will not run. With further investigation, I registered the TBSMidiIO.ocx In SysWow64 folder, and now the application works.
General Question:
Should the application work with the AxInterop.TBSMidiIOLib.dll and Interop.TBSMidiIOLib.dll files, or must it be the TBSMidiIO.ocx alone? If I need to install and register the TBSMidiIO.ocx in the SysWow64 folder, how do I do this through ClickOnce.?
Specific Question:
How do I publish a ocx or DLL, through Visual Studio 2013, to be installed in a system folder and then have this component registered?
Glen Stark