Creating a Release Build

[danielb1969023]

Help! I have used the Basic example in the SDK as a basis to create my plug-in, it works fine on my machine so I built it to put on another machine, and discovered because it was in debug mode, it was using the debug version of the C++ libraries which aren't distributable, however when I change it to a release build then it just doesn't appear as an add-in (It is signed and reader enabled).

I don't know what I am missing \ what I should be doing in get this to work, it has been ages since I have done anything in C++ so the many many options in the project properties are lost in time.  I have spent nearly 4 days this and not made any progress.  Can you help? Or at least point me some areas to check? People to ask.

Thanks in advance.

Danny Banks

[Bernd Alheit]

Will the release plug-in loaded in Adobe Acrobat?

[danielb1969023]

Nope not in that either, sadly.

[Bernd Alheit]

You can check your plug-in with this:

Dependency Walker (depends.exe) Home Page

[danielb1969023]

Yes I have done this, and that's how I discovered it was dependant on the debug version of the DLL. 

Are you trying to say you think there might be another dependency missing? would Adobe Acrobat not produce an error, or log if this is a problem?

[Bernd Alheit]

Adobe Acrobat will not produce a error message.

[danielb1969023]

Nope no missing dependancies.  So what to try next?  I am sure it's something to do with the property settings, but alas don't know enough about where I should be looking.

[danielb1969023]

any more ideas anyone, I am banging my head against a brick wall here.

[Bernd Alheit]

Did you test the plugin with Adobe Acrobat on the other machine?

[danielb1969023]

Yep same results on all machines.

[Bernd Alheit]

In the init part of the plugin you can insert some output code to a log file.

[danielb1969023]

I tried a simple msgbox to start with, and in debug build it worked fine but in release build nothing, so I am guessing this would indicate it isn't hitting the init section which would explain why it isn't displaying, what remains unknown is WHY would it not be running the init section.

[Test Screen Name]

1. Be sure the extension name returned by PIHandshake is unique and includes your company prefix.

2. You say you have verified there are no dependencies. How exactly did you do that? Did you install the C++ release runtime?

[danielb1969023]

1)  Think so but will double check that.

2)  Yes I have the runtime installed (and used the dependency to check that none ot them were mssing).

D

[Test Screen Name]

Which dependency check?

[danielb1969023]

1) It is currently set to "TMS:LawManPDFPlugin"

2) I used Microsft Dependancy Walker... which confirmed it was using the runtime version of the files, but as it was not displaying so whilst a win, still doesn't work.

[lrosenth]

Developer prefixes MUST be four characters in length. They MUST also be registered with Adobe.

Yours (TMS) doesn’t qualify for either.

(NOTE: this isn’t your problem with loading – but it is a problem)

[danielb1969023]

Thanks, wasn't aware of either, Adobe didn't mention anything when I applied for the Reader license, will investigate. 

Any ideas on the not loading? Anyone?

[danielb1969023]

Irosenth,

I have been trying to locate the facility to register for a developer prefix but can't seem to find it anywhere can you point me in the right direction.

D

[Karl Heinz Kremer]

Go to PDF Technology Center | Adobe PDF Technology Center and look for the link to "PDF Registry".

[Test Screen Name]

1) Should be fine, a classic problem is adapting a sample, without changing this.

2) Sounds OK. A thought: does it use any private DLLs? If so it's no use putting them in the plug_ins folder with the plug-in.

[danielb1969023]

It uses a Broker which uses an External DLL, but in itself no.

(The Broker has the external files with it).

I am so new to PDF plugins (and not used C++ in far too many years (I am a vb.net guy)). Can't help but feel there is something fundamental I am missing.

So frustrating... any ideas?

[Test Screen Name]

So long as the broker isn't in the same folder: the PLUG_INS folder isn't added to the Windows search order.

Did you put your message in the PIHandshake routine, at the top, using MessageBox (not AVAlert)?

[danielb1969023]

Yep that is exactly where I put it, built it on debug one message box, release nada.

D

[Test Screen Name]

I don't have much idea now, but let's confirm your symptoms/do a test. Does the problem happen when all of these apply.

1. Release build as a set up by Adobe's project, not modified settings

2. NOT Reader enabled.

3. Testing on SAME machine as build, SAME machine as worked with Debug build

4. Debug and all other custom plug-ins removed.

5. Installed to Acrobat PRO not Reader.

6. Confirmed running PRO.

7. Confirmed Acrobat NOT RUNNING using Task Manager (not just status bar)

8. Confirmed keyboard not touched while Acrobat started.