PDFviewerSdk deployment at the client

[adntES]

Hi team !, When i was manipulating the new functionnality, i realize that some files is obligated on the client side.
The both files i found was of course the PDCFview.exe and the language folder.
I wondering if theses file are mandatory on the client side to make the viewer work.
If so, do you have any kind of tips , system or guide that may easily deploy the app on the client side ?

Thanks.

[John - Tracker Supp]

We reccomend you use our deployment installer for distribution located here :

www.tracker-software.com/PDFXV_dev.zip

It can be called silently as required with various switches.

[adntES]

When we purchase the full license of ActiveX ,what do we obtain? a package installer for the client that is register for a retail version and then we can just reference the dll where is installed?

If so, we really want to install it silently to a precise path of our application. Do you guys include a guide for this? if not could you help us to acheive this?

Plus, does Registration-Free COM is important in the process of installation. Do you provide any guide of deployment and installation so we are sure that everything will not crash ^^

[John - Tracker Supp]

Hi,

if you dont wish to use our installer - you just need to include these 3 files (below) and the ActiveX no longer requires registration :
Required files :

PDFXCview.exe
PDFXCviewAx.dll
Resource.dat

Further - Language files should be placed in a sub folder below the files above called : 'Languages'

to ensure all are accessible

and thats it

[adntES]

Wow thanks and you sure that activeX no longer requires registration for any OS ?

[John - Tracker Supp]

Yes - I am indeed, provided you are using a recent release.

[adntES]

I supose that the PDFXV_dev you gave me is the most recent version ? or the last SDK provided on website ?

[John - Tracker Supp]

That link always provides the latest available release.

[adntES]

AWESOME BRO!!

[John - Tracker Supp]

[adntES]

I just read the PDF-XChange Viewer SDK document , and i wondering about the license expiry and the distribution declaration.

If we buy the 25k CLDP viewer SDK , that mean that the license won't expire unless we don't provide the declaration distribution annually right?.

Plus, i really wondering about the client license. When we send the required files to the client does the registration license is automatic or the client have to register the key somewhere??

[Paul - PDF-XChange]

Hi adntES,

there is no time limit on the use of the 25,000 licenses on the CDLP.

It is your responsibility to track the numbers of your application installation. The serial key we provide you is injected into your source code and compiled into your client application using a function (SetDevInfo) so your end user never needs to register this in any other way.

hth

[adntES]

Hi adntES,

there is no time limit on the use of the 25,000 licenses on the CDLP.

It is your responsibility to track the numbers of your application installation. The serial key we provide you is injected into your source code and compiled into your client application using a function (SetDevInfo) so your end user never needs to register this in any other way.

hth

So we need to set the serial key with the function setdevinfo in our source code right ?

[Paul - PDF-XChange]

yup

[adntES]

I can understand that is our responsability to check the number of workstation, just to be clear do we have an obligation to make a declaration of distribution annually?

Plus, if a client reinstall the application does it count for a +1 workstation

thanks

[John - Tracker Supp]

We say periodically - which is about every 12-18 months or when a major new release is issued and requries a serial number update.

Whilst we dont expect 'perfection' in the declaration we do expect it should fairly reflect the distribution within 5% (+/-) or so.

HTH

[adntES]

We say periodically - which is about every 12-18 months or when a major new release is issued and requries a serial number update.

Whilst we dont expect 'perfection' in the declaration we do expect it should fairly reflect the distribution within 5% (+/-) or so.

HTH

Ok, if a major release is required and required a serial number update does we loose the license from the actual version on our application?

Does the major update count in the 1 year subscription of update ?

Actually when we use the setdevinfo in source code and and then compile it to our client. Does each time the program will pass through this line code will event a viewer client distribution license ?

Thanks for replying so fast!

[Stefan - PDF-XChange]

Hello adntES,

Does the major update count in the 1 year subscription of update ?

Yes it does - you will receive the new version key for free but the number of CDLPs already distributed will not be updated back to 25000

Ok, if a major release is required and required a serial number update does we loose the license from the actual version on our application?

You do not lose the license, and if you offer your existing customers an update to a newer version of your product that uses our new SDK, this will not count as new distributions so the CDLP does not need to be updated.

Actually when we use the setdevinfo in source code and and then compile it to our client. Does each time the program will pass through this line code will event a viewer client distribution license ?

You are probably implementing some sort of license counting in your own application and the easiest would probably be if you keep your counting and ours consistent. We count our end user distributions as new licenses only when a new customer purchases our products or upgrades to a bigger package, so reinstallations (or calls to setDevInfo) should not be your main way of counting.

Hope this clarifies the situation a bit.
Best,
Stefan

[adntES]

Hello adntES,

Does the major update count in the 1 year subscription of update ?

Yes it does - you will receive the new version key for free but the number of CDLPs already distributed will not be updated back to 25000

Ok, if a major release is required and required a serial number update does we loose the license from the actual version on our application?

You do not lose the license, and if you offer your existing customers an update to a newer version of your product that uses our new SDK, this will not count as new distributions so the CDLP does not need to be updated.

Actually when we use the setdevinfo in source code and and then compile it to our client. Does each time the program will pass through this line code will event a viewer client distribution license ?

You are probably implementing some sort of license counting in your own application and the easiest would probably be if you keep your counting and ours consistent. We count our end user distributions as new licenses only when a new customer purchases our products or upgrades to a bigger package, so reinstallations (or calls to setDevInfo) should not be your main way of counting.

Hope this clarifies the situation a bit.
Best,
Stefan

I understand, but how do you guys count the number of OUR client license so we do not overflow the CLDP?
If you do, do you check each time we call the function SetDevInfo ? i just worry that each time we call the function you guys accumulate client license from our app.

If not i understand that part of the agreement and distribution of declaration.

By the way, what does the setdevinfo on the client side. Does each time the fucntion is called you guys add it to the register?.

Thanks!!!

[John - Tracker Supp]

There is no recording on our part and no 'call home' feature etc if that is what you are concerned about - this is done entirely on trust.

But - I should advise we do have a member of staff who's job it is to look for license abuse both in terms of the type of applications developed and also 'sniff out' license abuse - so whilst we do nothing nefarious - we are aware that not all trust is rewarded with trust and we do investigate where we believe our good will and trust is not being met with the same - and as a last resort where reliable figures are not supplied we will block a serial number form updates/upgrades until resolved - either amicably or legally, we are pleased to say we have never yet had to resort to the latter.

Hope that helps

[John - Tracker Supp]

I should also advise you there is a bit more required if you do not register the AtiveX than I first suggested - a colleague has informed me we need to add more detail - he will follow up here a bit later with more detail.

Of course using our installer is still the prefered and simplest method for all dev's

[Vasyl - PDF-XChange]

Hi, adntES.

...how do you guys count the number of OUR client license so we do not overflow the CLDP?
If you do, do you check each time we call the function SetDevInfo ? i just worry that each time we call the function you guys accumulate client license from our app.

On first loading your end-user app. On the target client you must call the our ctrl.SetDevInfo with your valid license info (pass your private key and dev-code for this SDK) to hide demo label on the pages view - diagonal text on the pages, and to skip placing other demo labels to document during saving of document to file/stream by our control. We don't count your license number in SetDevInfo - you may call it any number times, one recommendation only - call it one time for one run-time instance of our ActiveX-control and before opening any documents by it.

And about the potential misunderstanding John mentioned: our SDK Help has a section "ActiveX Control Registration" - here is info about the methods of installation for the ActiveX on the target client system control only - it will be renamed to "ActiveX Control Installation" in the future.

Also you may use the ActiveX without the full installation on the target system - by creating two special manifests (xml files) and placing them in the folder with our SDK-components - see the short description in our SDK-Examples, sub-folder - "Registration-Free COM".

Also attached here for convenience

Best
regards.

[adntES]

thanks

[John - Tracker Supp]

[adntES]

Hi, adntES.

...how do you guys count the number of OUR client license so we do not overflow the CLDP?
If you do, do you check each time we call the function SetDevInfo ? i just worry that each time we call the function you guys accumulate client license from our app.

On first loading your end-user app. On the target client you must call the our ctrl.SetDevInfo with your valid license info (pass your private key and dev-code for this SDK) to hide demo label on the pages view - diagonal text on the pages, and to skip placing other demo labels to document during saving of document to file/stream by our control. We don't count your license number in SetDevInfo - you may call it any number times, one recommendation only - call it one time for one run-time instance of our ActiveX-control and before opening any documents by it.

And about the potential misunderstanding John mentioned: our SDK Help has a section "ActiveX Control Registration" - here is info about the methods of installation for the ActiveX on the target client system control only - it will be renamed to "ActiveX Control Installation" in the future.

Also you may use the ActiveX without the full installation on the target system - by creating two special manifests (xml files) and placing them in the folder with our SDK-components - see the short description in our SDK-Examples, sub-folder - "Registration-Free COM".

Also attached here for convenience

Best
regards.

Renaming correctly and drag and drop in the app folder doesn't work,, i suppose i have to generate it but i don't see any option in visual studio 2003 to generate a manifest.

[Vasyl - PDF-XChange]

Hi, adntES.

You may simply copy both manifests from our examples folder to your application folder, rename the client.exe.manifect to <YourProgramName>.exe.manifest and change the value of "assemblyIdentity/name" attribute from stub "Client" to real - "<YourProgramName>". Note: the your program folder should contain:
<YourProgramName>.exe
<YourProgramName>.exe.manifest
PDFXCviewAx.X.manifest
PDFXCviewAx.dll
PDFXCview.exe
resource.dat

Note2: before adding our control to your form in the VStudio resource-editor you must register(install) in the standard way (pg 13-14 of SDK help). After this you will be able to simply add it on your form and use it during development. After developing you may then unregister(uninstall) it from your system and it will continue to work using the specified manifests. So, your program installer can simply copy both manifests to the target folder on the client's machine and our control should work correctly without any standard installation on the target system...

HTH.

[adntES]

Hi, adntES.

You may simply copy both manifests from our examples folder to your application folder, rename the client.exe.manifect to <YourProgramName>.exe.manifest and change the value of "assemblyIdentity/name" attribute from stub "Client" to real - "<YourProgramName>". Note: the your program folder should contain:
<YourProgramName>.exe
<YourProgramName>.exe.manifest
PDFXCviewAx.X.manifest
PDFXCviewAx.dll
PDFXCview.exe
resource.dat

Note2: before adding our control to your form in the VStudio resource-editor you must register(install) in the standard way (pg 13-14 of SDK help). After this you will be able to simply add it on your form and use it during development. After developing you may then unregister(uninstall) it from your system and it will continue to work using the specified manifests. So, your program installer can simply copy both manifests to the target folder on the client's machine and our control should work correctly without any standard installation on the target system...

HTH.

I was able to make manifest file work on my workstation. If i remove the manifest all stop working but if i put the manifest files all work perfect. So i tryed to test it on a client workstation. I take the app folder and the both manifest files, the controler doesn't worked on the clietn station. It's seem the application doesn't find the dll... If i regsvr the dll all work perfect...

[John - Tracker Supp]

Hi,

Yes - obviously if you remove the manifest files - your app will stop working !

Did you change the values in your manifest files as outlined in the previous post ?

If so - please zip and upload your manifest files so we can take a look and advise and also advise the install folder location on your clients work station (not yours) where the application fails to work unless registered. If using a manifest correctly using regsvr shouold not be necessary if done correctly and you are using a recent release (note this option was only added around 5 builds ago)

[adntES]

Hi,

Yes - obviously if you remove the manifest files - your app will stop working !

Did you change the values in your manifest files as outlined in the previous post ?

If so - please zip and upload your manifest files so we can take a look and advise and also advise the install folder location on your clients work station (not yours) where the application fails to work unless registered. If using a manifest correctly using regsvr shouold not be necessary if done correctly and you are using a recent release (note this option was only added around 5 builds ago)

Here is the manifest!!!

[Vasyl - PDF-XChange]

Hi, adntES.

Your manifests are correct.. Thanks.

We cannot reproduce any problem with our manifest tests on all out test machines.
What is client's OS exactly? Note: this method does not work in a system which is below WinXP (look for details: http://msdn.microsoft.com/en-us/library/ms973913.aspx).
Also you may send us simple example for trouble reproducing...

Best
Regards.

[adntES]

Hi, adntES.

Your manifests are correct.. Thanks.

We cannot reproduce any problem with our manifest tests on all out test machines.
What is client's OS exactly? Note: this method does not work in a system which is below WinXP (look for details: http://msdn.microsoft.com/en-us/library/ms973913.aspx).
Also you may send us simple example for trouble reproducing...

Best
Regards.

Well, do you remember that i did a dll from the wrapper so we don't get any error in developement with vs2003?

The dll is about the viewer control maybe this can be the problem ?? i add the dll as zip maybe u can help me if i have to do a manifest with this.. because the controller is done with this dll ..

[Vasyl - PDF-XChange]

Hi, adntES.

It did not help us...
Please send us the siiimple example program (exe) with sources for investigation. Thanks.
May be you should create manifest for your wrapper dll...

Best
Regards.

[adntES]

Do you have any guide of good example of how to make manifest??

For now we program a shell and we execute the register command on client side. We ,of course, asking him to accept administrator right for executing this command only. I hope to find another way because i don't like to involve user in this type of thing. It's not the bullet proof way...

[Corwin - Tracker Sup]

Hello adntES,

Try to add additional manifest file "AxPDFXPL2003.dll.manifest" (which should be copied from "Client.exe.manifest").

HTH.