Compilation Warnings

A forum for questions or concerns related to the PDF-XChange Core API SDK

Moderators: Tracker Support, TrackerSupp-Daniel, Chris - Tracker Supp, Vasyl-Tracker Dev Team, Sean - Tracker, Tracker Supp-Stefan

Forum rules
DO NOT post your license/serial key, or your activation code - these forums, and all posts within, are public and we will be forced to immediately deactivate your license.

When experiencing some errors, use the IAUX_Inst::FormatHRESULT method to see their description and include it in your post along with the error code.
Post Reply
whoit
User
Posts: 271
Joined: Tue Jul 07, 2015 3:30 pm

Compilation Warnings

Post by whoit » Wed Jun 27, 2018 12:49 pm

I'm getting a lot of Warnings (16) when I compile in Visual Studio 2017 (all current).

I get two basic kinds of warnings:
Severity Code Description Project File Line Suppression State
Warning Processing COM reference "PDFXCoreAPI" from path "C:\Program Files (x86)\Tracker Software\Core API SDK\Bin\PDFXCoreAPI.x86.dll". The type library importer could not convert the signature for the member '_CRYPT_BIT_BLOB.pbData'.


and:
Severity Code Description Project File Line Suppression State
Warning Processing COM reference "PDFXCoreAPI" from path "C:\Program Files (x86)\Tracker Software\Core API SDK\Bin\PDFXCoreAPI.x86.dll". At least one of the arguments for 'IPXS_PDFVariant.GetString_Unsafe' cannot be marshaled by the runtime marshaler. Such arguments will therefore be passed as a pointer and may require unsafe code to manipulate.


Even though these don't appear to affect the execution of the code, can you tell me how to fix these?

Thanks.

User avatar
Roman - Tracker Supp
Site Admin
Posts: 265
Joined: Sun Nov 21, 2004 3:19 pm

Re: Compilation Warnings

Post by Roman - Tracker Supp » Wed Jun 27, 2018 11:20 pm

Hello,
We use TLB (COM Type Library) format as a universal description of our SDK interfaces. Most programming environments can translate TLB into their own native representation but the complete translation is not possible for all languages due to limitations of some languages.
In your case .NET TLB importer cannot translate some our SDK types into .NET constructs.
If you are uncomfortable with these warnings you can generate .NET interop assembly for our SDK manually, with warnings suppressed. Add this command to the pre-build event command line of your project. E.g.:

Code: Select all

tlbimp.exe PDFXCoreAPI.x64.dll /out:PDFXCoreAPI.x64_interop.dll /silent
(set correct paths for input and output binaries).
Tracker Software Products

Please ZIP any files uploaded to this forum or they will not be posted !
You may also use a RAR or 7Z archive format

whoit
User
Posts: 271
Joined: Tue Jul 07, 2015 3:30 pm

Re: Compilation Warnings

Post by whoit » Tue Jul 03, 2018 11:45 am

Great! Thanks for the info.

User avatar
Sasha - Tracker Dev Team
User
Posts: 4076
Joined: Fri Nov 21, 2014 8:27 am
Contact:

Re: Compilation Warnings

Post by Sasha - Tracker Dev Team » Tue Jul 03, 2018 12:13 pm

:)
Join us at Google+:
https://plus.google.com/+PDFXChangeEditorTS
Subscribe at:
https://www.youtube.com/channel/UC-TwAMNi1haxJ1FX3LvB4CQ

Post Reply