Net60 Technology and Roadmap

What .NET Compact Framework version is Net60 binary compatible with?

Net60 is binary compatible with Microsoft’s .NET Compact Framework 2.0 implementation. Net60 supports Smart Device projects created in Visual Studio for Windows Mobile 5.0 Smartphone or for Windows Mobile 6 Standard.

Why does Net60 not support Smart Device projects for Pocket PC?

The Pocket PC version of a .NET Smart Device project depends on touch UI input.  At present S60 3rd edition devices do not support a touch UI and therefore Net60, in order to run on S60, only supports the Smartphone or Standard Smart Device projects. Pocket PC type controls will be supported when Net60 supports S60 5th edition devices.

Will Net60 support the touch UI of S60 5th edition?

Yes, Net60 will in future fully support the touch user interface of phones like the Nokia 5800 and N97.

What is a Smart Device project?

A Smart Device project is a project type/ template selected in Visual Studio when creating a .NET application for Windows Mobile. Smart Device projects can either target the Smartphone or the Pocket PC flavor of Windows Mobile device form factors.

Will Net60 support Microsoft’s .NET Compact Framework 3.5?

Yes, Net60 will be binary compatible with CF 3.5 supporting all the new namespaces and user controls.

What is Genesis as provided by Red Five Labs?

Genesis is a Visual Studio plug-in provided as part of the Net60 SDK (Net60.exe) installed to a user's PC.  Genesis creates a Symbian installer package (.SIS file) from the .NET application written in Visual Studio.

Net60 Licensing

How is Net60 licensed?

Net60 is licensed in two parts. Firstly, there is a license to access the Net60 SDK, provided on either a per developer seat basis (Net60 Pro), or on a per site basis (Net60 Premium). Secondly, there is a per device fee for each smartphone onto which Net60 is deployed. This device fee is called a runtime license, and is available by buying bundles online from our website. There is no “phone home” or automated activation required when deploying S60 applications built with Net60.

How is the Net60 runtime license activated on device?

When Net60 is purchased you will be provided with a Net60.licence file which must be included as a dependency in the Genesis project when creating your distributable S60 .SIS file. It is obligatory to license both the SDK and all runtimes deployed to device.

Net60 Pro and Premium customers will receive a volume license which isn’t IMEI or device-specific, allowing them to make one SIS file available for installation on any S60 device.

Deploying .NET apps to S60

Why must I convert my .exe into a .SIS?

Much like creating a Cab file for Windows Mobile to install native applications to device, Symbian uses the concept of SIS files. The .NET executable is wrapped up into a .SIS file using the Genesis Visual Studio plug-in included in the Net60 SDK. Once in SIS format, a .NET S60 app is easily installed on an S60 device, via PC or OTA.

What is a SIS?

A SIS or Symbian Installation Source file, is a native Symbian installation package that is used when installing S60 applications to device.

Once I have created my SIS, why must I Symbian Sign it?

Only applications that are Symbian Signed are allowed to be installed onto Symbian devices. “Symbian Signed is a program run by Symbian for and on behalf of the wireless community to digitally sign applications which meet certain industry agreed criteria. The 'for Symbian OS' logo is awarded to applications that are Symbian Signed. Symbian Signed promotes best practice in the design of applications and content to run on Symbian OS-based phones. Symbian Signed is endorsed and supported by network operators, handset manufacturers and developers.” - Point 1 of the Symbian Signed End User Statement describing Symbian Signed.

Will .NET applications created with Net60 need to be Symbian Signed?

Signing .NET applications ensures commercial .NET applications don’t subvert the Symbian OS security infrastructure. There is more information about the Symbian signing process at www.symbiansigned.com. Developers may find the Net60 Launcher useful during the testing and development phase. It allows developers to run their .NET executables on an S60 device directly thereby bypassing the sis file creation and Symbian Signing process.

How do I Symbian Sign a SIS file?

.NET applications that are shipped commercially must either be Certified or Express Signed by Symbian Signed. While applications are still in development, one can either Open Sign or Self Sign them. We recommend watching our online web demo that walks the viewer through the self signing process using Genesis.

How do I install Net60?

There are two binary versions of Net60 available. For development purposes, the debug version of Net60 is installed to device by installing the Net60_debug.sisx which is usually located in the default Net60 install path on your PC (C:\Program Files\Red Five Labs\Net60). The debug version installs the Net60 Launcher to the apps menu. Using the launcher you’re able to run .exes from any folder.  If you’d like to install the release version, you can install the Net60.sisx found in the same folder.  Normally, the release version is only referenced as a dependency when creating a deployable SIS file with Genesis.

Will I be able to embed the Net60 installer into my SIS? i.e. will I be able to distribute my  S60 application as a single, independent .SIS installer?

Yes, the S60 application that you create (YourApp.sisx) will have the Net60.sisx embedded within it, and can be independently distributed. If the .NET Compact Framework is not already installed on the S60 device when your application is installed, it will be installed during the same install process without requiring any end user intervention.

Technical Differences between .NET on WM and .NET on S60

The soft key menu options are reversed left to right on S60 compared to Windows Mobile.

In Microsoft Smart Device applications, the 'Options' menu is always found on the right hand side. In Symbian S60 applications, the 'Menu' is always found on the left hand side. Red Five Labs automatically reverses the order of the menu’s to honour the S60 design paradigm. The Windows Mobile Smart Device Menu rules (which are also applicable to the Red Five Labs implementation) are addressed in the .NET Compact Framework FAQ on MSDN. The FAQ is also a very good general reference for .NET CF development.

.NET on S60 does not support the creation of Pocket PC Smart Device Projects.

The main form factor difference between Smartphone and PocketPC devices is in the fact that Pocket PC devices have (often larger) touch screens. Thus the main differences are in the unavailable UI controls to Smartphones and the absence of touch UI input.

SQLite supported instead of MS SQL Server CE

Microsoft SQL Server CE is a Windows Mobile native application and is not available on S60 hence it is not supported by Net60. SQLite, which is S60’s built in database, is currently supported in Net60 as a full ADO.NET layer to SQLite is provided.

Net60 does not support running in the Symbian device emulators

Our JIT compiler can only generate instructions for ARM processors (those on device). The Symbian emulators run on PC processors (typically x86) so our JIT cannot target them. If you are unable to test on device, try using Forum Nokia’s Remote Device Access(RDA) services. RDA allows you to access a live device over the Internet. You are able to install and run applications as on a normal device, except it is done via a simulated front end on your pc that connects via the Internet to the live device.