I am about to create a Windows Store application, and need to purchase a Windows RT device for testing. Is the Microsoft Surface the only device that supports remote debugging from Visual Studio? Or will it also work with a third party tablet from for example Samsung?
For debugging on a tablet you need to install the Remote Debugging tools on the tablet. Secondly, both machine (your developer rig and the tablet) need to be on the same net and the local firewalls must allow access. Then you choose Remote Debugging in VS2012 and you can choose the tablet. On a Surface RT I had to enter the name manually, as it has not found it by searching the local network.
Tim Heuer has a blog entry exactly about this topic: http://timheuer.com/blog/archive/2012/10/26/remote-debugging-windows-store-apps-on-surface-arm-devices.aspx At the very end he says:
Now that you have a Surface (or other Windows RT device)
If your tablet is x86 it is a PC and is able to run the remote debugging agent, too. Note: download the correct version (x86, x64 or ARM)
Related
Unable to install Microsoft Hololens Emulator and throws an error midway:
And the link is of no help as well as it takes to another link showing a solution for "How to enable Hyper-V for the emulator for Windows Phone 8"..
You need to have a machine that can handle creating Virtual Machines, So you need an I3 or better and your Bios has to allow VM creation, and you need to be running windows 10 Professional to get access to Hyper-V
We design and develop applications that run on Windows Mobile and Windows Embedded, as this is the operating system that comes on most industrial bar code scanners right now.
Give that, we often use the Windows Mobile Device Emulator to simulate our software and give customer demonstrations. With Windows 8 being released, it seems that the Windows Mobile Device Center no longer works. This component was required to "Cradle" the device to get a network connection.
Is there a way to get the Windows Mobile/Embedded emulator to work on Windows 8?
You need to uninstall Windows Mobile Device Centerand to install the most recent one (dec 2012).
Go to the Microsoft web and download Windows Mobile Device Center for Vista (32 or 64 bits according your hardware). There is not option for Windows 8, but the version for Vista works perfectly in Windows 8.
you can always use Windows CE versions for using on your mobile/ embedded projects
I'm using Compact 7 and try to follow the steps in a book called "Professional Windows Embedded Compact 7". I managed all the exercises up to chapter 8 but now I'm stuck.
Chapter 9 is about Remote Tools. I build and deployed the OS as described in the book and everything is working fine but when trying to connect remotely, it doesn't seem to work. For example when using the "Remote File Viewer" from the "Tools\Remote Tools" menu, I select the target device from the "Select a Windows CE Device" menu and it shows the "Connecting to device" dialog but it stays there and never connects.
I also tried the Remote Profiling tool and other remote tools, they all failed to connect. Is there anything that I'm doing wrong or does this mean that it is not possible to use Remote Tools for a Virtual PC?
I found this Microsoft topic:
http://social.technet.microsoft.com/wiki/contents/articles/6012.how-to-use-the-remote-tools-framework-without-kitl-or-activesync-windows-embedded-compact-7.aspx
Hope this help you.
Thomas.
I am just curious if there is a way to package up a Windows 8 Metro application to distribute it to others with the Windows 8 Developer Preview installed? It would be nice to be able to allow someone to just download and install, rather than requiring them to install VS'11 Preview and compile the code themselves in order to test out / use a Windows 8 Metro application that I've built.
Is there a way to distribute a compiled Windows 8 Metro application for others to test/use since the Windows Store is not yet live?
This would likely be useful for testing Metro apps on non-development machines even after the Windows Store is live.
Each machine that wants to install the application will need a developer license. See this page for some details.
When you have your app ready:
select Store->Create App Package
Select Build a package to use locally only
Follow the prompts
This will create a package in whatever folder you specified. You should be able to copy that to another developer-licensed machine and install it.
There will be a batch file called Add-AppxDevPackage in the directory. Running it will install the app. It must be run as an admininistrator.
Distributing apps outside store is possible after complying to the prerequisites listed in this MSDN article. It also covers the process of application installation using PowerShell. Though it appears quite complicated, note that MSIs work fine for Windows 8 metro apps so you can probably enclose the installation process into one small instalator.
From the article
Requires Windows 8 Enterprise Edition, and must be joined to a domain, and the domain must have the Allow all trusted applications to install Group Policy setting.
for Windows 8 Professional, and Windows RT, or a non-domain joined machine, you must buy a sideloading product activation key from Microsoft
the application must be signed by a key that is trusted by the computer
Once you've purchased your sideloading product key from Microsoft, add the sideloading product key:
>Slmgr /ipk <sideloading product key>
To enable side-loading, enable the following guid:
>slmgr /ato ec67814b-30e6-4a50-bf7b-d55daf729d1e
To add an application, from a powershell prompt:
>add-appxpackage C:\app1.appx –DependencyPath C:\winjs.appx
Windows 8.1 Update
According to the latest announcements by Microsoft the next update to Windows 8.1 will allow all the devices running the Pro version to sideload applications without sideloading activation key. So far this has been the case only for the Enterprise version. Bare in mind that the machine will still need to be a part of the AD domain. Additionally, if you still run a previous version but you're part of any of the below programs:
Enterprise Agreement
Enterprise Subscription Agreement
Enrollment for Education Solutions (under a Campus and School Agreement)
School Enrollment
Select and Select Plus
You'll be granted the enterprise sideloading rights starting on the 1st of May 2014. Otherwise you'll still be able to sideload but will need to buy a sideloading activation key for 100$ (that's a one-time charge for an unlimited number of devices).
If I recall correctly from the white paper, then a Windows 8 Metro application can only be installed by consumers from the App Store.
However there will be a way provider for developers (as explain by Stave Rowe) and a way for corporations to installed Windows 8 Metro application directly, I expect the corporation method will be by using Active Directory (group policy), but may be limited to some editions of Windows 8.
You can distribute the Windows 8 App package and deploy the same using the Side loading process
Refer this link for more details about side loading
http://technet.microsoft.com/en-us/library/hh852635.aspx
I am a frequent Windows Mobile application developer in need of a new development laptop.
I am considering a MacBook or Macbook Pro running either Fusion from VMWare or Parallels Desktop. This will give me the option to port my applications to the iPhone depending on what MS does with WM 6.5 and 7.
Has anybody tried doing Windows Mobile development using Microsoft Windows Mobile Device Center (or ActiveSync) and VS2008 on the MacBook Pro using one of these virtual machines? Does the device emulator work properly? What about debugging a Windows Mobile device over a USB cable?
In general, do most USB drivers (non HID) designed for Windows work under these virtual machines?
I do cross platform (iPhone & Windows Mobile) development all the time on a Macbook (13" unibody). Have Visual Studio 2008 running on Windows XP on a Parallels VM. The USB pass through works perfectly for debugging too.
I would suggest you have 4Gb ram (minimum) if doing this, but works very well.
VMware's USB passthrough option works quite well. I have no personal experience using it to attach Windows Mobile devices to a guest OS though.