All geek questions in one place

Can I check the WinRT component DLL?

I am trying to get SQLite to be compatible with WinRT. I switched old calls that WinPT is not supported by new ones. Now that I have a compilation of the project, I would like to confirm that it does not use any of the old calls or API calls that are not supported.

The Windows application certificate set apparently only validates the actual metro application. How can I just check out the WinRT library?

Edit:

It seems that there is an error in the set of application certificates. It does not seem to check reference DLLs. If you move your code to the application, it checks it. In addition, compile-time errors are not always present for calls not supported in the subway. Is there a flag that I need to set in order to catch these errors at compile time? This file is a C file with WinRT extensions disabled for this file only.

+4
source share
2 answers

The issue of not causing compile-time errors for calls not supported in Metro has now been fixed in the Consumer Preview. In addition, the set of application certificates now correctly validates reference DLLs.

+4
source

I really know that Codeplex has an attempt to run SQL Lite for Metro Apps. http://sqlwinrt.codeplex.com/. Depending on the state of the port, you may consider this as an option.

I could see how this would be useful, but I do not know how to check a separate DLL.

However, there are a number of implicit and explicit checks that will take place to give you a very good idea.

If you want to load the application into the repository, the SQL Lite implementation must be part of your package and thus it will be checked during the certification process. The certification process checks all the executables and DLLs in your project and looks for bad APIs. If this is found, certification will fail.

In addition, the Windows 8 SDK that you are compiling has header files that expose only the Win8 Metro APIs, so you should get errors during compilation (it seems you solved this by successfully compiling).

Finally, you work in an isolated environment with your application, and when the API tries to do something that it should not, for example, a trivial example of registry access, you would encounter security / access problems. SYSINTERNALS "Process Monitor" is a great way to observe this in your application by looking at security / access issues during tracing.

I know this is a wide blow to fit your question. Hope this helps.

+1
source

Source: https://habr.com/ru/post/1398289/

More articles:


All Articles