Nick's .NET Travels - All Comments

re: What works/What doesn’t in Windows Mobile 6.5 Widgets

soundbbg — Sat, 20 Jun 2009 15:59:08 GMT

That's right..

Just like $.get cannot working.. :)

that's a very useful note..

Extends widgets using ActiveX

Extends widgets using ActiveX — Tue, 16 Jun 2009 06:56:26 GMT

Pingback from Extends widgets using ActiveX

Another bee4Mobile.Net Control

Nick's .NET Travels — Mon, 15 Jun 2009 10:55:53 GMT

In my previous post I talked about the ColourPicker, the ProgressBar and the OpenSaveDialog controls

Make My Windows Mobile 6.5 Widget Into a Windows Vista/Windows 7 Gadget

Nick's .NET Travels — Mon, 15 Jun 2009 02:46:10 GMT

Having shown how easily you can build a widget that wires up some data using Entity Framework, ADO.NET

Windows Mobile 6.5 Widget and ASP.NET AJAX 4

Ferry Meidianto — Sun, 14 Jun 2009 09:07:35 GMT

Nick Randolph wrote a good example of utilizing ASP.NET AJAX 4 (pre-release), ADO.NET Entity Framework

re: Extending the Widget model on Windows Mobile 6.5

Christopher Fairbairn — Wed, 10 Jun 2009 00:42:22 GMT

I'm interested in this extensibility story too.

I'm not expecting the market place to allow widgets that deploy CABs from external servers.

If they did it would seem to rather weaken their response as to why widgets must be deployed via the marketplace (security etc), as any bad bits could be pushed into the "uncontrollable" CAB file.

I'm wondering if another scenario would be to package up your widget as a *.CAB instead of a *.widget file. If you deployed this from your own server it could install the ActiveX control and a custom setup.dll could directly launch wmwidgetinstaller.exe to install the embedded widget file).

You would probbably loose the ability to publish via the market place, as again I assume they won't accept such a CAB for publication. But it may be a scenario for line of business / inhouse developments.

I've started porting Chris Craft's 30 days of windows mobile apps to widget form (windowsmobileapps.codeplex.com) but am quickly getting to the ones which will require access to GPS / phone functionality.

So you want Silverlight on your Windows Mobile device?

Nick's .NET Travels — Tue, 10 Mar 2009 22:05:12 GMT

At the last couple of Mix events Microsoft has been talking about having a version of Silverlight for

wan accelerators

wan accelerators — Wed, 04 Feb 2009 13:29:14 GMT

We already saw the Diamond and Omnia in action and you’ re free to replay the game here. The Diamond surely has a few things to offer over the Omnia (VGA screen, smaller size, 3D acceleration, and magnetic stylus) but it also has its issues here and there

re: How North Sydney Council Deals with an Economic Crisis

Nicholas — Mon, 02 Feb 2009 08:17:21 GMT

Completely agree, many councils have a large budget for placing artwork around the City when the money could be much better spent like you said on trees or improving safety around parks, roads etc.

Retrieving Map Images from Virtual Earth Web Services

Nick's .NET Travels — Mon, 19 Jan 2009 12:06:09 GMT

In my previous post on the Virtual Earth Web Services I showed how you can use the Imagery Service to

pZing and Tablet PC development

Nick's .NET Travels — Sat, 17 Jan 2009 02:31:38 GMT

I posted earlier on the Getting Started with Windows Live Tools for Visual Studio whitepaper that is

re: iPhone Killer Application

nick — Wed, 14 Jan 2009 11:53:09 GMT

Oh, now you guys are getting bogged down in the details. After all this is an application designed for the iPhone - you don't expect it to cater for "real world" scenarios, do you?

re: iPhone Killer Application

David — Wed, 14 Jan 2009 08:25:11 GMT

And if your iphone is stuffed and you're returning it ... how are you going to run this application?

re: iPhone Killer Application

AC — Wed, 14 Jan 2009 07:26:49 GMT

tee hee! talk about "killer" app... assuming the app can still run. maybe get a second iPhone as backup for running Return to Sender.

iPhone Killer Application

Nick's .NET Travels — Wed, 14 Jan 2009 06:01:18 GMT

Today at Geek Coffee we were considering what the next big killer mobile application is going to be. 