x64 registration-free deployment

[uMarko]

I was able to do a registration-free deployment of the C version of FullDemo to Windows XP x86. But I have trouble doing it to Windows 7 x64.

I installed PDF-XChange Viewer ActiveX SDK 2.5.201 using pdfvActiveXSDK.exe. Then I am following the procedure that I see in C:\Program Files\Tracker Software\PDF-XChange Viewer SDK\Examples\Registration-Free COM\Readme.txt. I am deploying the following files:

FullDemo.exe (C version, I built it with VS10SP1x86)
FullDemo.exe.manifest (modified to say name="FullDemo")
PDFXCview.exe (x86 version)
PDFXCviewAx.dll (x86 version)
PDFXCviewAx.X.manifest
resource.dat (x86 version)

This works when I move these 6 files to a Windows XP x86 machine. But not for Windows 7 x64. I tried replacing PDFXCview.exe, PDFXCviewAx.dll, and resource.dat with the x64 versions that you supplied, but it still does not work.

Could you tell me how to do registration-free deployment to x64?

[uMarko]

Tracker Support, could help me out here?

[Vasyl - PDF-XChange]

Hi, uMarko.

This works when I move these 6 files to a Windows XP x86 machine. But not for Windows 7 x64. I tried replacing PDFXCview.exe, PDFXCviewAx.dll, and resource.dat with the x64 versions that you supplied, but it still does not work.

In this case - what version of FullDemo(C++) you have used? x86 or x64?
Note: FullDemo(x86) will not work with PDFXCviewAx.dll(x64)/PDFXCview.exe(x64). The x86-client requires the x86 COM-server and x64-client - x64 COM-server...

Also, we will check it again to be sure if all is OK and let you known if something is wrong...

Best
regards.

[uMarko]

I am using the x86 version of FullDemo. I would like to deployment it registration-free to both x86 and x64 workstations.

[Vasyl - PDF-XChange]

Hi, uMarko.

Please open the 'FullDemo' project. Go to project-preferences and change one option:
[Configuration Props/Manifest Tool/Input and Output/Embed Manifest]
from Yes to No. Rebuild 'FullDemo' project and try your deployment(all should be x86) with new 'FullDemo.exe'.

HTH

[Vasyl - PDF-XChange]

Look for some improved client-manifest file (added support of current windows-theme).

[uMarko]

Vasyl,
I rebuilt with Embed Manifest=No. I did this from my development machine running Windows 7 x86 and VS2010SP1.

I then took the resulting FullDemo.exe, and added your replacement FullDemo.exe.manifest file, and deployed them alongside x86 versions of
PDFXCview.exe (x86 version)
PDFXCviewAx.dll (x86 version)
PDFXCviewAx.X.manifest
resource.dat (x86 version)

But I have the same results as before. This is what happens when I deploy to:

Windows XP SP3 x86 – FullDemo.exe works well.
Windows 7 SP1 x64 – nothing happens when I click on FullDemo.exe
Windows Vista SP2 x64 – nothing happens when I click on FullDemo.exe

Marko

[Vasyl - PDF-XChange]

Strange... We cannot reproduce any trouble on our Windows 7 SP1 x64, it works well...
Please try my deployment...

[uMarko]

I found my problem, I set Embed Manifest=No for Debug, but not Release. I fixed it in Release. Now my the FullDemo.exe that I built is working in registration-free deployment mode on my x64 platforms (Windows 7 and Vista), using your special FullDemo.exe.manifest file.

Tell me, will the publicKeyToken value of "6595b64144ccf1df” that you placed into the FullDemo.exe.manifest file work for all C++ programs that I build that call on PDF-XChange Viewer (PDFXCview.exe)?
~ Marko

[Vasyl - PDF-XChange]

Tell me, will the publicKeyToken value of "6595b64144ccf1df” that you placed into the FullDemo.exe.manifest file work for all C++ programs that I build that call on PDF-XChange Viewer (PDFXCview.exe)?

Yes, for all client-programs. Details about 'dependency/dependentAssembly/publicKeyToken' attribute:
http://msdn.microsoft.com/en-us/library/0ecdhtes.aspx

[uMarko]

Will it change in future new versions of PDFXCview.exe?

[Vasyl - PDF-XChange]

This attribute is only for safe/correct AnyClientApp <-> Microsoft.Windows.Common-Controls dependency.
The dependency to 'Microsoft.Windows.Common-Controls' is used for enabling of current windows-theme for your application.
You can remove this dependency but your application will take 'old' view (like in Win2000). This dependency is not related to our SDK, but to system.
So, it is not going to change in the future.

[uMarko]

You did a great job for me today. Diakuyu!
uMarko

[Vasyl - PDF-XChange]