Article View: adobe.scripting.indesign
Article #14856Re: InDesign Scripting Guide for InDesign CS
From: Jim_Schuyler
Date: Wed, 14 Jan 2004 19:57
Date: Wed, 14 Jan 2004 19:57
3 lines
1217 bytes
1217 bytes
Oskar - I'm doing a similar thing - moving from InDesign 2.0 to InDesign CS (3.0) and scripting from Visual Studio .NET. I was able to script InDesign 2.0 just fine from VB and it worked great. Then my trial license ran out and I bought InDesign CS which I installed. The instructions in the guide (see the other responses to your query) show how to load the "Adobe InDesign 3.0 Type Library" to VS-dot-NET (as a "resource"), but VS complains that they're not a COM component. Have you tried this and have you run into this same problem?
Technical Details
Message-ID:
<2ccf5907.4@webx.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news2.google.com!news.maxwell.syr.edu!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!webxReferences:
<2ccf5907.-1@webx.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f939a,798d7fabd6a8c70d X-Google-Attributes: gidf939a,public X-Google-ArrivalTime: 2004-01-14 12:08:31 PST From: Jim_Schuyler@adobeforums.com Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news2.google.com!news.maxwell.syr.edu!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!webx Newsgroups: adobe.scripting.indesign Subject: Re: InDesign Scripting Guide for InDesign CS Message-ID: <2ccf5907.4@webx.la2eafNXanI> Date: Wed, 14 Jan 2004 11:57:10 -0800 References: <2ccf5907.-1@webx.la2eafNXanI> Lines: 9 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit