.NET Compact Framework; Past, Present and Future

Feedback to the .NET Compact Framework Team

Neil Cowburn — Fri, 04 Feb 2005 11:51:00 GMT

re: .NET Compact Framework; Past, Present & Future

Chris Tacke — Fri, 04 Feb 2005 17:10:00 GMT

CLR Hosting, CLR Hosting, CLR Hosting....

re: .NET Compact Framework; Past, Present & Future

Alex Yakhnin — Fri, 04 Feb 2005 18:38:00 GMT

Mike,

You can see my feedback here:

http://blog.opennetcf.org/ayakhnin/PermaLink.aspx?guid=65e8102c-c1ab-4639-acd2-5bc32415bac9

-Alex

re: .NET Compact Framework; Past, Present & Future

Kevin Daly — Fri, 04 Feb 2005 20:54:00 GMT

Very cool photo by the way.
One thing you didn't mention was the XML support in v1.0, which is basically unmentionable (although it basically just carries on the unmentionableness of the XML support in eVT): "Oh, so I can't use XML serialisation? Never mind, I'll just XPath and get at the data directly..No XPath? Oh. Damn."

re: .NET Compact Framework; Past, Present & Future

Jeff Parker — Fri, 04 Feb 2005 21:13:00 GMT

Mike, one thing I have never heard of or found out about and sorry if it seems a silly question, but will the compact framework be released right along with the .net framework 2.0 or will it be a seperate release? I am talking more along the lines of timing. Also will VS 2005 be one of the main developer environments for the compact framework?

No one has ever been clear on this yes or no. I do not like to think of the compact framework as something different. Yeah we have different controls but everything basically works the same. One of the things I have loved about this ever since the compact framework has come out is 1 dev environment, one language C# for me, and one frameowrk. Which has always been nice. Ever since .net was released it has been like one brain one methodology in programming if you are doing windows, web, or compact, and I have just been having a hey day as a programmer, .net is like being is kid in a Candy store because I can basically do anything.

.NET CF 3.0

Daniel Moth — Sat, 05 Feb 2005 02:36:00 GMT

.NET CF 3.0

re: .NET Compact Framework; Past, Present & Future

Daniel Moth — Sat, 05 Feb 2005 16:05:00 GMT

Jeff,

Yes NETCF 2.0 will be released, like .NET 2.0, as part of the Whidbey package that includes VS2005.

In addition, this time round NETCF will also have a standalone SDK (like its big brother always had) so 3rd party tools could be developed for targeting it (today it is just VS.NET 2003 Pro and above).

Cheers
Daniel

re: .NET Compact Framework; Past, Present & Future

Kevin Daly — Sat, 05 Feb 2005 22:30:00 GMT

I'm surprised there's been very little buzz about the standalone SDK (I'm also horrified at the repetitive vocabulary and the odd missing word in my previous post, but I digress).
At the time the Compact Framework was originally released, the fact that development was only possible with VS 2003 Professional was not exactly met with shouts of joy, in view of the price disparity with the free embedded Visual Tools. While nobody has a right to expect a free lunch (on the other hand they're always welcome), a good argument can be made that there is as much software for Windows Mobile as there is because the previous generation of tools were *not* just accessible to the "Enterprise" market (I must remember to make a long, insulting blog post about the universal obsession with the "E" word soon), but to many skilled and innovative developers, including some from countries with very low per capita income.
So anyway, in my Never-Previously-Known-To-Be-Humble opinion, the standalone SDK is a key element in the future success both of the NETCF and the Windows Mobile platform (does anybody know by the way whether it will include the emulator? - that would be very nice). There's no reason why tools of the SharpDevelop variety could not be created for the NETCF, which would give us back the breadth of access we had with eVT. I'm all in favour of Visual Studio being the *best* environment for NETCF development, but it's good to have something for everyone else as well.
Which brings me back to my surprise that there has not been more comment on what I see as a crucial development. Part of this may be due to the fact that developers seem to be contributing less these days for some reason to the general enthusiast Pocket PC sites, compared with all the other content of the "Look, shiny!" variety (OK that was elitist and I'm very, very sorry. Honest.)

re: .NET Compact Framework; Past, Present & Future

Andy Wigley — Tue, 15 Feb 2005 20:50:00 GMT

I welcome the intention to focus on making it easier to deal with transiently connected networks. New APIs to allow easy switching between networks would be great - at present it's not at all easy to switch between an 802.11 and GPRS network, on devices that support both.
Kind of in the same vein - one goal of .NET CF 3.0 has to be some level of compatibility with Indigo. In general, I'm not convinced that the goal of compatibility with the desktop developer's 'way of doing things' is that important to us on devices, but the unified messaging API that is Indigo is going to change the way developers look at distributed applications, and devices have to be a part of that.

A Market Within A Market (was .NET in HD)

MikeZintel's WebLog — Tue, 14 Mar 2006 07:38:51 GMT

In the late 90s, I worked on the IrDA infrared connectivity technology. My team built the protocol stacks...

My Own Pirate Radio » .NET on the Xbox

My Own Pirate Radio » .NET on the Xbox — Tue, 14 Mar 2006 17:35:41 GMT

PingBack from http://myownpirateradio.com/2006/03/14/net-on-the-xbox/

MikeZintel s WebLog NET Compact Framework Past Present and Future | Portable Greenhouse

Mon, 01 Jun 2009 22:43:36 GMT

PingBack from http://portablegreenhousesite.info/story.php?id=14797