Hi Dirk, I've found the reason, why gSession is not found. The including of PlugIn.cpp was missing. Now I've some syntactical errors obviusely due to the via legalnotices shipped class-versions of Adobe. If you have any information/recommendation concerning that issue, you are wellcome. Regards Jochen ... View more

Hi Dirk, due to a lot of bugs/failures at CS2, I'v switched now to CS5.5. After addin g the respective additional include pathes to the different cpp-files, I get now at my Actioncomponent the error: error C2065: 'gSession' : undeclared identifier It seems to me that here is a similar failure as I've had at CS2. There obviusely classes/headers between the customer code and the Adobe stack. I've looked at the XMLCatalogHandler-Sample. Here at the projects properties the additione include pathes are set by using the variable 'id_sdk_dir'. Also this variable is not found, when I copy the pathes from the sample to my project. So where these variables are defined and how to make them visible at customer projects? Regards Jochen Seliger ... View more

Hi Steve, thank you for moving. What is the URL the right URL for? Regards Jochen Seliger ... View more

Hi Trevo, my you move my post to the right forum,. I was intended to post to the SDK forum. ... View more

Hi Manan, to lokate the causing of the uncatched dynamic cast error I had to exclude most of the files from my project an comment out lots of code lines. The reanination of my project was not really easy. But now the building process is working genarally corectly. But I get errors from all classes. Nearly from any class as the first logged line is reported the missing PMIID. It seems that tha following errors are mostly du to the initial error. What is missing? May you give me information, where PMIID is declared. Probably that file will hold more declarations, I'm requiring. Or is missing a setting at the project, or some where, to get access tho the global variables. Kind regards Jochen ... View more

Hi Markus, after having my build process generally working again, I've incuded OMTyes.h into my UIE.fr, to fix the missed PMIID failure. That changed at least the log-protocol. Now I get an error for missed namespace K3Meta. I stlll did not get the right information, where PMIID is declared. Could you please give me a tip, how to act? Regards Jochen ... View more

Hi Markus, which pathes shall the  rsp-and the pch-file containe. In my case the pch-file is containing the pathes the additionel include pathes of the project. The rsp-file seems to hold generel pathes (all them related to the SDK-Folder). But the fr-files buildstep does use the rsp-File. In my case that fact is leading to failures at building, related to not defined variables, declared within my ID.h-File. But that file does not within the pathes contained in the rsp-File. Is there a misunderstanding on my side, or where is the failure locaded? Jochen ... View more

Hi Markus, I'm facing now the following problem. After fixing a basic failure at my project, there are trown exceptions due ti not found PMIID and other global veriables like kPlugInIDSpace. They probably decrared at a haeder which is now missed. Could you please know the respective header? Kind regards Jochen ... View more

Hi Manan, I've inspected now my project again and found two failures. The first was a difference within the path at creation of the res file at the cpp files and the import at the UIE.rc-file. The second was the usage of a wrong makro for the Filename at the build step of the UIE.fr-file. But these functionalities are not yet reached. When compiling the cpp-files separately, nearly in all cases PMIID is not found basically. When building the Project, an error from my UIEID.h ist throw, wich is pointing to the missed kPlugInIDSpace. When commenting out that line, the next DECLARE_PMID(kClassIDSpace, kUIEActionComponentBoss, kUIEPrefix + 0) will thow the error concernig missed kClassIDSpace. It is the same situation as at the simple Dollx project. I can't find information, where PMIID and the k..IDSpace-variables are declared. Either the link to the Adobe_Object is broken (but that should not happen at a newly created Dolly-Project), or a header is missing. Could you please give me some advice? Kind regards Jochen ... View more

Hi Manan, as first some headers were not found, I've added the Include-pathes. That worked. But I'v inspected the sampple XMLCatalogHandler project. There only two relative pathes ..\..\..\external\axe\includes and ..\..\..\external\agm\includes These both pathes are not existing at my system. But the XMLCatalogHandler PlugIn my be build succesfully. I'v even started at another VM with a simple Dolly-project and reached the same errors as at my own project. There also are thrown errors du to not found declarated general values as PMIID, fInvaldPluginID, kInvalidClassID etc, hen copiling the single source files an at  buildin UIE.fr is reporting the all the haders to be imported, ar not found. It seems to me that the error is at the information transfer pch-, rep-, res-, fres-File naming/creation. I'v I remember right, I'v found last night, that there were differneces for the path||naming of one of the needed files at the Dolly-Project. In that case it will be quite clear, why some global-header-information is not tranferred to the single source files and no header-information at all is shipped to the UIE.fr-File. This issue I'll check and will come back to you if needed. Would be nice, If you could explain me the issue with the additional include pathes and how the XMLCatalogHandler-sample is getting the pathes to all the needed includes. Thanks and all the best for 2017. Regards Jochen ... View more

Hi Manan, that discussion semms to be close to myx current problem. After fixing a general failure, now top leven variables like kPlugihIDSpace, kCalsssIDSpace and PMIID can't fbe found. It seems to me, that the link to the Adobe (SDK) object is broken. Where that link is set. Is it within the vcproj-File or az the VC7-Properties. Or do you have another opportunity ti solve that problem? Kind regards Jochen ... View more

Hi Bartek, I try on two VM's to fix the problems I'm meeting. At the one I can build my plug-In without any error (after copying all the headers, missed by the Custom Build Step, into my source folder), but the Plug-In is rejected by InDesign CS2 as invalid. At the second one I've generated with DollyXS a smple project. Here also all headers, to be includet into the fr-file, are missing. The include pathes should be provided by the user rsp-file. This file was create by DollyXS and has lines as -i "..\..\..\source........... At that file seems to be all the incude pates in relative format, but no header is found. When adding a qualifyed include path, the odfrc is throwing the error 'The response file "Q2" can not be opened. The same error is thrown, when changing the introduction of the lines to /I "..\..\..\source... What's to do to fix that mix of errors? Regards Jochen ... View more

Hi Loic, my Plug-In shall handle the interaction between the workitem of oue ad production work flow solution. As we have hade build it about 10 years ago (it was unfortunately lost), we heve started again with CS2. We hade it build for several moths and could load it into ID CS2, although a relevant functionality is still missing. Some weeks ago we were confronted with a bug of VC7. After fixing that failure the plug-in is recognized by ID as invalid. We can build the Plug-in without any error. We arte really lost, because we have no chance to find out, what my cause the rejection. Could you please let us know, where to look at, to fix that failure? Kind regards Jochen Seliger ... View more

Hi Mana, the sucess with the CustomerBuid-Step is not yet trusted. I've recogniced that the input fields at that step were cleared by the disabeling. I will try to reimplement the values and will come back to you afterwards. Jochen ... View more

Hi Manan, I can load the shipped with the SDK pln's sucessfully into ID. Can you please let me know, what is forcing ID to reject a plug-in as invalid? Is it a information at the plug-in as it is, ore does ID check its functionality (what seems to me as impossible). Jochen ... View more

Hi Manan, after getting the error for missing headers at UIE.fr-processing by ordfc (CustomerBuildStep), I had diabled the VCHeader-usage and had set UIE.fr to C/C++-BuildTool. That way I could build my Plug-In succesfully, but is was rejected by ID as invalide. Today I've enabled th VCHeader-Usage first and could build my plug-In, but is was rejected by ID as invalid. Next I'e set my UIE.fr back to Customer-build-Tool (without changing the prior used settings) and could again my plug-in and again it was rejected by ID as invalid. Could you please give me a hint, where to look for information, what is wrong? I urgently need help!! Jochen ... View more

Hi Manan, I can  build my plug-in again with VC7-SDK 4.0.2. I've done it without VCPlugInHeaders-Logic and with the C/C++-BuildTool at my UIE.fr-File. But InDesign is stlll reginizing it as invalid. Where to find information, what is wrong? Where to find error messages, if somathing is wrong? Kind regards Jochen ... View more

Hi Manan, it was not the problem, if I user the qualifyed path or not, but what is the required configuration. I'v disabled now the customerBuildStep at my UIR.fr-File. Here I have still some class and Interface confiruration errors. After fixing them I'll come back to you to clafity the necessitity of that CustomerBuildStep (with the respective comend line) and the problem, why the separately caled odrfc does not find most of the headers at UIR.fr. ... View more

Hi Manan, meanwhile I've fixed some problems. The obj-files, the pch-file and the res-file are created. But my UIE.fr-file can't be compiled sucessfuly as long it is set to use the  Customer Build step-tool. The problen seems to be the path for the odrfc-call. That executable is not callable from a folder different from its detination. What should be done. a) make the odrfc callabe from any forder b) ad the incude folders to the path-variable c) anythig else? Jochen ... View more

Hi Manan, my problem after facing the bugs at VC7 (invalid Plug-Ins), is obviusely more generally. At the moment no obj-, no pch- and no res-file are created. I'm missing error messages concerning these essancial files. From the first beginning I've installed the SDK seperately from the VC installation dir. That's why the relative pathes in most cases do not work. As I told you, I could compile and build my Plug-In for several years under the described constallations. I could not find any documentation concerning the installation of the SDK into the VC folder. Do you have those documentation? My UIE.fr-File can't be compiled not separately nor while build process. Could you please let me know, how the header-pathes are tranferred to the customer build steps odrfc-call? The customer build step is reporting: Performing Custom Build Step on c:\id4sdk\source\USF_ID_EDIT\UIE.fr c:\id4sdk\source\USF_ID_EDIT\VCPlugInHeaders.h(33) : error R32: # Error: Could not open include file PluginBuildFlags.h That is saying that the VCPlugInHeders.h file could be found, bot it can't find PluginBuildFlags.h and UIE.fr does not find one of its incudes. When I comment the #include "VCPlugInHeaders.h"-line from UIE.fr, all its headers can't be found. Please help me to fix that problem!! Jochen ... View more

Hi Manan, my VCPlugInHeaders.cpp I can compile sepateretly and while tying to build my Plug-In successfully. There seems to be another lack. Furthermore I can't see any place, where the cph-File is imported into some File/class. Could you please let me know, in which cases the VCPlugInHeaders-Logic is defenitly required and how the References to the *.objand the *h-Files are thansferred from the compiler to the linker. Kind regards Jochen Seliger ... View more

Hi Dirk, after experiencing lots of problems/bugs with XP, VC70 and SDK 4.0.2, we have decided to start with the newest release and port than the Plug-In, if reqiured, backwards. I've tryed the two links, provided be Sanyam, but got 'access denied' errors. What is to do to get a member of the InDesign Family Pre-Release program. That seems to be the prerequisit for getting the SDK. If that will not be tru, please let me know the right steps, to get the SDK for ID CC. Jochen Seliger ... View more