kavachai

Here is a method that does convertion:

public InputStream stringToInputStream(String text) throws UnsupportedEncodingException {
	return new ByteArrayInputStream(text.getBytes("UTF-8"));
}

Sometimes message from exception that occurred inside .Net CF classes doesn’t look handly at all:

An error message cannot be displayed because an optional resource assembly containing it cannot be found.

The thing is that error messages are actually in the resource assembly which is not installed on the device. So to fix the problem you just need to install this assembly:

1. Navigate to CompactFramework folder in the SDK which is “%Program Files%\Microsoft.NET\SDK\CompactFramework”.
2. Navigate to Diagnostics folder under desired .Net CF version (“v3.5\WindowsCE\Diagnostics” for 3.5 or “v2.0\WindowsCE\Diagnostics” for 2.0).
3. Copy resource CAB file to device according to the language you want and install it.

As new articles and opinions pop up after official presentation of Windows Phone 7 I’m getting more and more excited about new OS.

• Windows Phone 7 Interface: Microsoft Has Out-Appled Apple describes new Windows Phone 7 as a new paradigm in user experience. Mostly I agree with the author, but it looks like he is too excited about data-centric UI. I believe that both data- and function-centric approaches have their followers and nobody knows to which of them applications from third developers will turn Windows Phones.
• Windows Phone 7 Series: Everything Is Different Now makes new OS even more clear. In the same time we as developers still have some very important questions waiting in the shadows, like:

But here’s a question: Will they multitask? Um, that depends on your definition of multitasking! When we asked Joe Belfiore, the guy running Windows Phone, he alluded to live tiles and feeds as some ofthe ways that third-parties will be able to “bring value to the user, even when their apps aren’t running.” Which sounds to us like a big ol’ “shnope,” but we’ll see more next month at Microsoft’s developer event MIX.

And another post from WMPoweuser:

• Windows Phone 7 development docs leaked says that as expected UI will be developed using Silverlight and access to native API will be restricted.
• Lack of backward compatibility for Windows Phone 7 confirmed by Microsoft also confirms that developers will have to rewrite applications.

On Mobile World Congress that take place in Barcelona Microsoft presented new generation of Windows Mobile. Here are some of reviews that reveal WM 7:

• First Look: Windows Phone 7 Series Hands on Demo is a demo from Channel 9 which describes new UI most detailed from what I saw today.
• Windows Phone 7 Series hands-on and impressions (updated with video) is another good video to get in touch with new UI.
• Basic feature comparison between previous WM versions and 7 Series.
• And of cause official site.

Yesterday I was surfing the web looking for information regarding Windows Mobile 7. Although not much details are available by this time I created a brief summary of rumors, leaks and announcements.

Official Announce and Preview

Mobile World Congress in Feb 2010 at Barcelona.
MIX in Mar 2010 at Las Vegas.

Editions

Business edition (expected in Q4 2010) is designed to give OEMs more control over customization.
Media edition (expected in Q1 2011) will be targeting the main consumer of cell phone devices, this version will come loaded with full support for Silverlight, Xbox Live, Mediaroom, Zune Music and Social media sites interfaces.

First Expected Phones

From LG in Sept 2010.
From HTC in Oct 2010.

Updates in Features

As reported Windows Mobile 7 will be the first release in WM history that totally breaks backward compatibility, so existing legacy code will have to be rewritten. However this is not official information and I expect to have this clarified during official preview at conferences in Feb and Mar.

New features and functionality updates include:

1. New UI:
• Totally finger-friendly UI
• Multi-touch support
• Zoom support
• New menu system
• Based on Silverlight technology
2. Hardware updates:
• Accelerometer
• Only two screen resolutions (WXGA and 720p)
3. No suspend/resume power model. Device will always stay turned on.
4. Smart Card support removed.
5. Multiple folders and stores in Pocket Outlook Object Model (i.e. for contacts, calendar).
6. Pocket Outlook Object Model will handle mail and note items.
7. Task scheduling.
8. Over-the-air updates like on iPhone and Palm Pre (user can update PIM without cradling device).
9. Association Engine will allow to create custom voice commands.
10. SmartSearch technology for better search experience.
11. New photo API.
12. New Office, IE, Media Player.

References:
Windows Mobile 7
Microsoft Zune Phone: Loaded With Windows Mobile 7 Ready To Kill iPhone
Windows Mobile 7 early build hands-on review, not compatible with old apps
Windows Mobile 7 Mockup
Windows Mobile 7 Exclusive Screenshots and Analysis!
Everything you need to know about Windows Mobile 7
Microsoft confirms Silverlight for Windows Mobile 7
A secret/hidden Windows Mobile 7 leak!
Windows Mobile 7: What we expect and what we are hearing
Windows Mobile 7: Fifteen New Details

Below is a snapshot that shows how to change screen orientation from normal to 90 degree rotated or from 90 degree back to normal depending on current screen state:

if (SystemSettings.ScreenOrientation == ScreenOrientation.Angle0) {
	SystemSettings.ScreenOrientation = ScreenOrientation.Angle90;
}
else {
	SystemSettings.ScreenOrientation = ScreenOrientation.Angle0;
}

To make this code compile don’t forget to import Microsoft.WindowsCE.Forms namespace.

New home screen available in Windows Mobile 6.5 should be refreshed differently for Professional and Standard editions of OS. It can be done using the same API methods as for earlier versions of Windows Mobile.

For Professional edition it can be done like this:

[DllImport("coredll.dll")]
private static extern IntPtr PostMessage(int hWnd, int msg, uint wParam, uint lParam);

private const int HWND_BROADCAST = 0xFFFF;
private const int WM_WININICHANGE = 0x001A;

public static void Refresh() {
	PostMessage(HWND_BROADCAST, WM_WININICHANGE, 0xF2, 0);
}

For Standard edition the trick is to provide correct GUID to API. This GUID can be found in SlidingPanel.home.xml file located in “\Application Data\Home” folder. Here is the code:

[DllImport("aygshell.dll")]
public extern static uint SHOnPluginDataChange(ref Guid clsid);

public static void Refresh() {
	Guid guid = new Guid("{E9267CAB-02EE-4f37-8216-6BF6A8FF5A71}");
	SHOnPluginDataChange(ref guid);
}

Here is a code for loading embedded image named MyImage.png stored directly in project directory:

Assembly assembly = Assembly.GetExecutingAssembly();
string iconFileName = string.Format("{0}.MyImage.png", assembly.GetName().Name);
using (Stream io = assembly.GetManifestResourceStream(iconFileName)) {
	return new Bitmap(io);
}

Name of resource to load contains three elements divided by dots:

• Assembly name;
• Path where resource is stored inside of a project (must be omitted if resource is in project directory);
• File name of resource.

Path to resource should be created using names of folders. For example, if resource is in “Resources/Images” folder than path will be “Resources.Images”.

Normally saving XmlDocument leads to xml declaration at the beginning of file. In case it is desirable to omit it, XmlWriterSettings comes to help:

XmlDocument doc = new XmlDocument();
// Do with document whatever is needed...

// Save xml document without xml declaration.
XmlWriterSettings writerSettings = new XmlWriterSettings();
writerSettings.OmitXmlDeclaration = true;
using (XmlWriter writer = XmlWriter.Create(@"\omit.xml", writerSettings)) {
	doc.Save(writer);
}

Making read-only file writable with full .Net Framework is a piece of cake: there is FileInfo.IsReadOnly. Just set it to false and it’s done.

With Compact Framework we need to use FileInfo.Attributes and a solid knowledge of bitwise operations:

FileInfo info = new FileInfo(pathToReadonlyFile);
info.Attributes &= ~FileAttributes.ReadOnly;