I'm using VS2015 with SDK 10240 .
I've build my application already (with C#) ... But I can't run it on my windows 10 mobile cause it's build 10130.
How can I change min SDK of my application ?
Do I've to download and install the old SDK ?
Can I debug it on my Windows 10 mobile?
To manually work around this (don't forget, the app may break on phone), you can do the following:
Right click on your project in the solution explorer
Click "Unload Project"
Right click again and edit [yourapp].csproj
Find TargetPlatformMinVersion and change it (in this case, to 10.0.10130.0 or lower)
Save the file and reload the project (right click on the project in solution explorer, "Reload project")
Your mileage may vary with this as 10130 is a prerelease build of Windows.Mobile. If you need to test/debug on Windows.Mobile, I recommend using the Windows 10 10.0.10240.0 emulators, but I recognize there are some advantages to trying on a real phone.
Related
I'm creating a windows desktop universal app (UWP) using Windows Template Studio on Visual Studio 2019 Community, on a Windows 10 Family Edition.
Windows and VS2019 were updated today (before creating this app).
After the project was created using WTS i have an error telling me (mine is in french so i'll try my best to translate) that : I need to upgrade to "windows 10, version 2004 (10.0.19041.0)" in order to display this content (aka : the XAML UI designer). However, the 19041 sdk is already installed. I can build and run the application just fine. It only a problem with the designer.
If i change the application property target to from 19041 to version 1903 (10.0 ; Build 18362) and reload the project, it works just fine.
I don't think i really need this 19041 (i hope so) but : what's happening and how to fix it ?
If you set the target version at 19041 (2004), this requires your development environment to be at least 19041. The SDK installed through Visual Studio contains some development tools corresponding to the platform, but UWP development usually requires some native resources (such as colors, control styles, etc.), and these resources will follow the system update.
So when you set the target version of the project to 19041, the target of some local resources referenced by the project is 19041. If your development environment is lower than this version, the designer will not be able to display.
I have been battling DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.14393.0 or higher. You currently are running version 10.0.10586.839. Please update your OS, or change your deployment target to a device with the appropriate version. for the past few days.
I have a UWP app which I cannot run on my machine. However, if I select one of the emulators, it runs fine. I have also set the minimum target value which ensures that the app runs, however, the app throws an error as it cannot find some methods in the lower version on the SDK.
I have tried repairing and uninstalling/re-installing both visual studio 2015 and 2017. I have tried the same with the various windows SDK as well. At one point i had three different versions of the SDK installed and visual studio was still complaining even though i had the updated version installed. Currently, I have installed win sdk 10.0.15063.17.
Any ideas what I can do next to resolve this issue. I have trawled various SO pages as well social.msdn pages with no luck.
Many thanks
I just started a new app and selected the highest Target levels and got this error. I was able to get rid of this error by selecting the default minimum Min Target Version as shown below.
I also encountered the same problem
Severity Code Description Project File Line Suppression State
Error DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.17763.0 or higher. You currently are running version 10.0.17134.648. Please update your OS, or change your deployment target to a device with the appropriate version.
Solution:
Right click on the project property and got to the General-> Target Platform Minimum version.
In my case, I changed it to "10.0.17134.0" by selecting from the drop-down and then rebuilt it.
I worked well. Attached snapshot for reference.
If your app is using APIs that only exist in newer versions of the OS (like 14393 or 15063), then you won't be able to call those on 10586. You will get an exception because the method simply doesn't exist on that machine.
In order to support the app on lower versions of the operating system you will need to wrap the calls to those APIs with an appropriate "IsAPIPresent" check:
https://learn.microsoft.com/en-us/uwp/api/Windows.Foundation.Metadata.ApiInformation
Thanks,
Stefan Wick - Windows Developer Platform
Possible Solution:
I was facing with the EXACT same issue. I have my SDK 15063, and I have installed Visual Studio 2017 afresh, which also installed SDK 15063 implicitly, but I still kept on getting the same deployment error DEP3321.
I solved this issue in this way -
Just go to the "Solution Explorer", on the right side of Visual Studio and do the following steps in this order -
1) Just right click on the project you are deploying
2) Press "Unload Project"
3) Right click on the project_name(unavailable) and press Edit project_name.jsproj. It will open an xml file on left hand side
4) Search for "TargetPlatformVersion" and "TargetPlatformMinVersion". Both are placed next to each other. Mine looked like this -
10.0.15063.0
10.0.15063.0
since mine Error DEP3321 explicitly stated that 'you are currently running version 10.0.14393.1715, so I replaced my "TargetPlatformMinVersion" from 10.0.15063.0 to 10.0.14393.1715 -
10.0.14393.1715
5) Now save it, Ctrl+S
6) Right click on "Solution Explorer" and press Reload Project and press Yes to the popup if you get stating that project is already loaded.
You are done. Just do what you normally do, Build (ctrl+shift+B) and then Debug - F5 or Ctrl+F5.
This way the project got deployed for me.
I have Visual Studio 2013 with Windows Phone 8 SDK installed. The phone is unlocked and recognized by the machine. However, very often Visual Studio doesn't list either "Device" (not emulator either) in the list of deployment target. If I create a new solution and add a Windows Phone application, then I can see "Device" and emulators in the list, but when I load an existing solution with project of various types, I can only see "Start" and "Attach to IIS" as deployment choices. I tried to delete solution temporary files, but this didn't help.
So what makes VS lose Windows Phone deployment options and is there any way to fix it?
As #WiredPrairie suggested, setting a project as a Startup project (and the single Startup project) resolved this issue. Sometimes you may need to delete *.suo file and reload the solution.
In case anybody has problems in getting the "Device" option in the application toolbar, I noticed that it makes a difference, which programming language you use: using a Lumia from Nokia:
with a windows phone c++ project Visual Studio did not list the "Device", just various emulators, with Windows phone 8.1 visual basic project it did list the "Device" option. Probably there are no c++ libraries on the phone. Just to let you know.
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.
I am working on creating a windows mobile application and I have a quick question. I have looked around for the answer and cant find anything. Is it possible to run a windows mobile application on a physical hardware device from visual studio? I don't need to be able to debug really, I just would like to be able to select my device and have it build, copy to the device, and run. Is there anyway to set this up?
There is a "Device" toolbar that should let you choose your target device. Check for it under the View -> Toolbars menu (for VS 2008... not sure if you are on a different VS version).
If you are only showing emulators, you might need to install the windows mobile 6 sdk (I don't know for sure, but I do know I also have that installed... could be that this only includes the emulators as well).
Update:
It might also be worthing right clicking on your project in the solution explorer and selecting properties. From the properties page, go into the Device tab. It might be that some devices are listed there that are not listed in the target device drop down list on the toolbar. Worth a shot, but no promises.
It's simple believe me.
I'm currently working on Visual Studio 2008 and I have already installed Windows Mobile 6.0 SDK. It's simple just two steps.
Plug your device to your computer via usb cable then you should see the ActiveSync connected your device.
Open VS and choose from target device menu that "Windows Mobile Professional Device", then push the VS Debug button (it's slower that simulator but it's working perfectly). (look at the picture)
alt text http://img38.imageshack.us/img38/3638/screenhy.jpg
I hope this will be able help to you.
Yes. If it's like mine (Verizon Motorola Q) Visual Studio will copy several files to the device and the device will prompt you to allow them. You only have to do that part once. Then when you debug on your device you may get a prompt to allow the program you're debugging to run. It seems to copy your program over to a folder in the devices "Program Files" folder and runs it from there. And it leaves it there even after you stop debugging.
And one more thing. With Visual Studio 2005, you'll need at least the standard edition to do mobile development. With Visual Studio 2008, you'll need at least the professional edition.
Thanks for the help everyone. My solution was a mix of a couple answers. I had to switch the project to the Windows Mobile 6 Professional SDK first and then I was able to select "Windows Mobile Professional Device"