Project

General

Profile

Actions

Support Request #9853

closed

ADTF 3.3.3 compatibility with 3.6.x

Added by hidden over 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Customer:
BOSCH
Department:
Requester's Priority:
Blocker
Support Level:
2nd Level
Resolution:
Solved Issue
Product Issue Numbers:
Affected Products:
Platform:
Windows 10 64bit
Topic:
ADTF::Common
FAQ Links:

Description

Supportanfrage

A few months ago I got the information that the binary built with ADTF 3.3.3 is compatible with every major 3 version:
"The ADTF versions are definetly binary and code compatible along the whole ADTF 3 major version."
Source: https://support.digitalwerk.net/issues/8232
So in theory the 3.3.3 filter should work just fine with 3.6.2. I already found out that the code compatibility is not true at all. The binary seems to work and in theory it should.

Since we would like to move to 3.6.2 I checked the system requirements and I found the following:
"Anyway, loading older adtfplugins build with the former toolchain is not supported !"
Source: https://support.digitalwerk.net/adtf/v3/adtf_html/page_system_requirements.html
Which one is the truth?

Lösung

This is a very combined "problem".
Yes we are binary and code compatible in a major version on each platform.
But you are comparing ADTF 3.3.3 (Windows 7, VS 2015, VC140) with ADTF 3.6.2 (Windows 10, VS 2017, VC141), this means different platforms !
Imho it will run because it should on Windows but we cannot guarantee it because its a Microsoft thing and not a ADTF restriction.
As well as an own plugin maybe uses 3rd party stuff which differs on these platforms.
So we cannot recommend that each older part will work.

They change and support for Windows 10 was mandatory, as well the compiler change regarding Qt/chromium issues, and requested by customer forum.

Sum up:
ADTF 3.6 binary compatible with ADTF 3.3
Windows 10 binary compatible with Windows 7
Qt 5.12 binary compatible 5.9
VS2017/VC141 ABI compatible with VS2015/VC140 (Update3)
Missing different platforms may work but is not recommended and can not be fully guaranteed, only for our delivered components and API/Runtime.
But this does not break thje binary compatible requirements.

Actions

Also available in: Atom PDF