I have a windows desktop app done in VB. Can I have same app to work on windows mobile also?
As far as I know windows mobile development is different and windows desktop development is different. Can we have 1 single app that works for both(windows mobile & windows desktop)?
I have developed a windows mobile app before and I had done it through Visual studio(Xaml and C#).
I have also worked with windows desktop app visual studio(c#).
If it is possible to have single app for both mobile and desktop then will the existing VB.net app will work? Or do I have to build a separate app from scratch?
That depends on what you mean by "Windows Mobile".
If you mean the old Windows that runs on old mobile devices called "Windows Mobile", then yes, you can have a single app for desktop and mobile providing you use .NET Compact Framework.
But if by "Windows Mobile" you mean "Windows Phone", then no. You cannot have a WPF/WinForms application that can run on Windows Phone devices. However, you can develop Windows Store app (or Universal Application for Windows 10) using Windows Runtime, that will run on desktop, tablet or phone.
What is Universal Windows Application?
Related
I am new to Windows Development. And as per criteria of my Internship they want an application from me on windows store whether UWP, WPF or Windows form. Now as I made an application on Windows form(C#). My question is that how to publish my application on windows store? Or whether a Windows form application can be published to store or not. Or I have to make a WPF or UWP application?
As a developer who creates some apps for the Windows Store, I think that you can only submit UWP. Because Visual Studio only generates store packages if you are working in a UWP project.
However, Microsoft is working in Project Centennial a desktop to store app converter.
I've made an educational game for Windows Phone 7 with XNA - which is now a dead technology. But through MonoGame and Xamarin I have been able to port it to Android. Now I need it as an app for Windows tablets, windows 8 app or windows 10 universal app.
What is the best route to this? I'm using Visual Studio 2013 with Xamarin Business edition. And I don't know enough about my options. Should I start with the XNA version or the Android/Xamarin version? What template or architecture is best. Or do I need to do a complete rewrite (only keeping the C# business logic)?
I need to make an app for a windows ce 6 device, but i haven't find any emulators for this type of operating system and I don't have the device. I only get windows ce 5 or windows mobile 5 and 6 emulators. If a write the app for a windows mobile 6 can it be installed afterwards on a windows ce? will it work? They both use net framework 3.5. If not what can I do? Any suggestions?
Thank you.
You have to write your app against Windows CE not Windows Mobile!
Apps written, compiled against Windows Mobile have references to shell functions (aygshell) that are not available on WM.
You should get a Windows CE Platform SDK for the device you are writing for by the OEM. That should enable you to run an emulator.
see also https://msdn.microsoft.com/en-US/library/ee504799%28v=winembedded.60%29.aspx
BTW: you can run Compact Framework app on your PC without any change as long as they do not reference any CE only functions.
I need to develop an app for a Windows Embedded Handheld 6.5.
I start looking for some tutorials or documentation for a "Getting Started".
After all I think I got the main facts but something still wonders me.
I look everywhere for an SDK or DTK but found nothing.
I found a small "Tutorial": URL HERE
But everything refers to Windows mobile 6.5 SDK and DTK.
So is there really a difference between them? Or why do I need Windows Mobile 6.5 to develop for Windows Embedded Handheld 6.5?
Or am I totally wrong?
For me Windows Mobile 6.5 and Windows Embedded Handheld are just two names for the same.
MS often did re-brand products to make you think it is something different or better. Especially with the Windows Mobile Pocket PC series.
You need the Windows Mobile 6.5.3 DTK to develop fur such devices: http://www.microsoft.com/en-us/download/details.aspx?id=5389
Although the DTK is OK so far it does NOT reflect the changed Screen Layout, for example if you design a form using it, Visual Studio shows a standard form with a large caption (Windows Mobile apps do not have a caption bar) and a normal menu bar (WM 6.5.3 devices show a larger menu bar).
Further on MS dropped some API functionality (SHFullScreen) without any notice. That's life.
Microsoft has renamed the Windows Mobile Platform to Windows Embedded Handheld.
There where releases in the following order:
Pocket Pc 2000
Blue desktop theme as a default. Coloured windows logo inside the start button.
Pocket Pc 2002
Blue desktop theme as a default. Coloured windows logo inside the start button.
Pocket Pc 2003
Blue desktop theme as a default. Coloured windows logo inside the start button.
Pocket Pc 2003 SE
Blue desktop theme as a default. Coloured windows logo inside the start button.
Windows Mobile 5.0
Blue desktop theme as a default.
Windows Mobile 6.0
Green desktop theme as a default.
Windows Mobile 6.1
More optimized than 6.0.
Windows Mobile 6.5
Change: New dark blue desktop theme as a default.
Windows Embedded Handheld 6.5.3
Change: Like Windows Mobile 6.5 but with the Start-Button on the bottom
Windows Embedded Handheld 6.5
Change: Just renamed 6.5.3 back to Windows Embedded Handheld 6.5 to add confusion.
From Windows Mobile 5.0 or later they come with a Windows CE 5 kernel and have the 32 MB of virtual RAM per process limit, so they didn't benefit form new Windows CE releases, which naming is as fucked up like the Windows Mobile naming.
On Windows CE you got:
Windows CE 5
Windows Embedded CE 6
Windows Embedded CE 6 R2
Windows Embedded CE 6 R3
Windows Embedded Compact 7
Windows Embedded 8
Windows Embedded 8 Industry
Windows Embedded Compact 2013
But wait, there is more. The Windows Mobile Platform died is no longer supplied with features/improvements, since the Microsoft .NET Compact Framework Team was moved to develop the Windows Phone Plattform. So these are the bastard childs and the spiritual continuation of Windows Mobile based on Windows Phone with some framework additions for datacapturing. Which include:
Windows Embedded Handheld 8 (also named Windows Embedded 8 Handheld)
Based on Windows Phone 8
Windows Embedded Handheld 8.1 (also named Windows Embedded 8.1 Handheld)
Based on Windows Phone 8.1
Windows 10 IoT Mobile Enterprise
Based on Windows 10 Mobile, which is based on the Windows Phone platform. We got a new rename, yay.
Windows Embedded 6.5 is backward compatible with legacy Windows Mobile applications.
As per Microsoft:
Windows Embedded Handheld 6.5
Built on Windows Mobile 6.5 to power line-of-business applications in
field mobility, transportation, retail and more.
Application compatibility with Windows Mobile 6.5, and a consistent SDK and set of APIs.
So I think you just should use Windows Mobile 6.5 SDK.
Recently I was asked to work on a project which was developed for an aviculture company.
The client asked if I can make the application which was being developed in C#, to work on a tablet.
So i want to know if i finish the application in c# normally Will I be able to:
1.Use the mono for android and compile the whole project with that and get an android app easily for being used in android devices?
2.Use the executable project on a Windows 8 tablet without any changes?
I would be grateful if any one could answer these two questions.
It depends which tablet you're talking about.
On a Windows RT (ARM based) tablet like Surface, only Metro apps are supported. There are a few desktop apps, but only Microsoft can make them. So if your app is a desktop app, it won't run on Surface RT.
On a tablet with the "real" Windows 8 (x86 based, e.g. Surface Pro), you can run the same apps as on a PC.