The question is the title.
I have downloaded http://www.microsoft.com/en-us/download/details.aspx?id=19004. It's currently being installed. It takes care of the IDE part.
Is there anything else that I need?
And secondly, is there a start-up tutorial to create a project and a "Hello World!" app?
you find here a couple of Win CE tutorials, they are written for the colibri modules but the getting started tutorials should help you with most of the other ARM Win CE systems.
http://developer.toradex.com/knowledge-base/getting-started-with-colibri-modules
Related
I'm new to programming for windows.
and I have one simple question for you, but it is unclear to me.
What is the different between Windows RT development of Windows 8 for tablets? (language c#)
Is it possible to write a single application - that will work in both systems?
If there is a link that read - will be happy.
Short answer: if you're on C# it doesn't make a difference.
For a more elaborate explanation, see this question.
My company is currently hosting a legacy application that contains a great deal of vbscript (client side browser and task automation ), classic asp and some vb 6. (I know pretty old) While we are in the works of rewriting a lot of it piecemeal. We will eventually need to support windows-8. Is there a list of issues or compatibility tips to look at in supporting windows 8?
Update
VB6 Running on Windows 8? partially answers mine as far as VB 6. But still concerned about vbscript.
vbscript support in windows 8 covers a good deal more
Everything that runs on Windows 7 should run on Windows 8 in desktop mode. None of the technologies you list will work in the new Metro style applications.
AS long as you have the VB6 runtime DLL it should be backwards compatible.
IIS7 and 7.5 both support Classic ASP pages, so you shouldn't have any problems. In the near future, you want to get those migrated to .NET.
As far as I know, JRuby runs only on full JVM. I found this version of JRuby which runs on Java Micro Edition devices, however it's marked as EXPERIMENTAL AND RESEARCH ONLY
Are there any other options for running Ruby application on Windows Mobile devices?
I'm not sure what you are asking. Your title and your question refer to Ruby, but your description talks about JRuby. Which are you asking about?
I know regular Ruby can run on Windows Mobile (see Rhodes, for example, or RubyOnMobile).
Here's my problem. I'm currently trying to develop a .Net Compact Framework 2.0 application (in C#) to a Windows CE 5.0 device.
Firstly: How do I debug/emulate the application in Visual Studio 2008 ? I doesn't mean debugging an application already deployed on the device, but debugging the version on my desktop. I have limited or no access to the prototype device.
Secondly: How do I integrate it with the OS image made by Platform Builder for Windows CE 5.0 ? Do I need to ?
Thank you for your time
You have a few options. One would be to install the Emulator BSP, roll your own emulator image, build a custom SDK and install it, then debug targeting that emulator. It's fairly simple to do.
That said, I still wouldn't do it. A far better option is to just go buy a cheap WinCE device like an eBox 4300 jump start kit. It's way easier, faster and and more reliable to target real iron.
As for integrating the app, it's like any other. Make sure you have the CF component included in your OS design from the Catalog, then add your app to your PROJECT.BIB (and REG and/or DAT files if needed) and run makeimg again.
Okay, so thanks everyone for the quick and nice answers. Although I've found my own solution yours may be as valid as mine.
Basically what I didn't tell you (because I didn't really know it either) is that I didn't actually need to emulate the OS, I only needed to work with the framework. I found the best way to "emulate" such situation here.
Also, I found that the easiest way to deploy the application to the device is to use ActiveSync and I found just the right (MSDN) article for it.
Ctacke: It's probably due to my only learning this type of development, I somehow made an error while creating/installing "my own SDK" so the Visual Studio stopped functioning properly. But of course some digging made that go away. Thanks anyway. I liked the idea of developing with a testing device, unfortunately the company I work for already picked a device but they couldn't issue me a prototype for development purposes yet.
Frans, I haven't found your CE simulator, but I'm pretty sure that I didn't look for it enough so thanks.
You should use the emulator which comes with the CE SDK. You can use that directly from vs.net, and it has all win CE features. DEbugging then works on that emulator, so you can step through your code as if it's running on a device.
Can I write and compile code for this on XP? We have utilities for our apps that use activesync and now will be adding Vista/WMDC - and I was hoping I don't have to have another development OS (Vista) to develop and compile on.
I have not seen much documentation for the API for WMDC - can someone point me to some useful references for it?
hummm... ActiveSync, so Windows Mobile am I right?
all you need is the SDK and Visual Studio (well, this last you don't need cause you can compile everything using the command line, but, very nice to have for such applications)
there are plenty of SDKs for what you need, for example PocketPC, Windows Mobile, etc...
the sdk contains everything you need to build, compile and deploy an application, works fine on windows XP (what I currently use) and with ActiveSync, you can even debug the application in the device ;)
added:
unfortunatelly there is no SDK for the WMDC. The only thing you have are the 4 libraries in the %WinDir%\Windows Mobile. It contains 4 libraries named as "Microsoft.WindowsMobile.*.dll". Additionally you don't get any documentation on the libraries themselves which makes it hard to use.
As you use the RAPI (I think by using the OpenNETCF library) most of the applications shall still run under WMDC as the included RAPI seems to be backward compatible. The included RAPI itself is in a new version.
taken from MSDN forum
I hope this helps for the moment.