VS2017 ActiveX not found by C# .NET application RRS feed

  • Question

  • Have ancient VS2008 environment which uses ActiveX OCX.

    Have developed new VS2017 ActiveX OCX based on VS2008 dispatch points and events.

    Used aximp to create C# interop DLLs from VS2017 OCX.

    Can add references to both interop DLLS for C# .NET application.

    But when CreateControl is called for OCX, FileNotFound exception is triggered.

    Have used regsvr32 to register the original OCX.

    How can FileNotFound be resolved?

    Wednesday, April 18, 2018 10:27 PM

All replies

  • Hello Frank,

    >>How can FileNotFound be resolved?

    You need to give me the entire error message, when the file doesn't exist you need to obtain it by downloading or others, the most possible reason is occurred by relative path. you need to ensure you aren't under this case.

    Best Regards,

    Neil Hu

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Friday, April 20, 2018 7:40 AM
  • Is the ActiveX OCX 32-bit? Is your C# running 64-bit? If the answer to both of these questions is yes then you will need to change the Platform option of your C# app to x86 (32-bit) in order for the app to load the 32-bit ActiveX component.

    Paul ~~~~ Microsoft MVP (Visual Basic)

    Friday, April 20, 2018 2:11 PM