Skip to main content
This topic is closed to new replies. Start a new post to keep the conversation going.
Test Screen NameCorrect answer
Legend
Mar 30, 2018 12:29 AM UTC

Each release of the SDK has a specific release of Visual Studio/Xcode, to match the version used to compile Acrobat. Your plugin becomes part of Acrobat so you must play nice.

An experienced plugin develop can often get things to work with other releases, but if you’re new you may face endless frustration with no way to know if your issues are version incompatibility.

View reply

12 replies

Thermitus30821062peu3
Participant
Jul 1, 2023 12:48 AM UTC

Boa noite

 

Translate
Dan_Korn
Dan_Korn
Inspiring
Apr 5, 2018 8:36 PM UTC

Yes.  Most of the Acrobat SDK is a fairly lightweight "C" interface, where you load host function pointers ("tables," or HFTs) from Acrobat itself, with only a single source file (PIMain.c) that you compile into your plug-in.  There's no C++ interface like in other plug-in SDKs (such as the InDesign SDK), so you don't really have any binary compatibility issues using a different compiler.  We are able to build Acrobat plug-ins using a wide range of compilers, on both Windows and Mac (though the compiler version is not tied as closely to the IDE version in Xcode as it is in Visual Studio).  Currently we use VS2015 and Xcode 4 (with Apple LLVM 4.2), but I know firsthand that VS2005 through VS2015 and Xcode 4 through Xcode 7 work with the Acrobat DC SDK, and I don't see why newer ones wouldn't also work.

Translate
R0b_EvansAuthor
Known Participant
Apr 5, 2018 8:45 PM UTC

Thanks for replying even after I had already marked a correct answer for this post.  With this new information, I will go boldly ahead with my VS2017 with confidence that it will work.

Translate
markm6767785
Participating Frequently
Jul 28, 2018 10:02 PM UTC

I would be interested to learn of your experience with trying VS2017 Rob.  Would really appreciate your guidance as we evaluate this. 

Translate
Test Screen Name
Legend
Mar 30, 2018 7:53 AM UTC

Microsoft make old versions of Visual Studio available. You might consider using a VM to keep each release separate.

Translate
R0b_EvansAuthor
Known Participant
Mar 30, 2018 4:52 PM UTC

Thanks for the advice.  I am building a new development machine with lots of storage, memory and fast graphics.  A VM would work well on that.

Translate
Test Screen NameCorrect answer
Legend
Mar 30, 2018 12:29 AM UTC

Each release of the SDK has a specific release of Visual Studio/Xcode, to match the version used to compile Acrobat. Your plugin becomes part of Acrobat so you must play nice.

An experienced plugin develop can often get things to work with other releases, but if you’re new you may face endless frustration with no way to know if your issues are version incompatibility.

Translate
R0b_EvansAuthor
Known Participant
Mar 30, 2018 1:54 AM UTC

The SDK Version I have is for VS 2013.  I only have access to VS 2017, and I am a C++ noob.  So it appears that my project is screwed and I am screwed.  This is a very big disappointment. 

Translate
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices