Advertisement
Promo

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 EPSON

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:












Video icon

Video

Win a BlackBerry with Vlingo voice recognition

Win a BlackBerry with Vlingo voice recognition

What is ZDNet UK's usual tagline?

Competition closes - 14 Jan 2010

Discussions

J.A. Watson J.A. Watson

Google it

Friday 25 December 2009, 1:40 PM

3 comments
J.A. Watson J.A. Watson

Google it

Friday 25 December 2009, 1:38 PM

3 comments
Shibley R Shibley R

Question!

Friday 25 December 2009, 11:09 AM

3 comments

Vista Upgrade Blog

How to Upgrade From Windows Vista to W...

Did you get the news? Microsoft has unzipped its kitty and kept its latest, supposedly the best, offering on display. This is the brand new version of Microsoft operating system, named... More

Post a comment

Tinsel on the TARDIS

There were shepherds on the hill, and the Doctor popped his head out of the TARDIS and said "you might want to see this" and they were astounded. WHY do we pay for a TV license?... More

Post a comment

Can I have fries with that? (Consumer...

Licence policies of Tech company's have been for a long time both complicated and 'Dick Turpin-esque', people just click 'I agree' without reading the Agreement. I do the same, but... More

1 comment


Skip Sub Navigation Links to CNET Brand Links

Help

Become part of the ZDNet community.

Newsletters