ZDNet UK


Skip to Main Content

ZDNet.co.uk - Winner of Best Business Website 2007
  1. Home
  2. News
  3. Blogs
  4. Reviews
  5. Jobs
  6. Resources
  7. Community
  8. My ZDNet

 

ZDNet UK RSS Feeds


Office applications Toolkit

What's .Net got for the mobile developer?

Lamont Adams Builder.com

Published: 29 Jan 2003 09:43 GMT

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

This .Net Compact Framework opens up an entirely new world of devices for .Net developers, but is the environment at all like its big brother? Obviously, in shrinking a 23-MB runtime library into less than 1.5 MB for a mobile device, Microsoft had to discard something. So what did they leave, and do the changes preclude any compatibility between the two frameworks? Let's answer the last question first and then take a look at the primary ways the Compact Framework differs from its full-scale sibling.

The question of portability
In creating the Compact Framework, said Microsoft's Ed Kaim, the aim was twofold. Beyond the obvious goal of coming up with a .Net runtime that was smaller and less resource-hungry than the full version, Microsoft wanted to centralise development for all platforms in Visual Studio .Net. "We wanted to make it possible for a typical Visual Studio .Net developer to do everything they needed from inside the IDE, [and] keep the development experience the same for all platforms," Kaim said.

Missing from this mission statement is any kind of "write once, run anywhere" portability, and Microsoft has been sending mixed messages on the subject. The latest example of this sort of thing is the newest episode of MSDN's "The .Net Show," which manages to send contradictory messages about whether it would be reasonable to assume that code written for one framework would run on another. So what's the real story?

Kaim responded to this confusion by pointing out that although "write once, run anywhere" wasn't really a primary goal, it nevertheless is possible to achieve this level of portability, with due consideration and planning. Existing .Net applications will need to be recompiled for the Compact Framework, he said, but assuming that they don't reference any assemblies that are absent from the mobile API, there's no reason why the same code base can't be used with both runtimes.

Next

Previous

1 2


  • Email
  • Trackback
  • Clip Link
  • Print friendlyPrint with Konica

Did you find this article useful?
159 out of 314 people found this useful


Full Talkback thread

0 comments

Company/Topic Alerts

Create a new alert from the list below:












Featured Talkback

In association with Intel
Why do so many (virtually all) software packages think that they are so important that they have to be started automatically every time the computer boots? What is the largest number of "speed access", "update check", "camera download" and whatever other background programs you have ever seen running? Of those, how many did you really need?

By: J.A. Watson

Read full story:
Annoying software: a rogues' gallery

Vista Upgrade Blog

Vista - Still Running and Stable After...

Six weeks ago, when I wrote Renewed Adventures with Vista, I wondered if Microsoft had finally managed to fix it sufficiently that I wouldn't be forced to give up on it after a few... More

Post a comment

Official MS Windows 7 Bloggers

Check this out: http://blogs.msdn.com/e7...spx Its an official blog "Engineering Windows 7" Nothing. That's what is revealed. Until there is real... More

5 comments

Microsoft's Mojave just a desert vista

It didn't seem fair to wade into Microsoft's “Mojave Experiment” advert quite so soon after the flat earth incident. But The Economist has no such qualms: in this week's issue, it wonders... More

6 comments