monocross / monocross Goto Github PK

A cross-platform mobile framework using C# .NET and Mono to create shared-code apps on iOS, Android, Windows and Webkit.

Home Page: monocross.net

License: MIT License

C# 86.94% ASP 0.26% HTML 0.18% JavaScript 7.72% CSS 4.82% Batchfile 0.09%

monocross's Introduction

Latest News: v2.0 has been released and is now available for public consumption.

What is Monocross

Monocross is a C# .NET cross-platform mobile framework maintained and developed by a community of users and developers. Released under the MIT license, anyone is free to download, contribute and share the framework. With Monocross you can build native apps that use any platform-specific APIs or HTML5 to provide rich web-based functionality, all while using the same business logic and data code, whether running on the device or the server. With Monocross you have the flexibility to write apps for multiple device platforms and architectures with a custom user interface for each platform.

Multi-Platform Support

Output native code for iPhone/iPad/iPad mini/iPod, Android, Windows Mobile, Windows Phone 7 & 8, Windows Surface and Windows XP/Vista/7/8. MonoCross also outputs web/hybrid app support for Android, BlackBerry, Symbian, and Web OS via HTML 5.0, CSS, and JavaScript. It even provides support for basic HTML/WAP for those still living with feature phones.

Single Codebase

At the foundation of the Monocross mobile framework is an abstract mobile application model where all app specific business logic is developed. The output for each mobile device platform is then generated from that single codebase, independent of whether the business logic is executed natively on the device or remotely on the server. As a result, supporting application changes and enhancements are significantly reduced.

Development Consistency

Unlike other development efforts targeting fully native platform-specific code that require Objective-C/Cocoa developers for iPhone & iPad, Java developers for Android, a different flavor of Java developers for Blackberry, C# .NET developers for Windows Phone, Modern, and Classic, the development and on-going support of Monocross applications only require C# .NET capabilities.

Get Involved

First, 'Git' registered. Then fork the main repo found at https://github.com/Monocross/Monocross This will allow you to make changes to your own repo and send us patches and enhancements, that benefit everyone.

Participate in the forums found on the Monocross.net website, where you can find the answers to the most frequently asked questions, find monocross related jobs, and discuss your code. Once you create an application using Monocross please let [email protected] know so we can add you to the applications page on Monocross.

History

[ITR mobility](http://itr-mobility.com) started the Monocross project as a mobile framework for their clients in 2010, the year of the iPad. Through conversations at conferences and code camps with other developers, more people became interested in using the C# .NET language that Monocross is built upon, as their mobile framework of choice, so the project was open sourced.

For more information on using the pattern, Visit the WIKI

monocross's People

Contributors

Stargazers

Watchers

monocross's Issues

http://monocross.net/overview has broken image references

The web page at http://monocross.net/overview has a bunch of broken image references with URLs of the form http://itr-mobility.com/wp-content/uploads/[...] which are all invalid.

Is the source for the website itself also hosted on GitHub? I couldn't find it in the list of public repos of the https://github.com/monocross user account.

MonoCross.Droid refernce issue in "MonoCross Android Container" VS2010 template

Oh man, I think the problem was that in my MonoCrossFragments.Droid project I left the MonoCross.Navigation.dll file in the MonoCross subdirectory along with the MonoCross.Navigation.MD.dll. It was left over from how I created the MonoCrossFragments.Droid project from the base MonoCrossFragments project. Ugh. Well, I know there is still a problem with the MonoCross project template references, because I ran into this issue a while back, and as of now I'm using all the MonoCross assemblies right from where I unzipped the 1.0.2 source, and not the ones included with the templates.

Hello.

Before I begin, here are some specs:

Windows 7 Enterprise x64
Visual Studio 2010 Ult SP1
Android-SDK (1.6-4.1)
Mono for Android 4.2.6
MonoCross 1.0.2
MonoCross Utilities 1.0.2
MonoCross Templates

I just got done manually creating a multi-platform solution/project in visual studio from scratch following the layout from the CustomerManagement example:

 MonoCrossFragments.Droid (VS2010 Solution)

      Container (folder)
           MonoCrossFragments.Droid (MX Android Container Project)

      Data (folder)
           MonoCrossFragments.Data.MD (Mono/Android Class Lib Project)

      MonoCrossFragments.MD (MX Android App Project)

      MonoCrossFragments.Shared.MD (Mono/Android Class Lib Project)

After compiling the near empty solution, I got the error message:

"Error 1 The type 'Android.App.ListActivity' is defined in an assembly that is not referenced. You must add a reference to assembly 'Mono.Android, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'. C:\My Projects\TestArea\MonoCross\MonoCrossFragmentsRoot\MonoCrossFragments\MonoCrossFragments.Droid\Views\MessageView.cs 16 18 MonoCrossFragments.Droid"

The MonoCross Android Container project this was happening in, MonoCrossFragments.Droid, did in fact have a reference to the Mono.Android assembly residing in my "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v2.2" directory, which was automatically added by the template.

So, I tried to clean the solution and rebuild, then tried removing and adding back the Mono.Android reference, and then tried selecting a newer version of the Android platform (4.0) (and yes, I reopend my solution after changing). None of which worked.

Assuming that the MonoCross.Droid.dll assembly may be a fault for not properly referencing Mono.Android.dll, I copied a MonoCross.Droid.dll file from another, working project. This fixed the Mono.Droid reference error, but then gave:

Error 1 Exception while loading assemblies: System.IO.FileNotFoundException: Could not load assembly 'Android.Dialog, Version=1.0.0.0, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?
File name: 'Android.Dialog.dll'
at Monodroid.Tuner.MonoDroidResolver.Resolve(AssemblyNameReference reference, ReaderParameters parameters)
at Xamarin.Android.Tasks.ResolveAssemblies.AddAssemblyReferences(List1 assemblies, AssemblyDefinition assembly) at Xamarin.Android.Tasks.ResolveAssemblies.AddAssemblyReferences(List1 assemblies, AssemblyDefinition assembly)
at Xamarin.Android.Tasks.ResolveAssemblies.Execute() MonoCrossFragments.Droid

and so I copied a Android.Dialog.dll assembly into the directory where MonoCross.Droid.dll resided (which was the directory named "MonoCross" in the root of my project folder, or MonoCrossFragments.Droid\MonoCross). Then it compiled.

So, it seems like there is something going on with the reference to Mono.Android from within the MonoCross.Droid assembly that is included with the MonoCross Android Container project template.

Has anyone else reported issues with this Mono.Droid reference ?

Thanks, Dan.