Feeds

.NET for iPad stretches to Google's Android

Jobs the merciful god?

Providing a secure and efficient Helpdesk

Call it an unholy three-way, but .NET is coming to Google Android, potentially helping C# developers interested in creating applications for Apple's iPad.

Novel has announced that MonoDroid, a software development kit (SDK) to build applications for Google's Linux OS using C# and the Common Intermediate Language (CIL), is ready for beta testing. MonoDroid is based on Novell's Mono Project, and final code for MonoDroid is due this summer.

Ahead of that, Novell - which is searching for a new owner - has posted a sign-up survey of developers interested in trying the beta. You can sign up here.

The Mono Project has been building an open-source implementation of Microsoft's C# and .NET for Linux and Unix through out the 2000s, with Microsoft's blessing.

Novell created MonoTouch in September 2009, putting Mono on Apple's iPhone and iPad. Since then, though, it's become unclear whether MonoTouch is actually allowed on the Jobsian machine under the recently updated terms of Apple's developer program agreement for the iPhone OS 4 that the iPad will run.

Novell has tired to minimize reports MonoTouch could be banned, but judging by the team-Mono blog the company is as much in the dark as everybody else over what the iPhone OS 4 license means to their code.

The company has admitted in blog posts that it has had little direct feedback from Apple on the matter. Instead, it optimistically points to App Store approval for the Mono-based applications Touch Playbook, Really Simple, and LCARS Reader as proof that Mono complies with Jobs' new rules for doing business. Novell was unable to comment or update The Reg by press time.

MonoDroid potentially lets developers build applications using C# that talk to Android's native Java APIs and lets those APIs execute inside the Common Language Infrastructure (CLI) runtime engine that - like C# - is an ECMA standard.

If Mono is allowed on the iPad, having it on Android as well will mean that developers can save time and effort porting their apps between devices.

It should mean coders can reuse their existing .NET skills and ECMA-compliant CLI runtime engines, plus existing business logic on the Apple and Google platforms. That'll leave developers free to focus on the interesting work of making changes to the interface needed for the different devices. ®

Secure remote control for conventional and virtual desktops

More from The Register

next story
Not appy with your Chromebook? Well now it can run Android apps
Google offers beta of tricky OS-inside-OS tech
New 'Cosmos' browser surfs the net by TXT alone
No data plan? No WiFi? No worries ... except sluggish download speed
Greater dev access to iOS 8 will put us AT RISK from HACKERS
Knocking holes in Apple's walled garden could backfire, says securo-chap
NHS grows a NoSQL backbone and rips out its Oracle Spine
Open source? In the government? Ha ha! What, wait ...?
Google extends app refund window to two hours
You now have 120 minutes to finish that game instead of 15
Intel: Hey, enterprises, drop everything and DO HADOOP
Big Data analytics projected to run on more servers than any other app
prev story

Whitepapers

Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.
Saudi Petroleum chooses Tegile storage solution
A storage solution that addresses company growth and performance for business-critical applications of caseware archive and search along with other key operational systems.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.