Hi,

I do have a problem with loading a CDialog-window (MFC) in a Visio Add-on in Visio 2016 with a ActiveX control on the dialog. The ActiveX-control is not registered on the machine, but 'registry-free activation' is used via a manifest. In the manifest the following info is added:

<file name="SftTree_IX86_U_70.ocx">


<comClass description="SftTree/OCX Tree Control"
clsid="{10C7FF33-FC3E-4579-A9F2-C1BA410D3B56}"
threadingModel = "Apartment"
miscStatus="setclientsitefirst,simpleframe,alignab le,activatewhenvisible,insideout,cantlinkinside,re composeonresize"
progid="SftTreeOCX70.SftTree.1"
tlbid = "{10C7FF30-FC3E-4579-A9F2-C1BA410D3B56}"/>
<typelib tlbid="{10C7FF30-FC3E-4579-A9F2-C1BA410D3B56}"
version="7.0" helpdir=""/>
</file>
</assembly>The Visio Add-on is a C++-project build with Visual Studio 2015 and the platform toolset is set to 'Visual Studio 2015 (v140)'.

When building the Visio Add-on with Visual Studio 2015 and platform toolset is set to 'Visual Studio 2013 (v120)' the problem does not occur.

So, I think the problem is a combination of MFC V14 with Visio 2016.

Is this a know issue and if so could you solve this issue. Or do you have I solution for this issue?

The Visio Add-on is Win32 and I use the 32-bit of Visio 2016.

Kind Regards,

Thierry