We created a XAML C# Project on Windows8(RTM ) but it failed to get certified using Windows App Cert Kit
But this failure occurred on RTM Machine we were able to pass the test on Preview Release.
Just to ensure this might be happening due to RTM we created a Sample Grid Layout Project and checked using the Certification Kit but even this failed .
Please Help...
I had this exact problem. There are changes between RTM and Release Preview, including version number changes that will automatically trigger a fail in the WACK test tool.
Basically, you need to recompile your project code using RTM Visual Studio on an RTM copy of Windows 8. you'll want to update any of your references as well if you're using third-party components.
Related
I just created a new empty universal app (windows 10) and checked it in on my visual studio online project.
The configured build is constantly failing on following error...
The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\WindowsXaml\v14.0\8.2\Microsoft.Windows.UI.Xaml.CSharp.targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
I set build configurations to use VS2015 but without any luck.
I keep thinking there's a simple configuration I'm missing here... but can it also be that it's not yet supported?
The project itself is just the standard template from Visual Studio.
I'm having a similar issue running with MSBuild 8.2 target missing under VS2013 Update 5 under Windows 10 TH1. Except my target is Microsoft.Windows.UI.Xaml.Cpp.targets. So not necessarily an issue with Visual Studio but rather the substitution for $(TargetPlatformVersion) in the targets definition:
<Import Project="$(TargetPlatformVersion)\Microsoft.Windows.UI.Xaml.Cpp.targets" />
I'm building a project from Microsoft (https://github.com/Microsoft/winsdkfb), so I don't think this is your problem (meaning you've not done anything incorrect).
I know this isn't an answer, but I suspect we're caught in a gap in the Windows 10 SDK & Tools. Those aren't scheduled to be complete and available until 29 July even though VS2015 has RTM'd. I tried to track down something in the VS2015 release notes without luck.
Just inform the solution I found on this thread.
At the time of writing, it appeared that VSTO serves were not yet updated with
the Windows 10 SDK.
The only way back then to make it run was by creating your own Build VM (through Windows Azure) and link it to your VSTO builds.
I posted the thread and got the answer on the MSDN TFS forum.
I have not tried it right now, but since Windows 10 is officially released now, I guess it may work out of the box.
We now support building Universal Windows Platform (UWP) projects on the hosted build service.
I want to do Windows Phone development with Titanium Studio.
I followed https://wiki.appcelerator.org/display/guides2/Getting+Started+with+the+Windows+Phone+SDK#GettingStartedwiththeWindowsPhoneSDK-UsingStudio(Preview) in order to get the Windows plugin. After a required restart of the software, the Windows option apears in the Deployment Targets when creating a new project.
Unfortunately, for all Titanium SDK Versions I have installed, 3.5.1.GA, 3.5.0.GA, 3.4.0.GA, 3.3.0.GA, I am getting an error like "Titanium SDK v3.5.1.GA does not support the Windows platform".
So I basically cannot create projects for Windows Phone.
I am using Titanium Studio 3.4.1 and followed the installation tutorial, though I deleted the SDK path after setting it (it is the default path, setting a value caused an error message, also I left the publisher GUID and Windows Store Certificate empty, since I just want to develop and don't have publishing credentials yet).
How can I create an app that runs on Windows Phone, too?
Edit:
I add some images to show the problem better. In the last step, I don't have the possibility to create a Windows project in Titanium Studio.
2nd edit:
As per Eduard's answer, I skipped https://wiki.appcelerator.org/display/guides2/Getting+Started+with+the+Windows+Phone+SDK#GettingStartedwiththeWindowsPhoneSDK-WindowsPlatform(Preview) and had to do it. Now I got Titanium SDK 4.1.0.v2015... and I get the option.
Unfortunately, it still does not work.
https://jira.appcelerator.org/browse/TISTUD-7171
So I also need to update Titanium Studio.
Well, I guess mobile development has to be buggy and cumbersome, at least that is my experience so far with various (cross-platform) products.
Try opening the solution generated in Visual Studio to attempt packaging the .sln to .appxupload to upload it to the Windows Store. Hopefully that will serve as work around until Titanium has full support for Windows (very likely 4.0.0 or 4.1.0 Titanium SDKs).
I created a hybrid worklight application having iPhone as the target environment using Worklight Studio 6.0. The application has 1 html file which has HelloWorld written in it.
I then migrated my worklight project to Worklight Studio 6.1. The application builds successfully, but while running the application, the application hangs at the splash screen and does not show the HTML page.
Is there any step that I am missing in the migration activity for iOS?
This actually sounds very much likely a recently fixed APAR: PI21872 ON IOS, INSTALLING THE SAME APPLICATION TWICE (WITHOUT unistall) would perform FREEZE AT THE APPLICATION START-UP.
While the APAR title does not match your problem description, it does match the issue that was resolved internally.
Either take a look at IBM Fix Central and install the latest 6.1.0.1 available there, or
Open a PMR and request the latest available Worklight 6.1.0.1 iFix
Verify that your issue is then resolved.
Also, since you say you have only "hello world" in your application, you could just create a new project in 6.1 instead?
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.
Background
We're using System Center 2012 to deploy a Windows 8 Metro-style application to Samsung slates in the field running Windows 8 Enterprise x64. The slates are joined to the domain and have a persistent DirectAccess connection back to it, allowing System Center to push applications and updates to the devices.
We have to deploy our application to potentially hundreds of devices in the field, which is why we went the System Center route. The code signing cert is installed on every device using Group Policy. To deploy the application, you simply provide the package output and specify the collection of devices to install it on. The app just shows up on the device in a few minutes.
The problem we're having is that when System Center deploys our application, the SQLite dependency is lost and none of our data access works.
About our project
Our application is a WinJS application that uses SQLite as a backend. However, all our data access code is in a C# WinMD project which the WinJS project references. We're using the sqlite-net library to talk to SQLite - we included the source for that in our C# project.
In Visual Studio, we installed the SQLite for Windows Runtime extension as described in Tim Heuer's article. The Metro application references this.
Testing using other deployment methods
SQLite data access from the application works fine when you debug or run it locally - in both Debug/Release and x86/x64.
The app packaging process provides a PowerShell script that you can use to install the application and a developer license if necessary. When installing our app using the PowerShell script, SQLite data access also works fine. Verified this by packaging and installing both Debug/Release and x86/x64 versions of the app.
Troubleshooting
When the application first tries to use SQLite, we see an exception about it not being able to find the sqlite3.dll.
We've tried/verified the following:
Confirm that we're deploying a Release/x64 build
Examine the appx in WinRAR and verify that it contains the sqlite3.dll
Reference the "SQLite for Windows Runtime" extension from the C# project instead of the WinJS project
Also reference the C++ runtime, this caused System Center to fail when deploying the app. Don't know why yet, but looking into it.
UPDATE
The issue is that System Center is having trouble deploying the Visual C++ Runtime Library dependency that the SQLite library needs. So unfortunately this isn't a programming question anymore. We're getting some help on this and I'll post the fix.
I wanted to post the details of a temporary fix that we're going with. We've also gotten closer to the root of the problem, so I wanted to provide those details as well.
Recap of Issue
When referencing the Visual C++ Runtime Package from our Metro project, System Center is unable to deploy the application to the devices because there is a problem deploying the proper version of the dependency for the appropriate architecture and build flavor.
Our development machines running Visual Studio 2012 (and packaging the project for deployment) are using a newer version of the Visual C++ Runtime (50727) than what is available in a fresh installation of Windows 8 (50712).
Worked with the System Center team and confirmed that this was a bug in the version we were using and has already been addressed in future builds. We're going to work on upgrading the environment but that will take a couple of weeks.
Workaround
I confirmed and tested the following workaround:
Remove the reference to the Microsoft Visual C++ Runtime Package from the Metro project
Install the x64 version of the Visual C++ Redistributable for Visual Studio 2012 - http://www.microsoft.com/en-us/download/details.aspx?id=3
Deploy the application
Works like a charm because the correct version of the dependency is there already. Obviously not a long term solution if we choose to also target x86 and ARM, but will get us over this hump.