A null-terminated string, such as "Service Pack 3", that indicates the latest Service Pack installed on the system. If no Service Pack has been installed, the string is empty. The major version number of the latest Service Pack installed on the system. For example, for Service Pack 3, the major version number is 3. If no Service Pack has been installed, the value is zero. The minor version number of the latest Service Pack installed on the system. For example, for Service Pack 3, the minor version number is 0.
A bit mask that identifies the product suites available on the system. This member can be a combination of the following values. Relying on version information is not the best way to test for a feature. Instead, refer to the documentation for the feature of interest. For an example, see Getting the System Version. The winnt. Mixing usage of the encoding-neutral alias with code that not encoding-neutral can lead to mismatches that result in compilation or runtime errors.
For more information, see Conventions for Function Prototypes. Version Helper APIs. Skip to main content. This browser is no longer supported. Especially years after the thread originally started. Details required : characters remaining Cancel Submit 1 person found this reply helpful. Bob Valentine. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :.
Cancel Submit. Previous Next. Windows 7 should be 6. If so, you'd get 5. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. HansV, Thanks for your quick response. I appreciate it. In reply to Bob Valentine's post on February 5, Are you sure you're really getting 5. In most cases, there are more direct and robust ways to achieve the right test, and they don't involve either GetVersion Ex or VerifyVersionInfo. Furthermore, with the Windows 10 servicing model, the OS version number itself is becoming less meaningful, and the existing set of Windows Vista, Windows 7, Windows 8, Windows 8.
This change is in the public Windows 10 flights for validation, but all the auxiliary changes such as MSDN, deprecation warnings in headers, updated appcompat guideance, etc. There is always cases where we can't avoid to check the version. For example, I want to use the robocopy utility to synchronize data. Its options change on each new version of Windows.
If I want to use the newer features while keeping a compatibility with Vista, I have no other way but to check the OS version before building my command line. I could check the return value of robocopy but this not documented "Any value greater than 8 indicates that there was at least one failure during the copy operation.
Therefore, I cannot be sure that this is because of an unrecognized switch. Another example. On XP, the behavior is unpredictable and seemingly not desirable at all. So, only one solution: check the OS version. There are always features for which the availability cannot be checked, or in a very bad way.
Therefore, we need to check the OS version. You cannot avoid that. We will always find a way to check the OS version, because a newer OS always presents differences with its previous version. You can only make things more complicated for developers.
The earlier you move away from robocopy the better. It is made for a specific problem, and that problem isn't a sync platform for third party software. If you are looking at a Microsoft solution, there's a Microsoft Sync Framework. Shelling to robocopy is indeed likely to be platform-specific, and perhaps something you should be handling in another way.
The recommended solution is: don't do version checks. That said, all of the VersionHelpers. So the question is: Why are you doing a version check in the first place? There is most likely a better way to get the information you really need directly. We are in this situation. There are a few reasons why we need to know the Operating System version. We need to know the Operating System version for licensing purposes, and the licensing program needs to be able to run on and handle future Operating Systems without a recompile.
We need to be able to detect the Operating System version as we over time no longer support our applications on older Operating Systems. Unless you are specifically trying to prevent running on Windows 8. If it does require Windows 8. So there is no need for us to install our product's driver on these machines.
0コメント