Deployment of application to device failed - windows-phone-8

I'm developing a WindowsPhone8 application on Visual Studio 2012.3. (on Windows8 x64, ARM project) Application works fine on emulator, but when I tried to deploy it onto real phone I have got:
Windows Phone: Deployment of application to device failed.

It is a common question. I think that it will be helpful:
"The current implementation of strong names in Windows Phone 8 does
not support the RSA-SHA256, RSA-SHA384, or RSA-SHA512 (collectively
known as RSA-SHA2) signature algorithms. The current implementation
supports only the RSA-SHA1 signature algorithm. Therefore, developers
should use the RSA-SHA1 signature algorithm. Developers who write
Portable Class Library projects that include Windows Phone 8 as one of
the target platforms should consider this support if they decide to
sign their projects. "

Related

libgdx to windows phone using bridge

Windows Phone got my attention recently with making iOS and Android apps convertible to Windows Phone apps using Windows Bridge. I am eager to know if libgdx support translation to windows phone apps with Bridge tools? Has anyone any experience with it?
Well, the bridge is under construction still so you're not likely to get much feedback here. LIBGDX hasn't concentrated on Window's phone, but I think they've created an x86 DLL for some of their unmanaged code a while back. Not sure on the status of that.
I used a similar bridge technology for Blackberry in the past. The process was simple and only required installing plugins and executing a conversion tool on my Android APK. No code changes.
However the site for the Window's phone bridge says minimal code changes may be required. I'd speculate the process will be extremely simple so as to encourage releases of popular apps onto their platform. If Microsoft makes the process complicated, developers aren't going to bother.

Why does the managed version of WinRT not include access to the .NET API?

Recently I began working in WinRT for Windows Store Apps (and the upcoming Windows 10 Universal Apps) using C#. After working in .NET for awhile previously, I was excited to work with .NET on mobile devices, only to find that WinRT did not feel like home at all.
Constantly I find myself having to search for alternatives to certain classes that I'm familiar with in .NET since often they're not the same or even implemented in WinRT. I figure that the lack of implementation derives from the fact that WinRT at its core is unmanaged, even though the CLR binds to it from managed code.
My question is: What is stopping Microsoft from allowing developers to import and use all of the familiar .NET classes from managed code, even with WinRT running from behind? I know it's not a limitation of the device because my Surface Pro can run desktop .NET apps just fine and the Mono project has succeeded in porting almost the entire .NET API to devices of every kind.
Thanks for your input!
This is a big topic but there are three basic reasons why you don't get the full .NET API from a Windows Store app.
The APIs don't fit on smaller devices like phones. Since the purpose of the Universal Windows Platform is to have apps that can run everywhere, it can't include APIs that are too resource-intensive (disk, memory, CPU, etc.) to run on smaller devices. (Note that even if the managed API appears to be small, it might have a dependency on a large underlying Win32 API).
The APIs aren't compatible with the Store app model. Many APIs that require permissions not granted to Store apps fall into this category, as do APIs that would enable apps to do "unwanted" things to your machine (the degree of "unwantedness" is subjective).
The APIs are deprecated or there are newer alternatives. This was the case with a lot of APIs in Windows 8, where things like file-system access and network sockets were blocked from Store apps because there were newer WinRT equivalents.
Note that Microsoft is always open to re-evaluating whether a specific API should be included or not. For example, Windows 10 brings back many APIs that were banned from Windows 8.1 (such as System.IO and System.Net.Sockets) and has expanded the capabilities granted to apps. You can file feedback via the Windows Feedback app or on UserVoice if you want additional APIs brought back (adding detailed justification never hurts).

Windows Phone 8 and Neural Network

I am wondering to using Neural Network frameworks on Windows Phone 8. I am searching on google but I can not found illustrative information. Is it possible ? Can using like a Aforge or another frameworks.
Thanks in advance. (sorry my language)
Both the AForge.NET Framework and its "extension" Accord.NET Framework have been adapted to Portable Class Libraries. All functionality related to neural networks, machine learning etc. that are contained in the original frameworks have been ported to their PCL analogues.
The PCL libraries target the following platforms:
Windows 8 and higher (formerly known as Metro or Windows Store apps)
Windows Phone (Silverlight) 8 and higher
.NET Framework 4.5 and higher
(When used in .NET, the libraries enable the ability to create WPF applications independent of System.Drawing and System.Windows.Forms assemblies, but that's another story :-)
The portable frameworks are available on Github:
Portable AForge.NET Framework
Portable Accord.NET Framework

Bluetooth Low Energy costum Service device discovery and development for Windows 8.1 Store Apps

I started building Windows Store App, but after I discovered that my device is not discovarable on Windows 8.1 compared to Windows 7 and IPhone on which I can detect this Blutooth LE device.
I am using following PrimaryServices:
Generic Access (0x1800)
General Attribute (0x1801)
Costum service (0x13B0)
Device Information (0x180A)
How can I make this device discovarable and usable later in Windows Store Apps (writing some kind of driver, change some services on device or as a last option write specification for costum service this is too expensive for me at the moment)?
Mutiple solutions for this problem are welcome.
You need to go through Windows 8's UI to pair with Bluetooth Devices. You cannot control the pairing programmatically.
If what you describe is that you cannot discover your Bluetooth device, even on Windows 8's UI, then there must be a compatibility problem:
Your dongle on Windows 8 may be classical (below 4.0) while the device is strictly Low Energy (4.0)
Your dongle's driver was not properly installed

Windows Phone 8 - Simulate touchscreen events

What would be the best approach to simulate a user tapping on a touchscreen of a Windows Phone 8 device?
One approach I could imagine is to use native code to call the Win32 API functions which control the mouse events. This would assume that touchscreen events are more or less the same as mouse events, and that these API functions are accessible. Does anyone know if this is the case on WP8?
Another approach would be to have something like the Android ADB for the Windows Phone. On Android, one can use ADB to control the device from the PC and also simulate touch screen events (e.g. via Monkeyrunner). I haven't found any information if there is a tool like ADB for Windows Phone 8.
The purpose of finding a solution for this is the integration of Windows Phone 8 devices in an automated testing process.
I found out that there is a DLL file named InputInjection.dll in the System32 folder of the Windows Phone 8 (at least in the simulator image I mounted).
This library contains the following functions:
ApiInjectInitialize
ApiInjectTouchEvent
ApiInjectButtonEvent
ApiInjectEnableExclusive
ApiInjectUninitialize
Doing some research, I found out that there are official ways to simulate touch input for Windows 8 development:
http://social.technet.microsoft.com/wiki/contents/articles/6460.simulating-touch-input-in-windows-8-preview-versions-using-touch-injection-api-en-us.aspx
http://msdn.microsoft.com/library/windows/desktop/hh802896(v=vs.85).aspx
However, the functions used for Windows 8 development are not available on Windows Phone 8. But the functions are named similarly to the ones I found in InputInjection.dll:
InitializeTouchInjection similar to ApiInjectInitialize
InjectTouchInput similar to ApiInjectTouchEvent
(...)
I wasn't able to find any documentation on InputInjection.dll and its functions. These functions also don't appear in the header files of the SDK. Maybe Microsoft uses these functions internally for their own tests during Windows Phone development.
The question is: Is it possible to access this library and call these functions somehow? This would be similar to using "Private APIs" on iOS, I guess. I tried several ways to achieve this with a Windows Phone 8 app using native C++ code, but I had no luck so far (the basic reason is that the apps run sandboxed on Windows Phone). Is there any way to get a binary running on Windows Phone (maybe via a debug bridge or something)?
You can access all those API's From Win32 Service/ Kernel Driver. Include the header file to your source code and Library of injection method it will work