How to get WASDK runtime version?

[HO-COOH]

If I write a Windows runtime component using wasdk, how can I determine the actual runtime version of wasdk?

[DarranRowe]

This all depends.

It seems that for 1.7, the RuntimeInfo runtime class will be available. It is more annoying for 1.6 and older.

For 1.6 and older self contained, the version of the runtime should match the version that it was built with, so the static version is what you query. For 1.6 and older framework dependent, then it is the version of the framework package that you can find. GetCurrentPackageInfo(2)(3) allows you to query for the current dependencies. This also works for unpackaged desktop applications that use the Dynamic Dependencies API, and this includes the Bootstrapper API, to reference the Windows App SDK. If you are using GetCurrentPackageInfo or GetCurrentPackageInfo2, you have to remember to add the PACKAGE_FILTER_DYNAMIC flag.

[HO-COOH]

Why this complicated? Can't I simply walk through all loaded module by using toolhelp32, find the wasdk dll, then read its version string? I thought my way is too complex and there might be a simpler api I don't know of.

[DarranRowe]

Why this complicated?

There is no requirement for the library version numbers to match the package versioning, and they mostly don't. I believe that with the current package, there is only one DLL that matches the package version and this isn't loaded automatically. While the package full name is part of the Windows App Runtime install path, because some applications include it self contained and Windows uses hard links to reduce installation sizes, then you are not guaranteed to see the Windows App Runtime install path. So really the only guaranteed way to get the version that matches the versions reported in the Windows App SDK headers is from reading the package info.

Getting the version from the package graph is also VERY fast, even with a debug build, it took 28μs to iterate through the packages and return the version in tests on my system.

Also, a version of this functionality that can get the version of any package loaded should come in at around 20 lines of C++, even with error checking.

[DarranRowe]

Just to add to my previous post, there are also versions of the Windows App Runtime in which this one library that has a version which matches the package version currently, doesn't have a version resource.

So there is only one method that I know of to easily get a guaranteed distinguishable version for older versions of the Windows App Runtime.