I am upgrading my Windows Mobile 5 project to a Windows Mobile 6 project.
The first step (at least so it seems to me) is to get the Windows Mobile 6 SDK installed.
When I went searching for this I found the following installs that both seemed to fit what I was looking for:
Windows Mobile 6 Professional SDK Refresh.msi
Windows Mobile 6.5 Professional Developer Tookit (USA).msi
So, the question is, do I need these both? and if so, what order do I install them in? and is there any other installers/steps I am missing?
It depends on what you're targeting. There are loads of SDKs, but generally what they bring to the table are emulators and SDK-specific stuff (like additions to the Microsoft.WindowsMobile namespace). Otherwise they really don't do a whole lot. For example you can continue to use just the PPC 2003 SDK to write and deploy apps on WinMo 6.5, you'll just be missing availability of the stuff that was added to be 6.5-specific.
Persoanlly I'd recommend installing the 6.5 Pro (and maybe standard too) SDKs and foregoing the 6.0 SDK unless you need to do emulator testing for something like a 6.0 or 6.1 device.
Related
I need to work on unity 3D and Hololens to predict and map the movement of a machine.I wanted to ask is it possible to use Hololens and trace the movement of a machine by using windows 8? I would also appreciate if anyone could help me with the total installation procedure of how to install and use Hololens since I am new to it.I found some installation guides but that requires Windows 10 and since I have windows 8, anything related to it such as which packages to install, would be very useful.Thank you everyone for your time.
Best Regards
Safayet
Can I use windows 8 to install and use Microsoft Hololens?
No, you can't.
To build for Hololens you need UWP and UWP needs the requirements below:
Unity 5.2 or later
A Windows 10 Pro, Enterprise, or Education (The Home edition does not support Hyper-V)
Visual Studio 2015 RTM, (the minimum version is 14.0.23107.0). Please
note that earlier versions, for example Visual Studio RC, are not
supported in Unity 5.2.
You’ll also need to install the Windows 10 SDK.
8 GB of RAM or more
The source for this information from Unity's blog. In short, you can't because the SDK requires Windows 10.
I have a .net CF 2.0 application(app also uses some C++ libraries), running on a windows mobile 5.0 device. And we are planning to use a new device in Windows Embedded 6.5.
Here can I use Xamarin studio to port my app from .netCF 2.0 ?
So that along with device upgrade I will have our app code-base platform independent.
Pros/Cons/thoughts ?
Xamarin only supports Windows 8 (plus 8.1 and 10 runtime coming soon) - not WEH 6.5
If you are looking to transfer to Windows 8 and you are looking to just click the app and hope it ports to Xamarin that isn't going to happen.
If you are coming from WM5 on Compact Framework, its not going to be a nice port. I would recommend a write from scratch and build again. Copy and paste code sections as necessary but it is certainly a build the projects and views from scratch.
You might get some good reuse out of copying C# code across depending how extensive that is, but if it is tied to platform specifics you will run into many issues.
Remember you are going from CF 2.0 to PCL. From WM5 to Windows 8. They are very different.
Also those C++ libraries may have significant problems if they are WM5 specific.
As Microsoft said that windows 8 and windows phone 8 share the same code base. If I use visual studio 2012 RC write an application for windows 8. I want to know whether I can install and run the same application on windows phone 8?
If the answer is yes we can prepare ourselves for windows phone 8 SDK by learning Visual Studio 2012 RC for windows 8 today!
Right now they haven't announced everything, so this is just my speculation.
I guess that you will not be able deploy the same app (xap file) to WP8 and Windows 8. This by design. Why? Because they are very different systems. Your beautiful, fast and awesome Windows Phone app will suck on Windows 8. There is no silver bullet. It's the same for HTML. You have to create separate mobile version of the web app, otherwise nobody will use it.
They share the same kernel and probably plenty of APIs. But that doesn't mean the runtime environment in which your applications run is the same. E.g. very different form factors make it necessary to adapt the app anyway. Since they never said that Windows Phone 8 has the same application programming model as Windows 8 you can at the moment safely expect not to be able to deploy the same app to both Windows 8 and Windows Phone 8.
That being said, you probably can expect to share a lot of code between both systems, especially if you're using either C# or C++ (with native apps coming to WP8 too).
Application compiled for WP8 won't just run on Windows 8, but you can share lot of code into common libraries.
There is a chapter in Windows Phone 8 SDK about targeting both Windows 8 and Windows Phone 8 development. Mostly is possible either by Portable Class Libraries, referencing common files both in W8 and WP8 projects or using Windows Runtime Components.
http://www.microsoft.com/en-us/download/details.aspx?id=35471
Many Application designed for wp8 work on windows8 also as The developer have also to decide whether it will work in both of then,usually windows8 has not enough graphic and motion control so some WP games do not run on windows8,, You can always see any app permission notice to understand whether it work on wp8 or not on other hand there were also some windows game that has as much graphics that WP could not run,,
Like if you want game like assassins creed it will run on both operating system(WP,window) but in different manner
So it's chooses by game properties that define cap package to run or not
My company is planning on developing for Windows Phone 7. The build server we have, however runs Windows Server 2008. According to the Windows Phone SDK release notes I've read that only Windows Server is not supported for the SDK.
Does anyone have any experience on whether there's a possible workaround to have a Windows Server 2008 machine build Windows Phone 7 projects?
Update: I'm interested in building on a WS 2008 as we're talking about a project with a larger team where continous integration and centralized builds are essential. I'd be hoping we wouldn't have to set up an additional Windows 7 build server for this task.
Most the issues of this nature come into play meeting the emulator's requirements rather than the development tools.
With that said some are hacking around the walls put up to stop people going into the unsupported territory of WS2008.
Judging by your requirements I'd say dive in. If you have the option to test on device or in emulators in Win7, that will place you well.
This post likely of interest.
Aaron Stebner's WebLog : How to install the Windows Phone Developer Tools CTP Refresh on Windows Server 2008
If someone is interested here is instruction how to modify ISO image of the WinPhone 7.1 SDK for installing it on Windows Server. Basically it's the same Aaron Stebner solution, the only difference is that you need to modify it in the ISO image.
Can I develop an application targeted to run on CE 5.0 using the Visual Studio 2005/CE 6.0 development environment? Or do I need to find the CE 5.0 development downloads on microsoft.com rather than the latest CE 6.0 ones?
Having been 'given' a hardware platform of an ARM based touch device running CE 5.0, along with an SDK from the device's manufacturer, I am now looking at the feasibility of porting our C++, VS2008 built, Windows XP/Vista/7 application to run on the smaller platform.
This is our first foray into the world of CE, so please forgive any ignorance on the subject.
This question is a bit old and possibly stale at this point, but I thought I'd toss in an answer for future views on the subject. After all, as much as I like CE 5.0, its a bit old and stale itself. :)
First off, understand that Visual Studio 2005 and the CE 6 dev environment are two distinct entities. While CE 6 runs as something of a plug-in for and depends upon VS 2005, the converse is not true. So if you’re doing CE 5.0 application development, you can just as easily do it with (standalone) VS 2005 as VS 2008, so long as you have a suitable SDK with which to link your Smart Device project.
As for developing for or porting to a CE 5.0 platform, you’ll definitely need to stick with the CE 5.0 bits only. Consider CE 6.0 to be a completely different OS with a completely different memory model, user/access paradigm, etc. Microsoft provides the Standard SDK for Windows CE 5.0 as a free download, available here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=fa1a3d66-3f61-4ddc-9510-ae450e2318c3
Note that the SDK linked to by JoelHess is for Windows Mobile 5.0, which differs in significant ways from Windows CE 5.0.
Alternately, you mention an SDK from the device manufacturer…this type of custom SDK typically includes all or significant portions of the Standard SDK plus the device-specific components required to get your platform up-and-running.
A final point: you only mention developing an application targeted to CE 5.0, but if you also need to be able to build the platform image, you’ll need Platform Builder 5.0. A 120-day eval edition is available from Microsoft (unable to post a second link due to my obvious newb-ness).
I'd recommend sticking with the v5 stuff. You could probably get binaries that would run, but none of the debugging tools would work.
Here's a link to the SDK:
http://www.microsoft.com/downloads/details.aspx?familyid=83A52AF2-F524-4EC5-9155-717CBE5D25ED&displaylang=en