When I go in to debug the app, it asks me to choose where I would like to deploy it. When I select Windows Mobile 6.5.3 Professional Emulator and click the Deploy button, it starts to work and throws up a command line and then it goes away and Visual Studio doesn't appear to be in debug mode.
I have the Device Emulator open, Windows Mobile 6.5.3 Professional Emulator loaded and cradled. Can someone help me figure out why it will not let me debug this project?
Brad, I downloaded the code and just unpacked the zip to D:\boxoffice_mobile (a local drive partition). Then I started VisualStudio 2008 and opened the solution file. I get a warning message that the project is not loaded from a trusted location (http://msdn.microsoft.com/en-us/library/bs2bkwxc%28v=vs.80%29.aspx). As I do not use a network drive, I ignored the warning two times and the projects load all fine.
BTW: I found a great tool to manage these 'security' warnings: http://blog.codingoutloud.com/2010/03/05/the-project-location-is-not-trusted-dealing-with-the-dreaded-unblock/. The message had nothing to do with a remote file access.
Then I just looked at the solution configuration to ensure that only the needed projects are build and did no change, as only BoxOfficeMobile and WebserviceTest are set to build and only BoxOfficeMobile is set to deploy.
Then closed solution configuration manager and just pressed F5 to start debugging to see what happens.
The startup project BoxOfficeMobile was build and deployed to "Windows Mobile 6.5.3 Professional Emulator". The emulator started and the files were deployed and the project was stopped by a breakpoint inside the code:
Here is another screen shot with the emulator set to 'Display: Always on top':
So, as you can see, the project is fine and the debug issue on your site is caused by a different setup.
Do you load the project from a network drive share? Try moving it to a local drive and run it from there.
Did you change Device settings in the VS2008 Tools:Options menu? Here is my setup (as coming as default, I did not change anything):
and the details:
The additional settings available via the buttons are empty (Configure) or unchanged (Emulator Options).
I am very interested in seeing what you changed to be not able to debug the project.
before you start developing for Windows Mobile 6.5 Prof, you need to setup your development environment.
First, install Visual Studio 2008 (no express version)
Download and install either ActiveSync (host OS <= Windows XP) or Windows Mobile Device Center / WMDC (Windows Vista/7)
[optional] Download and install Device Emulator Manager
Then download and install Windows Mobile 6.5 DTK (http://www.microsoft.com/en-us/download/details.aspx?id=5389)
Now, you can start a new C# project inside Visual Studio 2008:
Follow the wizard:
The list of Target Platforms depend on the Mobile/CE SDKs you have installed!
Select either .Net Compact Framework 2.0 or 3.5. The choose depends on what is installed on your PC and what is available on the device. If the device comes with 2.0 pre-installed, I would choose 2.0 except for I need something only available in 3.5 (ie Mobile.Status namespace).
Now you get an empty form:
You can change the target device in the project properties:
If you want to change the target platform, look at "Change Target Platform" in Project menu or just right click the project in solution explorer and select Change Target Platform:
The above has nothing to do with Device Emulator Manager or the installed Emulator Images!
You can run a WM5 targeting project on a Windows Mobile 6.5 device if you want.
To start debugging and SmartDevice application inside an emulator. Just Select an Emulator entry from the target device list in Project properties or just in the SmartDevice toolbar. Then click Debug and "Start Debugging". VS will start an emulator with the specified emulator image and deploys your project application files and start remote devugging.
You may also start an emulator image using DeviceEmulatorManager and then cradle the running Emulator image. To use the running and cradled (ActiveSync or WMDC connected!) emulator do NOT select an emulator inside VS but a Device. VS does not see the difference and uses the WMDC connected device, regardless of being an emulator or real device.
VS uses DMA to communicate with the emulator, not USB or Serial as with a real device.
Now start your development.
First of all clean your project.Then freshly start the emulator.Right click the project and select build.Then Debug the project.Your project will be started in Emulator (Don't Open the application from your Emulator at this time).
Just check your Emulator Start>File Explorer>My Device>Program Files whether the project has been previously installed.If so uninstall from the Settings> System > Remove Programs. And try re-building application and deploy it.
Related
I am trying to deploy a simple unity app to the Hololens v2 emulator. I followed some tutorials to build the unity files according to the Hololens build framework. The tutorials on Microsoft show there being an option in visual studio 2019 to connect the debugger to the hololens v2 emulator application, but no such option exists on my installation of Visual Studio, despite it being within the stated requirements, version 19.2 or later. Mine is 19.11
My version of Visual studio is 19.11, which should meet the requirement of 19.2 or later
here: https://learn.microsoft.com/en-us/windows/mixed-reality/develop/platform-capabilities-and-apis/using-visual-studio?tabs=hl2
It is shown having an option to target the emulator directly, and an option to target a remote device if using a physical hololens. I have neither option in my debug settings.
What the tutorials show
What my visual studio shows
I attempted to set it up like the remote machine setup shown in the tutorial, getting the correct hololens machine name by accessing the ip address of the emulator, but to no avail, it refuses to connect
It compiles properly, but then comes up with this error when run with those settings (with the correct machine name rather than a filler like I have in the image)
Does anyone have any ideas as to how to fix this? I have updated visual studio multiple times already.
Please make sure the correct project has been selected for the startup project. To change the startup project, you should navigate to Solution Explorer, right-click the desired project and choose Set as StartUp Project from the context-sensitive menu that is displayed.
I have some old windows 10 mobile phones, that I want to give a second life as a music device for my kids. Since I have Visual Studio 2019 Enterprise at my hands, I thought I try to create something myself.
Not I tried to create an UWP app and a Xamarin app and try to debug them on the phone (connected via USB, developer mode enabled, unlocked). But with both I get this error:
DEP6957: Failed to connect to device '127.0.0.1' using Universal
Authentication. Please verify the correct remote authentication mode
is specified in the project debug settings. COMException ... HRESULT:
0x8007274D) [0x8007274D]
The apps are still in their initial state after creating the project, no modifications done. The settings for debugging are set to: Debug, ARM, Device
I had some experience with an older Visual Studio version and windows phone 7, back then it just worked and all the documents I could google up suggest, while there are new ways, it should still work via USB.
If you plan to develop Windows 10 Mobile App, you need to use Visual Studio 2017 and make sure the target version of the app is below 14393.
Visual Studio 2019 no longer supports deploying UWP apps on mobile phones.
Best regards.
sometime i must reboot service something like windowsphone ipoverusb
Using Visual Studio 2013 Ultimate update 4, I have developed a universal app for the store and the phone under Windows 8.1. The app is implemented upon the Prism for Windows Runtime.
The app is at its final testing stage. I have no problem to run/test it with the corresponding emulators and devices (Surface Pro and Lumia 1020) until few days ago. Although the app can still run/test with the emulators (The store app can be still packaged and deployed to Surface Pro for testing). But I will receive following error message when running with device (Lumia 1020) under Visual Studio 2013:
Unable to activate Windows Store app …. The xxx.exe process started, but the activation request failed with error ‘The app didn’t start’.
I have tried all followings in number of times, still received the same error message (there is no app.config file used in app (at least not being seen in the solution pane and windows explorer):
Roll back to the change set where I have successful made the build and deployed to Phone.
Run repair on Visual Studio
The problem has been fixed.
I have used MS Ocr Lib. for Phone once which only works for ARM. After using NuGet to remove Ocr lib., OcrResource folder still remains in the phone project.
To fix the problem, one must either deletes OcrResource folder if the target platform is for Any CPU, or keep OcrResource folder and set the target platform as ARM.
I have not been able to find any documentation on if you can run applications in debug from a Windows 8 RT based tablet (such as the new Microsoft Surface) like you can on the iPad or Android devices.
Does anyone know if this is possible, and if so (or not), is there any documentation anywhere pointing to such?
Yes, Visual Studio remote debugging supports debugging an app running on an ARM target. You can find more information "What you need to know about developing for Windows on ARM (WOA)."
Visual Studio has the remote debugging tools for working with external devices and other computers. In a Windows Store application project you go to the project properties and click the debug tab. Choose the target device in the dropdown Debug settings (click to see screenshot)
You'll need the setup remote debug service on your tablet and on your dev computer. The devices need to be on the same network subnet. I'm not sure how that will work on the Surface ARM device, as they cannot join a domain. I guess we'll know more once the hardware ships.
Get your remote debugging tools at Visual Studio Downloads.
Jason Zander has a post about working with ARM devices that might be helpful.
I have built an os design (and its bsp) in Visual Studio. I need to know how to get started with writing applications for the os by writing a simple application that will run in the os created (probably in an emulator, I still don't have the Evaluation module for the device). I have Visual Studio 2005 and Windows embedded C.E. 6.0 installed.
Some blogs described how to create the application in eMbedded Visual C++. Will I have to install this apart from Visual Studio to get started?
If you built an image from an OSDesign for a specific device you cannot run it in the emulator. The emulator has it's own sepcific BSP based on which you need to create an OSdesign.
To develop an application for your osdesgin of choice open VS2005 create a new project of type Visual C++-> Smart Device and choose the type you want. Alternatively, you can create a C# application for smart devices that will run on any device that includes the Compact Framework component in the OSDesign or has it installed on the device.
You do not need additional software other than VS2005.
You can download a package from this vendor. It includes demo applications for Windows CE6 (for that device). It also includes a document of how to create a new application for the device. You can use the instructions to create an applcation to your own device.
To test your application as it will perform on the image you built, you will need a physical device.
Update: During the New Project wizard you will be asked to choose the designated platform (native projcets at least) and you will need to choose from a list of SDKs. The list shows the installed SDKs on your desktop machine. You can create your own SDK, but in order ofr it to show in that list you need to install it on the Machine. In Windows CE the SDKs are installed to: C:\Program Files\Windows CE Tools\wce600