Windows 10 is very well tolerated.
In my previous post, I discussed an overview of the Windows 10 application compatibility and a single application found that worked on Windows 8.1 64-bit, which is not more than 10 64-bit Windows does not work.
which is a really high degree of compatibility, no matter how you look at it, but that's enough ... well not necessarily there are many problems that can cause applications to not work on a new platform and obviously the greater the variation the greater the risk.
What factors affect application compatibility?
There are various factors that can affect application compatibility, generally speaking:
- The age of the application; The older he gets, the less likely it is with a modern operating system and the restrictions in place as UAC, Session 0 Isolation, OS Versioning controls and the more likely will depend on outdated or removed technologies
- work the transition from 32 bits to 64 bits is application compatibility to decrease, there are still many 16-bit applications and components even in applications in circulation
- the platform was developed on Microsoft .Net application-tends to work well because of the platform they are developed on (this is not to say developers can not do bad things, it's just less likely). You would expect that Java would be in the category, but not the sheer number of changes between JRE versions, it is a nightmare breaks in the most complex environments to manage
- The knowledge and skills of software engineer who wrote it
AppDNA can all the problems mentioned above in the detection (ok, except for the skill level software engineer), regardless of whether the application is in the house or not ,
But Windows 10 64-bit and Windows 8 64 bit are highly compatible, so why should I AppDNA?
It is highly unlikely that you have a homogeneous environment where all users are using an operating system image and all its applications in Windows 8.1 64-bit. If they are, then perhaps you are in this great location where you can move only at low risk, or can you?
Perhaps not, if we consider the results further confirmed by a search a little deeper into the AppDNA database, we can see that directly between Windows 7 64-bit and Windows 10 64-bit, there are 3321 PE files missing (or moved), this means there are potentially 3321 files that are to import your applications, and the API calls are obviously not present when these files are missing, or have a non-library loading point.
missing files between Windows 7 moves 64-bit and Windows 10 64-bit: 3321
And when we start a little deeper digging for more subtle changes, where the files are present, but they have special API calls had to be removed, we find that 4052 API calls are missing! Many of them are certainly benign and probably does not support your applications or published not use API calls or do they !?
Missing API calls between Windows 7 64-bit and Windows 10 64-bit: 4052
As usual, there are no guarantees but fortunately Citrix AppDNA a category of algorithms in the OBSOLETE group that applications can recognize that. to depend these files or API calls
it when you import your own customized operating systems AppDNA a delta comparison between them do it automatically would be even better to identify any missing PE file or API calls between the builds, especially important if you high customized builds.
If you are a XenDesktop or XenApp Platinum customers or partners Download AppDNA today you are on Windows 10 to help the migration
0 Komentar