I guess DLLTOOLSSW is the name of the 4DX, not the DLL it is linked to. the mystery is why it "appeared to work with v15" initially.
even though DLL wizard is no longer available for unicode mode, it was always possible to read public C APIs from a DLL using DUMPBIN. then you could use LIBTOOLS and some text editing to create a LIB file for linking. and call the DLL using standard Win32 APIs. but it would be much easier if there were at least some header files or SDK to use that DLL. > 2016/09/01 23:38、Douglas Cryer <[email protected]> のメール： > > It was then converted to the new Plugin architecture via plugin wizard > (although I am unsure of the settings that were used). This has worked for > the past few years with v13 and appeared to work with v15 but since deploying > it in on one of the few clients who use this PAF solution we have found that > it no longer works with v15. The plugin shows and the code compiles but at > runtime it does not work. > > As far as I can tell the internal path to the DLL is not resolving or there > is an issue with how the plugin is > I may need help more than just advice with this as each day that goes by > means a client is unable to use the functionality. > Any ideas are welcomed. Ideally what I need is a way of directly creating a > new style plugin from the DLL like the old DLL Wizard process which is sadly > missed. 宮古 啓介 セールス・エンジニア 株式会社フォーディー・ジャパン 〒150-0043 東京都渋谷区道玄坂1-10-2 渋谷THビル6F Tel: 03-6427-8441 Fax: 03-6427-8449 [email protected] www.4D.com/JP ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
