🚀 go-pugleaf

I did find the "scripting.rpln" file.  In C# what you have to do is use "Tlbimp.exe" which converts the type definitions found within a COM type library into equivalent definitions in managed metadata format.  

 In your C# code you will compile the new DLL into you code and write some C# code that define a name space and reference a class like follows.  



   using InDesign; 

  class InDesign Class {     static void Main(string[] args) {       Application objIDApp = new Application();       Console.WriteLine(objIDApp.Version);     }   }   

 The error I mentioned above occurs when referencing any properties or methods from the "Application" class. 

 With the .NET SDK an application is included called "ILDASM.exe" (MSIL Disassembler) This app Takes a PE (portable executable) file that contains MSIL (Microsoft intermediate language) code and creates a text file suitable as input to the MSIL Assembler.  The Disassembler will give you a GUI interface to look at all of the Classes and how they were converted.  

When looking at the dll created by "Tlbimp" it appears that InDesign gets converted into a series of "Interfaces" and not "Classes". This is not uncommon to use interfaces but I think that the error I described is the direct result of there being NO classes in this managed metadata format file (DLL).  My guess is that it is inappropriate to use the "scripting.rpln" file to create the managed metadata format. 

 If you have any experts at Adobe that you could speak with I would be interested in hearing there take on this.  Do you know of anyone that uses InDesign scripting through Java or C++? 
 

-Joel