Standard AppDNA reports
Aug 14, 2017
Reports control the analysis that is performed on the selected applications. Each report is made up of a suite of algorithms that relate to a target technology against which the application DNA is evaluated. The algorithms validate the suitability, interoperability, conflicts, and performance of applications in the target environment. Each algorithm identifies applications that potentially have a specific issue on the target platform. Applications that are identified as having this issue are said to trigger the algorithm.
This section provides an overview to the standard AppDNA reports. You can also define your own reports by creating custom reports.
Windows 10
Description |
Tests desktop applications for compatibility with editions of Windows 10 for the x86 and x64 architectures. In order to reduce the number of false positives in Windows 10 migration reports, algorithms trigger only when the specific legacy and target OSs introduce the break. For example, algorithms that trigger between Windows XP and Windows 7 because a component was removed in Windows 7 will also trigger between XP and 10 but do not trigger when analyzing between Windows 7 and 10. The assumption is that if your application is already working on Windows 7, it is not a real issue. |
Restrictions | AppDNA does not support the import or testing of Windows Store apps, nor compatibility testing for Windows RT. The Windows 10 report tests the compatibility of traditional Windows desktop applications, such as applications that are based on the Windows API (Win32 API). |
OS images | Analyzes against the legacy and target OS images |
Windows 8/8.1
Description | Tests desktop applications for compatibility with editions of Windows 8/8.1 for the x86 and x86-64 architectures. |
Restrictions | Windows 8 introduced a new application run-time environment called the Windows Runtime (WinRT). Applications written for this environment are called Windows Store apps and they work on x86-64 editions of Windows 8/8.1 and editions of Windows 8/8.1 (such as Windows RT) that run on tablets and other devices that are based on ARM chips. AppDNA does not support the import or testing of Windows Store apps, nor compatibility testing for Windows RT. The Windows 8/8.1 report tests the compatibility of traditional Windows desktop applications, such as applications that are based on the Windows API (Win32 API). |
OS images | Analyzes against the legacy and target OS images |
Windows 7 SP1
Description | Tests desktop applications for compatibility with Windows 7 SP1. |
OS image | Analyzes against the legacy and target OS images |
Windows Server 2016
Description | Tests desktop applications for compatibility with Windows Server 2016. |
Restrictions | The Windows Server 2016 report tests the compatibility of traditional Windows desktop applications, such as applications that are based on the Windows API (Win32 API). This report does not test the compatibility of Windows Store apps. |
OS image | Analyzes against the legacy and target OS images |
Windows Server 2012/2012 R2
Description | Tests desktop applications for compatibility with Windows Server 2012/2012 R2. |
Restrictions | The Windows Server 2012/2012 R2 report tests the compatibility of traditional Windows desktop applications, such as applications that are based on the Windows API (Win32 API). This report does not test the compatibility of Windows Store apps. |
OS image | Analyzes against the legacy and target OS images |
Windows Server 2008 R2 SP1
Description | Tests desktop applications for compatibility with Windows Server 2008 R2 SP1. |
OS image | Analyzes against the legacy and target OS images |
App-V
Description | Tests desktop applications for suitability with Microsoft Application Virtualization (App-V) 4.5, 4.6 SP1, or 5.0. |
OS image | Does not analyze against an OS image |
XenApp Hosted
Description | Tests desktop applications for suitability for deployment in a shared server-hosted environment, such as through XenApp 6and later, XenDesktop 7, or Remote Desktop Services (formerly known as Terminal Services). An application deployed in this way is presented to the user as if it were running on the user's device, but all user actions, such as keystrokes and mouse actions, are relayed back to the application hosted on the server. Potentially many users can use each application simultaneously. This poses a particular set of challenges. Important: When you are moving to a XenDesktop environment from another system, we recommend that you use the XenDesktop Adoption solution instead of the XenApp Hosted report. The XenDesktop Adoption solution provides a more complete picture of application compatibility with XenDesktop based on your current environment. The XenApp Hosted report only indicates if an application that already runs on a server platform will work with XenApp. |
OS image | Does not analyze against an OS image |
Internet Explorer
Description | Tests web applications for compatibility with 32-bit or 64-bit versions of Internet Explorer 7.0, 8.0, 9.0, 10.0, and 11. |
Restrictions | The Internet Explorer 11 and 10 algorithms test compatibility with the desktop browser only and not the Windows Store app style UI that is optimized for touch devices. |
OS image | Analyzes against the target OS image |
Firefox
Description | Tests web applications for compatibility with all versions of Firefox from Firefox 5 to Firefox 9. Unlike the IE report, you do not need to configure the Firefox report with a specific version. This is because Firefox is a standards-based browser and as such variations between versions tend to be minor. |
OS image | Analyzes against the target OS image |