Provide feedback
Saved searches
Use saved searches to filter your results more quickly
Sign up
Appearance settings
The topic you requested is included in another documentation set. For convenience, it’s displayed below. Choose Switch to see the topic in its original location.
To give your app the best chance of getting certified, validate and test it on your computer before you submit it for certification and listing in the Windows Store. This topic shows you how to install and run the Windows App Certification Kit.
For more details on specific tests carried out by this kit, refer to the following topics:
- Windows App Certification Kit tests
- Windows security features test
For a high level look at the certification process, and where the use of this tool fits in, see Certify your app.
Prerequisites
If you are developing a Windows 8 app:
- You must install and run Windows 8 or Windows 8.1.
-
You must install Windows App Certification Kit version 3.1, which is included in the Windows Software Development Kit (SDK) for Windows 8.1.
Note Because it is frequently recommended that you test your app on Windows RT, be sure to also install the Windows App Certification Kit for Windows RT (available as a separate download for Windows RT devices).
If you are developing a Windows 8.1 app:
-
You must install and run Windows 8.1.
-
You must install Windows App Certification Kit version 3.1, which is included in the Windows SDK for Windows 8.1.
Note
Because it is frequently recommended that you test your app on Windows RT, be sure to also install the Windows App Certification Kit for Windows RT (available as a separate download for Windows RT devices).
To run Windows App Certification Kit version 3.1 on a Windows RT machine (Windows 8.1 RT), the kits policy needs to be installed as well. For details on installing the kits policy, see ARM Kit Policy Installation.
Other pre-requisites:
-
You must have a valid developer license for your computer.
See Get a developer license to learn how. -
You must deploy the Windows Store app that you want to test to your computer.
Note If you’re using Visual Studio, you can run the Windows App Certification Kit when you create your app package. See Creating an app package to learn how.
Enabling in place upgrade
The installation of Windows App Certification Kit version 3.1 or higher will replace any previous version of the kit that is installed on the machine.
Instructions
Validate your Windows Store app by using the Windows App Certification Kit interactively
-
From the Start menu, search Apps, find Windows Kits, and click Windows App Cert Kit.
-
From the Windows App Certification Kit, select the category of validation you would like to perform. For example: If you are validating a Windows Store app, select Validate a Windows Store app.
When the Windows App Certification Kit is run for the first time, the UI lists all the Windows Store apps that you have installed on your computer. For any subsequent runs, the UI will display the most recent apps that you have validated. If the app that you want to test is not listed, you can click on My app isn’t listed to get a comprehensive list of all apps installed on your system.
-
Select the Windows Store app you want to test, and then click Next.
-
From the next screen, select the tests you want to run on your Windows Store app and click Next.
The Windows App Certification Kit begins validating the app.
-
At the prompt after the test, enter the path to the folder where you want to save the test report.
The Windows App Certification Kit creates an HTML along with an XML report
and saves it in this folder. - Open the report file and review the results of the test.
Validate your Windows Store app by using the Windows App Certification Kit from a command line
-
In the command window, navigate to the directory that contains the Windows App Certification Kit.
Note
The default path is C:\Program Files\Windows Kits\8.1\App Certification Kit\. -
Enter the following commands in this order:
appcert.exe resetappcert.exe test -apptype windowsstoreapp -packagefullname [package full name] -reportoutputpath [report file name]
where:
[package full name]is the fully qualified name of the package.[report file name]is the fully qualified file name, that includes the file path, of the XML file that the kit will create to contain the test report. -
After the test completes, open the report file named
[report file name]and review the test results.
Note
For more info about the Windows App Certification Kit command line, enter the command appcert.exe /?
Remarks
Testing with a low-power computer
The performance test thresholds of the Windows App Certification Kit are based on the performance of a low-power computer.
The characteristics of the computer on which the test is performed can influence the test results. To determine if your app’s performance meets the certification requirements, we recommend that you test your app on a low-power computer, such as an Intel Atom processor-based computer with a screen resolution of 1366×768 (or higher) and a rotational hard drive (as opposed to a solid-state hard drive).
As low-power computers evolve, their performance characteristics might change over time. Refer to the most current certification requirements and test your app with the most current version of the Windows App Certification Kit to make sure that your app complies with the latest performance requirements.
Windows App Certification Kit tests
Several enhancements were made to the latest version of the Windows App Certification Kit to improve usability:
- Simplified user interface
- General fixes and performance improvements.
- Better integration within Visual Studio for evaluating Windows Store apps.
Tests performed on Windows Store apps
| Test name | Possible test results | Certification requirements tested | OS Applicability |
|---|---|---|---|
|
Crashes & hangs test |
Pass Fail |
Crashes and hangs |
Windows 8 Windows 8.1 |
|
App manifest compliance test |
Pass Fail |
App manifest |
Windows 8 Windows 8.1 |
| Windows security features test |
Pass Fail |
Binary analyzer |
Windows 8 Windows 8.1 |
|
Banned file analyzer** |
|||
|
Private code signing |
|||
|
Supported Windows Store API test |
Pass Fail |
Supported APIs |
The test is applicable to both Windows 8 and Windows 8.1 The updates in Windows App Certification Kit 3.0 and later are applicable only for Windows 8.1 |
|
Performance test |
Pass Fail |
Bytecode generation |
Windows 8 Windows 8.1 |
|
Optimized binding references |
|||
|
Performance launch |
|||
|
Performance suspend |
|||
|
App manifest resources test |
Pass Fail |
App resources validation |
Windows 8 Windows 8.1 |
|
Branding validation |
|||
|
Debug configuration test |
Pass Fail |
Debug configuration |
Windows 8 Windows 8.1 |
|
File encoding test |
Pass Fail |
UTF-8 file encoding |
Windows 8 Windows 8.1 |
|
Direct3D feature level test |
Pass Fail |
Direct3D feature level support |
Windows 8 Windows 8.1 |
|
Direct3D Trim after suspend** |
Windows 8.1 |
||
|
App capabilities test |
Pass Fail |
Special use capabilities |
Windows 8 Windows 8.1 |
|
Windows Runtime metadata validation |
Pass Fail |
ExclusiveTo attribute test |
The test is applicable to both Windows 8 and Windows 8.1 The updates in Windows App Certification Kit 3.0 and later are applicable only for Windows 8.1 |
|
Type location test |
|||
|
Type name case-sensitivity test |
|||
|
Type name correctness test |
|||
|
General metadata correctness test |
|||
|
Properties test |
|||
|
Package Sanity check |
Pass Fail |
Platform appropriate files** |
Windows 8 Windows 8.1 |
|
Supported directory structure check** |
Windows 8 Windows 8.1 |
||
|
Resource Usage test |
Pass Fail |
WinJS bckground task test** |
Windows 8.1 |
|
** indicates the test was newly added for Windows App Certification Kit for Windows 8.1 and is applicable only when you test using the latest kit. |
Testing on ARM devices
If you’re creating an app for Windows RT devices, be sure to check out Debugging and testing on Windows RT PCs. It contains info to help you test apps for these devices.
Related topics
- Windows App Certification Kit tests
Show:
Inherited
Protected
Время на прочтение5 мин
Количество просмотров14K
Shen Chauhan и Andy Wigley рассказывают об обновлении Windows и новом SDK
Пару недель назад мы выпустили новую версию Windows 10 SDK (можно ставить параллельно с предыдущей версией). SDK включает более 200 новых типов и дополнительных методов и свойств для существующих типов.
В этой статье мы расскажем подробнее о некоторых улучшениях в универсальной Windows-платформе (UWP), включенных в SDK:
- Визуальная композиция, эффекты и анимация
- SQLite
- Работа с вводом и пером
- Более эффективная и гибкая установка AppX
- UI и обновления XAML
- Bluetooth и работа по сети
- Работа с сенсорами
- Хранилище устройства
- Windows App Certification Kit (Windows ACK)
- Набор для дизайна (Photoshop)
Визуальная композиция, эффекты и анимация
Мы добавили в SDK новое семейство API — Windows.UI.Composition, позволяющее напрямую работать с базовым слоем UI. Базовый слой UI находится между фреймворком (например, XAML) и графическим слоем DirectX. Мы подготовили набор соответствующих примеров на GitHub. Новый набор API включает:
- Быстрый рендеринг легковесных визуальных элементов в трехмерном координатном пространстве
- Новый декларативный движок для анимации, масштабируемый и включающий новый механизм описания анимаций через выражения и возможность покадровых анимаций, работающих независимо от UI-потока.
- Высокопроизводительная система UI-эффектов, работающая в реальном времени. Эффекты, применяемые к визуальным элементам, могут настраиваться, объединяться в цепочки, а их свойства также могут быть анимированы.
SQLite
Библиотека SQLite теперь поставляется вместе с UWP для решения задач локального доступа к данным, необходимого во всем спектре устройств на Windows 10. SQLite реализует транзакционный движок поддержки SQL-базы данных, не имеющий дополнительных зависимостей и не требующий наличия сервера или специфичных настроек. Разработчики теперь могут напрямую обращаться к SQLite, включенному в SDK вместо самостоятельного включения соответствующей библиотеки в приложение. Руководство по работе с данными было обновлено, чтобы помочь разработчикам разобраться в работе в SQLite в UWP-приложениях.
Работа с вводом и пером
Обновление включает следующие улучшения в работе с клавиатурой и пером:
- Direct Ink для Win32-приложений. API Ink Presenter позволяет Win32-приложениям управлять вводом с помощью пера, включая обработку и рендеринг штрихов через объект InkPresenter, вставляемый в визуальное дерево DirectComposition разрабатываемого приложения. Другими словами, теперь Win32-приложения могут работать с пером также, как и UWP-приложения.
- Перехват доставки событий клавиатуры. Новый класс KeyboardDeliveryInterceptor позволяет приложениям переопределить системный процесс обработки нажатий клавиатуры, включая сочетания клавиш, клавиши быстрого доступа (горячие клавиши), ускоряющие комбинации и клавиши приложений, но исключая комбинации клавиш, связанные с безопасностью (например, Ctrl-Alt-Del и Windows-L), которые система продолжает обрабатывать.
- Межпроцессные цепочки обработки указателей. Доступно через новые события указателей (pointer) – как для UWP-приложений, так и для классических Windows-приложений.
Более эффективная и гибкая установка AppX
Обновление делает установку пакетов приложений на устройствах более гибкой:
- Уменьшено требуемое для установки место. Раньше нам требовался двойной размер пространства на диске по сравнению с объемом самого AppX-пакета для его установки. Так, если пакет весил 1GB, то для установки нам требовалось 2+GB свободного места на диске. Теперь мы запрашиваем заметно меньше дополнительного места: тот же пакет в 1GB подребует 1.1GB пространства на диске для установки.
- Дополнительные диски на десктопе. Дополнительные диски на десктопе теперь поддерживаются для установки приложений, например, вы можете решить ставить приложения на диск D:, изменив место для установки в настройках хранилища. В мобильном сценарии аналогичные настройки позволяют ставить приложения на SD-карту при ее наличии.
UI и обновления XAML
SDK включает несколько обновлений API, чтобы вы могли улучшить опыт пользователей:
- Всплывающие списки. Новые классы JumpList и JumpListItem для работы со стартовым экраном дают возможность приложениям программно управлять всплывающим меню у плитки или иконки в панели задач, включая добавление новых элементов и групп.
- Обновление XAML. Включает возможность указать формат для буфера обмена через обновленный API для RichText, улучшения в навигации в обновленном API для работы с картами, а также улучшения в размере меню по умолчанию.
Bluetooth и работа по сети
В SDK включены следующие улучшения:
- Bluetooth. Новые методы для связывания в классе DeviceInformationPairing позволяют установить или разорвать связь изнутри приложения с опциональными уровнями защиты.
- Sockets. Для разработчиков, использующих WebSockets: методы FlushAsync в MessageWebSocket.OutputStream и StreamWebSocket.OutputStream были реализованы полностью и теперь ожидают завершения ранее вызванного метода WriteAsync. Учтите, что это может привести к появлению исключений в существующем коде, если WebSocket находится в некорректном состоянии при вызове метода FlushAsync.
- Cookies. Новое свойство CookieUsageBehavior было добавлено в существующем классе HttpBaseProtocolFilter. Это позволит разработчикам контролировать, как куки обрабатываются в системе.
Работа с сенсорами
Windows 10 включает ряд улучшений в работе с контекстными сенсорами, позволяющими определять тип активности (например, ходьба, бег, езда на велосипеде или машине), подсчитывать шаги и узнавать высоту и барометрическое давление, а также отслеживать появление пользователя рядом с устройством или его отдаление. Подробнее о работе с сенсорами мы писали в статье «Сенсоры контекста в Windows 10». В дополнение, наша вторая статья описывает некоторые продвинутые возможности работы с сенсорами, включая пакетную обработку данных акселерометра, использование ReadingTransform для поддержки правильной ориентации приложения на различных устройствах и также возможность добавления собственных сенсоров. Таким образом, полный набор всех сенсорных API работает на всем спектре устройств на Windows 10.
Ноябрьское обновление развивает возможности, позволяя использовать сенсоры как фоновые триггеры. Подробности можно узнать из нашего растущего набора примеров работы с устройствами и сенсорами на GitHub.
Хранилище устройства
Разработчики теперь могут более гибко работать с файлами, сохраняя и ассоциируя их с конкретными пользователями:
- С помощью методов CreateFileForUserAsync и CreateFolderForUserAsync можно, соответственно, создавать файлы или папки внутри папки «Загрузки» для указанного пользователя.
- С помощью метода GetLibraryForUserAsync можно получить доступ к известному хранилищу для указанного пользователя.
Windows App Certification Kit (Windows ACK)
Windows App Certification Kit обновился и включает улучшенные тесты. В частности, добавлен тест для предзагрузки приложения (Prelaunch) и поправлены тесты ресурсов и используемых API. Полное описание изменений и известных проблем можно найти на странице WACK.
Набор для дизайна (Photoshop)
Чтобы облегчить проектирование приложений, мы добавили новые шаблоны дизайна UWP-приложений для Adobe Photoshop. Мы также обновили шаблоны Microsoft PowerPoint и Adobe Illustrator и сделали PDF-версию руководств.
Вопросы и отзывы будем рады услышать в твиттере @WindowsDev. Если вы встретитесь с багами или проблемами, используйте инстурмент Windows Feedback и MSDN форумы.
Before you submit your app for
certification and listing in the Windows Store, use the Windows App
Certification Kit (ACK) to test your app and make sure it’s ready for
submission.
The Windows SDK includes the Windows ACK to test your app for the Windows 8 Certification Program and the Windows 7 Logo Program.
Download now
To self-test your app on Windows RT, use the separate Windows App Certification Kit for Windows RT download.
Download now
What’s New
November 16, 2012:
Windows ACK 2.2 is now available; this version is required for app
submissions to the Windows Store as of December 11, 2012. Windows ACK
2.2 includes bug fixes as well as three new tests:
- Optimized binding references (when using bindings, WinJS.Binding.optimizeBindingReferences should be set to TRUE in the app’s JavaScript to otpimize the memory usage).
- Branding validation (apps should not use the default icons generated by Visual Studio or included in the SDK samples).
- Private code signing (remove any private code signing keys, such as .pfx files, from the package).
System requirements
Windows App Certification Kit (Windows SDK)
Note:
the Windows SDK for Windows 8 cannot be installed directly on the ARM
architecture. You can install the Windows SDK on an x86 or x64 platform
to build applications that target the ARM architecture, and then use the
Windows App Certification Kit for Windows RT download to test the app on that platform.
- Supported Operating Systems: Windows 8 (x86 and x64)
- Hardware Requirements:
The complete installation of the Windows SDK requires 10 MB to 1 GB
hard disk space for installation, depending on the features selected.
Windows App Certification Kit for Windows RT
- Supported Operating Systems: Windows RT
- Hardware Requirements:
- 1.6 GHz or faster processor
- 1 GB of RAM (1.5 GB if running on a virtual machine)
- 5.0 GB of available hard disk space
- 5400 RPM hard drive
- DirectX 9-capable video card running at 1024 x 768 or higher display resolution
The software can be uninstalled in the Control Panel. Recommended: Identify fussvc. Important: Some malware camouflages itself as fussvc. Therefore, you should check the fussvc. A clean and tidy computer is the key requirement for avoiding problems with fussvc. Always remember to perform periodic backups, or at least to set restore points. Should you experience an actual problem, try to recall the last thing you did, or the last thing you installed before the problem appeared for the first time. Use the 6 resmon command to identify the processes that are causing your problem.
Even for serious problems, rather than reinstalling Windows, you are better off repairing of your installation or, for Windows 8 and later versions, executing the 7 DISM. This allows you to repair the operating system without losing data. To help you analyze the fussvc. This document was created with Unity 5. For your benefit, it is recommended that you use, at a minimum, Unity 5. Windows Store now has a single place to submit and upload your UWP apps.
You can still target devices using older operating systems, but for this document, we will be focusing on submitting your game as a UWP app to Windows Store. NuGet is the package manager for the Microsoft development platform including. It allows developers to find third-party libraries and add them to projects as dependencies.
You can use NuGet to provide any Windows libraries that you need to use natively. NET Core. In this section, we are going to cover what is required to take an existing Unity game and get it ready for deploying to Windows Store as a Universal Windows Platform UWP game. We will cover the following:.
Getting Windows 8 Applications into the Windows Store
A developer license is no longer required for each device that you want to use to develop, install, or test your app. Instead, you may now enable a device just once for these tasks from the setting for the device. For Windows 10, whether using a desktop, tablet, or phone, you need to enable that device for development under System Settings.
You can find more details on how to do this here. One of the first steps in preparing your game for Unity is to make sure you have the right build settings configured for it. If you choose to, you can also add logo and tile images in the Player Settings window that will be displayed in Windows Store.
Windows App Certification Kit — French
As with many things in building Unity apps for the Windows Store, however, there are multiple ways to accomplish this; you can also defer adding images through the Unity IDE and do it later through Visual Studio instead. Unity 5. Three architectures are supported: ARM, x86, and x In addition, you can use. NET Core 5. Clicking on the Build button in the Build Settings window will prompt you with a Build Windows Store dialog to select a folder for building your game. Once you have selected the folder, Unity will begin building your game, targeting the platform you selected.
This can take several minutes if you have a large game:. A Windows Explorer window should now display the folder containing all the files generated by Unity. In order to sell or distribute your Universal Windows Platform UWP app, you need to create an appxupload package for it. This package facilitates selling your app on Windows Store or distributing it to other users.
When you create the appxupload, another appx package will be generated to use for testing and sideloading. You can distribute your app directly by sideloading the appx package to a device. For Windows 10, you generate one package. Your app is then available to be installed and run on any Windows 10 device. Note: If you need to create an app package for a Windows 8. For more details, see Packaging Universal Windows apps for Windows When you do this, most of the fields in the Packaging tab of the manifest designer will be automatically updated.
The following values are downloaded to the app manifest file for the current project on your local machine:.
Get the Kit
If you override the default package. If you try to associate a custom manifest file with the store, you will see an error message. Creating a custom package manifest is discouraged. Once you have created your app by reserving a name, you can start working on getting it published. The first step is to create a submission. You typically start your submission when your app is complete and ready to publish. However, you can start entering info even before you have written a single line of code.
The submission will be saved in your dashboard so you can work on it whenever you are ready. After your app is published, you can publish an updated version by creating another submission in your dashboard. Creating a new submission lets you make and publish whatever changes are needed, whether you are uploading new packages or just changing details, such as price or category. To create a new submission for an app, click Update next to the most recent submission shown on the App overview page.
Unity provides you with the minimum assets required for submitting an app, but it is recommended that you provide your own images and assets. The following is a screenshot of the Visual Assets section of the Package. To give your app the best chance of being published on Windows Store, or becoming Windows Certified, validate and test it locally before you submit it for certification.
Develop Your Windows 8 App — Resources, Tools and Tips — Hongkiat
This topic shows you how to install and run the Windows App Certification Kit. For more details on specific tests carried out by this kit, refer to the following topics:. Click Next to proceed with the validation steps. Do not be alarmed if you see multiple windows pop up. The tool is simply running your game and performing tests.
These tests can take several minutes to complete. Once the tests have completed, you will be presented with the following window. If the tests failed, you will be able to review them to make corrections and then repeat this process to pass the tests. Here you can review every test and find out what exactly failed and correct the issue.
After you have corrected all the issues and rerun the tests, you should get the following results:. Now that your game is built and uploaded, you need to go into your developer account in order to submit it to the store. Follow the following steps in order to begin the submission process. The Packages page is where you upload all of the package files. You can upload packages for any operating system that your app targets in this step. For details about what a package includes and how it must be structured, see App package requirements. You may also want to learn about…. To upload packages, drag them into the upload field or click to browse your files.
The Packages page will let you upload. Note: For Windows 10, you should always upload the. If issues are detected with your packages while validating them, you will need to remove the package, fix the issues and then try uploading it again.
app certification kit download
For more info, see Resolve package upload errors. In this section, we will be referencing a simple 3D Basketball game written by Jb Evain onstage at Build in less than 20 minutes.
- facebook chat messenger software for mobile free download!
- dragon ball games download for mobile?
- samsung galaxy s5 model number.
- Uninstall and Remove Windows App Certification Kit x64 Step by Step!
- clumsy ninja hack ios ifunbox?
The only external asset you will need to create the game is this Hoop. If you would rather just download the finished project package, Basketball-At-Build. In the next few steps, we will use a game to demonstrate the steps outlined above for getting a game ready for submission to Windows Store. If you are building the game from scratch, you will need to follow these steps. If you have downloaded the completed project, you can skip steps 1 through 8. In the menu, click on File Build Settings… to open up the Build Settings window and make sure that you have a scene selected under the Scenes In Build view.
You will want to ensure that…. Next, click on the Player Settings… button and make sure that the information there is correct.