Downloaded and loaded Windows 10 Pro (X64) via Parallels Desktop and attempted to download Desktop App Converter but wasn't able to do so as I was receiving a message stating "This app will not work on your device."
On scrolling down I could see that the issue was caused due to the fact that the Store did not detect that my OS was running in X64 architecture, but it was ! (as seen in the screenshot)
I contacted the Microsoft support team, explaining this. A tech representative took control of my desktop and figured out that the issue was that I was running Windows 10 as a VM on a Mac.
The work around is to install the Desktop App Converter from https://www.microsoft.com/en-us/download/details.aspx?id=51691
Related
Whenever I am starting to test an Windows Phone app (even a blank app) on emulator, I am getting error "The project needs to be deployed before it can be started". The emulator will be started & run successfully, still no luck in deploying app on emulator. Getting error DEP6100 & DEP6200.
These are the stuffs I tried till now:
Checked "deploy" option in 'Configuration Manager'.
Tried deploying Windows 10 Mobile, Windows Phone 8.1 & Windows Phone 8 blank apps on different types of emulators.
Although I am able to run apps on my device.
I am running Visual Studio Enterprise 2015 on Windows 10 Enterprise.
The Emulator is x86 based and Phone is ARM architecture. To run the app in the emulator, change the CPU to x86 in the toolbar and compile it. Now you can deploy te App to the Emulator and test it.
I faced problem like that and I fixed it by right click on project > properties > change platform target to X86.
I just started playing with Xamarin Forms, and ran into this error after following the Xamarin Forms Quickstart Guide. The error message actually said to Run the Deploy... for the project that you are trying to run. Deploying the project seems to install some Windows dependencies that might be required to run the UMP. After deploying the project, it ran without issue as a Windows Desktop app, or if you change to Device, then install emulator, as Windows Phone app.
This error was relentlessly happening to me as well, and I found out that it was because my project was saved on a SanDisk SD card. If I simply moved the entire solution to my C drive, it built without issue, but on the D drive, it would give this error.
I am able to generate & install windows phone build in my Microsoft Lumia 640. Its running on Windows OS 8.1.
But as soon as I run application generated by CN1 build server, it gives error
An internal application error occurred: java.lang.RuntimeException Unsupported operation as per below screen shot.
For a testing purpose I created new CN1 Project and without changing any code / theme.res I just sent windows phone build and it ended up with the same error.
Unfortunately I didnt get any log output from windows phone, as it doesnt support Logcat like Android. Also I tried to grab Isolated Storage by WP Power Tools but there was nothing in it.
Anyone faced / facing this in Codename One windows phone build ?
The Windows Phone port is the least mature of the Codename One ports having gone thru 3 rewrites due to changes from Microsoft.
We are now debating the 4th rewrite, in the meantime some community members did their own port which should be more complete:
https://github.com/Pmovil/CN1WindowsPort
So as the short answer I suggest using that. For an explanation on how we got here read on.
The reason we didn't already start with the 4th port was Microsofts project astoria that they suddenly (might have) canceled. We were relying on this project for future Windows Phone support but now that its status is unclear we are in a bind.
We also have the JavaScript port & the Windows desktop port as options for targeting windows phone alleviating some of the problem.
If MS cancels the project for good we'll dedicate the resources for a complete rewrite of the port, but that will take time. However, we don't want to start off on such a huge effort and suddenly be faced with a huge shortcut of Android compatibility.
I have been using Windows 8.1 for creating Windows Store apps. Below is output of winver command.
I have installed necessary updates to start developing universal Windows Store app using JavaScript. When I try to launch app on Windows Phone emulator, I am getting following error.
Unable to start windows phone emulator
It also suggesting to use Windows 8 pro version. Is there anyway of running this without requiring to throw more money on getting Windows 8 Pro version?
Windows Phone Emulator requires Hyper-V which needs Windows Pro version. That's probably why you aren't able to start your Emulator.
As I've posted in comment, I've heard about VirtualBox and an ability to run WP Emulator on it. Some helpful links: other question on SO, VirtualBox forum, video. I'm not sure how it will work (and if) as I haven't tried this.
IMO I would follow WiredPrairie's comment - upgrade or buy inextensive phone.
I installed Windows 8.1 RTM and installed VS2012 had a little problem while installing windows phone 8 sdk but i guess it is resolved now but still i have a weird problem.
Even i select "device" as the launch target when clicked the run button VS launches the app on the emulator not the phone. Surprisingly if i right click the project on solution explorer and select debug it this time launched app on the device.
Is there anybody faced with this kind of problem? I dont want to install everthing from scratch :)
Ok it was my fault, since the project build platform was x86 visual studio could not deploy the app to the device and hence launching the emulator. When i changed the build platform to Any CPU now it deploys my app to the device without any problem.
I have observed inconsistent behavior using the Web Developer extension (Chris Pederick) in Google Chrome on these different machines:
My PC running Windows 7 Home Premium 64-bit
A VirturalBox Virtual Machine (VM) running Ubuntu 12 on my PC
A VM running a updated, fresh install of Windows 7 Home Premium 64-bit on my PC
I have the same version of Google Chrome and Web Developer installed on all these machines. However, for some reason, Web Developer does not work as expected on my PC. It works perfectly on the Ubuntu VM and the Windows VM.
On my PC, about 95% of the time the Custom Tools functions (Validate CSS, Validate HTML, etc.) in Web Developer do nothing when clicked (they should open new tabs to the W3C validators).
I have uninstalled and reinstalled Google Chrome on my PC several times. I have even manually gone through the file system and registry to completely remove all traces of Google Chrome before reinstalling. Nothing I've attempted so far has corrected this problem.
Of course, due to Google's 'field trials', all these machines have slightly different variations (as reported by chrome://version), but I would doubt that is the source of the problem.
Any ideas or suggestions?
OK, here's a possible clue...
It has baffled me why this problem NEVER occurs in my virtual machine (VM); only on the host. Same version of OS, Chrome, and Web Developer installed on both. May have discovered why.
My standard settings for VMs is to use only one CPU. As a test, I changed the VM to use two CPUs. BOOM! I can reproduce the problem on my VM. Change back to one CPU - can not reproduce the problem.
Does this suggest a problem with threading in Chrome?