It can be painful generating icons of different sizes for your application, if you do not know how to script and automate the image processing on Photoshop/Gimp. But there are time saver alternatives that can simplify the process.

I always start with 1024 X 1024 image and use these utility apps to generate icons in a matter of seconds.

You can use Jabber URIs in your iOS apps, for example, tapping a contact’s picture might start a Jabber call. Once you have constructed the appropriate Jabber URI, simply use openURL to initiate its actions.

I have Xcode 4.5.2 loaded with developer certificates and provisioning profiles from both my individual developer account and enterprise team account.

With this setup, when I tried to run my application on the iOS device I came across the error message “A valid provisioning profile for this executable was not found”.

On my application build settings, code signing identity was set to Automatic Profile Selector, which was defaulting to my enterprise account, where I have not created provisioning profiles for my personal applications.

To overcome this error, you can go to Project -> Build Settings -> Code Signing Identity and set specific provisioning profile you want to use during run, instead of choosing automatic profile selector.

WebSocket provides the bi-directional communication, which allows data to be sent back and forth at the same time, without requiring to request from server or client. So once the WebSocket connection is established, data can be pushed across without either side having to ask for it.

Following is the best references to get started with understanding all about websockets and its benefits.

There are many WebSocket libraries available to support the development of WebSocket server in C# .net, but the most efficient, and one of the easiest to use is the Alchemy Websockets (http://alchemywebsockets.net/)

The current version (2.2.1.238) supports the latest Google chrome, Mozilla Firefox, Safari on mac/windows and mobile devices (iPhone/iPad).

Note: If websocket server and webserver are running on the different machines, make sure to change the websocket server address (‘ws://localhost:8100’) with correct IP address or hostname.

Now lets see how it works. Open up browser and navigate to the URL where you have published “client.html”.
Its working fine for me on Google Chrome (19.0.1084.56 m), Mozilla Firefox (13.0), Safari (5.1.7 – 7534.57.2), Safari on iPhone/iPad (iOS 5.1.1-9B206)

Console Messages

Isn’t that so simple to implement websocket with your favorite language C# .NET.
Thanks to OLIVINE LABS (http://olivinelabs.com/) for making this library available under MIT and LGPL licenses.