I realize I'm jumping ahead a bit, but has anyone attempted to run CoronaCards through Virtual Studio on the Windows 10 Technical Preview?
Jump to content
Agreed Larry. I will be using VS 2013 (Community; not trying to shell out right now), so we'll see how it goes. The move to Win10 was error-free to Microsoft's credit. I did not expect that.
I'll report back with any hiccups or updates as I move through the process. If anyone has any questions or would like me to test something out with CoronaCards on WP development with Win10, post here and I'll get it added to the list.
@Alex, the Corona University videos we did all used Windows 10 Technical Preview.
Not sure how long the Preview will last, but it works great as a way to set up a "no cost" development environment.
Well, I hit the first hiccup: Hyper-V Virtual Machine Management service seems to be either be missing or disabled on my Win10 box, as I am not able to debug on an emulated device. Virtual Studio keeps telling me that I need Windows 8 Professional.
I can bring up my services window, but I can't click on anything within it. @Charles, did you encounter this issue?
Alex, Microsoft document's the minimum system requirements for the WP8 emulator here...
1) You need to run a 64-bit Windows operating system.
2) Your CPU must support a hardware feature known as SLAT. (aka: "Extended Page Tables" on Intel; aka: "Nested Page Tables" on AMD.)
3) You should also have at least 4 GB of RAM.
I suspect #2 up above is the problem. Your CPU might not support SLAT. Microsoft provides instructions via the link below on how to enable SLAT in the BIOS. They also provide a downloadable command line tool to identify if your hardware supports it too.
You can also purchase a WP8 device without a contract for cheap on Amazon. For example, I've found a Nokia Lumia 520 (no contract) for $40 on Amazon here...
Oh and based on the statistics that I've seen, that Lumia 520 is currently the most popular WP8 device. Low-end, low-resolution, low-memory WP8 devices are the most popular WP8 devices, so, it would be good to test on them. Especially to make sure that you're not exceeding the max memory limit for you app (worst case is 150 MB) and to ensure that your app performs well on low-end CPUs.
And in case you're interested, I usually go to AdDuplex's blog (link below) to see what the current WP8 model and OS version distribution is.
I hope this helps!
@Joshua, definitely helps a bunch! I found some useful resources regarding enabling Hyper-V on my particular laptop model, and I'm running through those now. I'll report back on my success.
Thanks also for the cheap WP phone tip. I was looking at Newegg; I should have known to price-check on Amazon!
Issue #2: The service "Windows Phone IP over USB Transport (IpOverUsbSvc)" on my Win10 box isn't started. I did find it in the services dialog, but as I said before, I can't click on anything in this window so I can't start this service.
Has anyone run into this issue? At this point, I think it's closer to a Win10 problem (can't start services because I can't click on them) rather than a hardware problem.
You need admin permissions to start/stop Windows services. Perhaps you are not running as an admin then?
Go to the following folder in Windows Explorer:
Control Panel\System and Security\Administrative Tools
And then right click on "Services" and click on "Run as Administrator" from the popup menu.
Note: If you press "WindowsKey+S" and type in "Administrative Tools" in the search popup, it'll display a shortcut that'll open the Administrative Tools folder in Windows Explorer.
Joshua, thanks for the help on this. It's becoming apparent that my Windows 10 build doesn't behave like other folks. Here are the screens I have from my "settings" panel:
And here's the "system" entry:
I can't right click on anything in either window, and if I search for the "services" entry (which is how I found the window to begin with) I can't right-click on that either. As a matter of fact, I can't re-size the window, I can't minimize or maximize the window. I can only close it. I know my right-click button works, so that's out.
Am I missing something stupid? Does the fact that I can't right-click inside the "settings" window mean that I'm not logged in as an administrator? I'll try that now and report back...
I swear that I am not an idiot, but ALL OF A SUDDEN I can click inside of my "services" window. I'm thinking about packing it in today and calling it a bad job, because I'm swinging and missing all over the place.
I was able to get the service to start, and I'll report back once I confirm I can build to an .xap file. Thanks all for the help!
Great! Happy to help!
Also, I know that Charles was able to run the WP8 emulator on his Windows 10 preview machine. So, as long as your CPU supports SLAT, there is most definitely hope.
Perhaps Microsoft's Visual Studio installer doesn't automatically set up everything for you on Windows 10 like it normally does on Windows 8... because I don't remember having to manually enable the Windows service you mentioned. It just worked after installing it. I guess this is just part of the pain on jumping on the bleeding edge.
I guess so, Joshua. I've never been impressed with the early builds of any Microsoft OSes, and this one isn't changing my mind anytime soon.
One last question for the day: I'm finally trying to build my app, and it keeps failing because I don't have a Windows Phone connected to my machine. Do either of you know of a way to get around this? Is there a way I can emulate a WP device being connected, or perhaps just disable this pre-requisite?
If you just want to build a *.xap file, then click on "Build\Build Solution" from Visual Studio's menu. That will build the app without deploying it to a device or emulator. The *.xap file is typically outputted under your project's "bin" directory.
Also note that even though clicking the ">" toolbar button will cause a deployment failure due to a missing WP8 device/emulator, it'll still do the "Build Solution" step up above and compile/output a *.xap file under your "bin" directory as well.
And if you look at the documentation in the link below, you need to build for "ARM" when building for a device. Building for "x86" is for testing purposes only via the WP8 emulator.
Happy to help!
And I've got 1 more helpful tip, in case you don't already know it. When you install Visual Studio 2013, it comes with an "Application Deployment" tool that allows you or someone else to deploy a XAP to a WP8 device connected via USB. Just do a Windows desktop search for "Application Deployment" and it should pop right up.
Hit another snag, as my CoronaCards subscription for WP wasn't renewed with my Pro subscription. I just sent an email to support, so it should be resolved shortly.
That "Application Deployment" tip is definitely useful. Regarding the device, I was chatting with another WP developer, and they were saying that the 520 is good to test the bottom of the device curve, as you said, but they said a good amount of folks are using the 820, which has specs that are a bit better, but isn't being actively sold. A little food for thought for those looking to deploy to WP.
Our tech-support group is usually pretty fast in resolving these things during business days. So, you should here something fairly soon. Once they've synced your WP8 CoronaCards subscription with your Pro subscription, then just so you know, you'll be required to download a new license file with your updated authorization data.
If you need to test/debug stuff now, then in the mean time you can simply remove or exclude the license file from your WP8 project. That'll put Corona back into trial mode, which will show a "Trial" watermark onscreen. There is no trial expiration time for WP8 CoronaCards.
And interesting point about the Nokia 820. I would hope that people who are willing to pay extra for the better WP8 device models would make better potential customers too. Like you would expect someone who pays for a "gaming rig" quality PC would intend to do more with it than simply e-mail and Internet browsing.
Subscription issue already handled. Thanks Joshua!
I have to admit, I like the idea of Windows Phone, and the designs and user interface are very nice, but after using an iPhone for a couple of years (and having an S.O. who demands an iPhone) I can't see myself ever using anything but Android. That said, I am strangely looking forward to getting my 520 in the mail, dropping my SIM in and taking it for a spin.
Just Some FYI..
Here are a couple good articles about Windows Phone usages and devices Ram / Power etc..
Community Forum Software by IP.Board