When I want to certify my application (Metro application) with the Windows App Certification Kit, I click on store and when the Windows App Certification Kit is launched it goes into preparing to validate app and then I get the error message:
The Windows App Certification Kit experienced the following failure while validating your app.
The {0} cannot continue testing since the specified Windows App store was was not found. Please verify that the packagefullname is correct"
How can the packagefulname not be correct since I am not the one that typed it? I use the GUI in VS 2012.
When launch the command Get-AppxPackage > out.txt in power shell I can see that my app has a package full name so even when I try to launch the command prompt
.\appcert.exe test -apptype metrostyle –packagefullname XXXXXXXXXX_neutral__823pgb98jhb94 -reportoutputpath c:\temp\MyWACKReport.xml
It says that the package full name must be specified with is the case so I really don't understand. What can I do so that my application can pass Windows App Certification.
My machine: Windows 8 Pro x64 with VS 2012 ultimate
Did you install the application prior to running the certification kit?
It is somewhat annoying that appcert.exe can't install a package itself. (Which is why we developed some tooling to do that for us, hopefully we'll open-source it soon...)
Related
Here's the setup:
I'm trying to connect / deploy to a Motorola Windows Embedded Compact 7 device from VS 2008. The development machine VM is Windows XP (it has tools and SDKs going back to eVC3 on it that will not run on anything newer). It is therefore running ActiveSync as opposed to WMDC. Basic RAPI seems to be working as I can browse the device file system, ect via ActiveSync. This developemnt system works successfully with dozens of other devices, but this might be the first CE 7 device. And again, the error message was simply "The bootstrap could not be loaded".
I'd appreciate any tips on getting a successful connection to the CE 7 device working.
I had exactly the same problem. The solution for me was to install the SDK for the pda. Mine was MC32N0.
You can find the sdk here
I am developing a C#/XAML METRO Application I created the package which generated the Add-AppDevPackage.ps1 and all other files from VS2012 but:
I wanted to know how to deploy this package in real device for testing in Surface RT tablet?
Option 1: Take that folder containing the .appx file and copy it to wherever you need to deploy it. then right click on the .ps1 script and select "run with powershell", which will install the package on the other machine
Option 2: download the remote debugging for visual studio onto the other pc and run it. Then from your visual studio machine select "remote machine" and select the other pc from there
I found this link while searching for the same information as the OP:
http://blogs.msdn.com/b/spike/archive/2013/05/20/how-to-deploy-your-windows-store-app-to-surface-rt-for-testing.aspx
Hopefully this is helpful to someone who comes across this post. Basically, you will need to build the packages and copy them to the device, and then get your developer license installed on the device as well.
Complete instructions in the linked article.
One issue I came across was at the "Run with PowerShell" of the .ps1 file, I was getting signing certificate errors. I had to manually install the .cer file, and you have to make sure to put it in Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates node or the Certificates (Local Computer) > Trusted People > Certificates node for the signing certificate to be trusted by Windows and allow you to install your app package.
I'm running windows 8 and visual studio express for windows 8.
I have created an app and had it successfully submitted to the app store.
I am now working on a second app and getting ready to submit it. However, I just updated to the latest win8 SDK and to Windows app certification kit 2.2. Ever since I updated, I have been unable to run the cert kit.
Whenever I run the cert kit as part of the 'create app packages' I get the following error. I find it interesting that my first app gets the same behavior.
The {0} cannot continue testing since the specified Windows Store App was not found. Please verify the packagefullname is correct.
So, I try running the Windows App Certification kit 2.2 in stand-alone mode. When I select to certify windows store app, it thinks for a bit and then returns with an empty list of applications.
I found the following link wack doesn't see my app and followed the steps but still no joy.
Can you please confirm that you are using the RTM build of Windows 8? This was a bug discovered in pre-RTM builds that should have been fixed for RTM.
For testing an application, I have deployed my metro app by creating a app package which is provided in vs2012. I have deployed the package by opening using the PowerShell, but now I want to deploy the metro app in a Windows 8 device (tablet) for testing it, how can I do this?
Will there be a PowerShell option available in device also? (to deploy the app)
Are there any other ways of deployment?
i have used this to sideload apps for testing onto other devices including SurfaceRT
http://blogs.msdn.com/b/patricka/archive/2012/11/06/10365947.aspx
In addition to creating an app package in Visual Studio 2012, and deploying your app that way, you can also use the Remote Tools for Visual Studio 2012 for ARM to deploy and debug an app to a Surface or other tablet (for x86 or x64 tablets, use the matching remote tools install).
Once the remote tools have been installed on the target device, you simply start up the remote tools on the target, configure the access permissions, and then on your development machine, open the project properties, select the Debugging option, and use the dropdown to select Remote Machine as the debugger to launch. Click into the Machine Name field, and use the dropdown to select the machine name of the target machine running the remote tools.
Now, when you start debugging the project, it'll be packaged up and deployed to the target device, and you can set breakpoints and step through your code. And once deployed this way, you can re-run the app from the start screen using the app's tile.
EDIT: One important thing to note...whether you deploy/sideload using the PowerShell script technique, or using remote debugging, the target device will need to have a valid developer license. You should be prompted to obtain a developer license when you attempt to sideload your app, but you can also use PowerShell to obtain the license manually...instructions can be found here: http://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh974578.aspx
I have a Windows Desktop App ( WPF + c++ ).
I have just made a ClickOnce installer. I built it on Windows 7, but I want to certify the App for the Windows Store, so I'm running the Windows App Certification kit on Windows 8.
The installer works fine, it installs my application and puts an icon on Windows 8 start screen. My Application runs fine. I then uninstalled it ready to run the certification.
When I try to Certify it, the Application Compatibility Kit fails to install it ( a couple of windows flash open and closed SO fast I can't read them, I DON'T experience the installer dialog which would normally require some interaction from me).
Then the kit pops a dialog:
The Windows App Certification Kit did not detect any new applications
as a result of your installation. testing cannot continue unless an
application is successfully installed).
Previously a had a MSI installer that did seem to work with the compatibility kit (the app failed certification, but for legitimate reasons). Now I can't get the compatibility kit to even install my ClickOnce application. How can I certify my desktop app?
Edit Desktop apps are indeed possible in the store. See this. http://msdn.microsoft.com/en-us/library/windows/desktop/hh749939.aspx
ClickOnce applications are not eligible for Windows 7 and Windows 8 Software Logo program.
http://social.msdn.microsoft.com/Forums/en-US/windowscompatibility/thread/f10242cb-39f1-4f5e-ac1f-e55a6c722a6b