Monodroid For Visual Studio 2012
Android App Development with MonoDroid using.NET framework in Visual Studio. I will discuss how to configure MonoDroid in Visual Studio 2010. 2012 at 11:46 AM. Use Visual Studio for Mac or Visual Studio to build new Watch Apps. Build native iOS and Android apps in Visual Studio. Visual Studio for Mac. Download Now.
. Ship native app bundles on the App Store.
Our Ahead-of-Time (AOT) compiler compiles Xamarin.iOS apps directly to native ARM assembly code, meaning your app is a native platform binary. Access any iOS API. We bring 100% of Apple’s iOS SDK to C#, enhancing Objective-C APIs with stronger types and.NET naming conventions so you feel right at home. Call existing Objective-C code from C#. Use your existing Objective-C code, frameworks, and custom controls in your Xamarin app using our automatic binding generator. Build WatchKit apps. Use Visual Studio for Mac or Visual Studio to build new Watch Apps, edit Watch user interfaces in the iOS Designer, and debug Watch apps in the iOS Simulator.
Stay up-to-date with Apple. We released same-day support for iOS 5, iOS 6, iOS 7, and iOS 8 so your apps can take advantage of the latest iOS features as soon as possible. Ship native Android packages. Xamarin.Android uses just-in-time compilation for sophisticated runtime optimization of your app’s performance, meaning your app is a native Android APK. Access any Android API, including new form factors.
We bring 100% of Google’s Android APIs to C#, enhancing Java APIs with async support and.NET naming conventions so you feel right at home. Call existing Java code from C#.
Use your existing Java code, frameworks, and custom controls in your Xamarin app using our automatic binding generator. Build Android Wear apps. With access to 100% API support for Android Wear, create full-featured applications capable of running on Android Wear devices. Stay up-to-date with Android. Xamarin stays up-to-date with the most current APIs from Google, so you can always use the latest features in your apps.
I've been asked on Twitter about the latest state of PCLs, VS2012, VSMonoTouch, etc. There's no way I could do that in 140 characters. So here's a longer answer. Before you start. The Productivity tools for VS2012 are essential - install them - tools like 'right-click to edit the csproj file' are incredibly useful! Loading MonoTouch, MonoDroid, WP, WindowsStore, WPF, MonoMac projects in Visual Studio 2012 By Visual Studio 2012, I mean Professional Edition or better - give up on Express as there is no addin support in the free version.
WindowsStore and WPF projects are all supported out of the box by Visual Studio 2012 WP7.1, WP8 can be supported by adding on the WP SDK - MonoDroid projects can be supported by buying (or evaluating) the Mono for Android - For the best MonoDroid experience, you probably want to get the x86 Android emulator working - see instructions at Unfortunately I've had a lot of problems getting this running on the same machine as Windows 8/Windows Phone 8/Hyper-V. I hope you have better luck than I do - as a good emulator is a wonderful tool to have.
MonoTouch projects require a little tinkering to make them load - they require VSMonoTouch2012 - a completely unsupported installer for this is available on my SkyDrive account -some hint at where it came from are on - obviously you install this at your own risk. To complete the install of VSMonoTouch you also need to follow the steps in the readme of:. 'Copy the MonoTouch binaries from your Mac development environment.' . 'Add a RedistList-folder.' Warning: See section belo w on some known issues in VSMonoTouch in VS2012. For MonoMac/ Xamarin.Mac I'm not aware of any way to load these in VS2012 at present.
For older targets like Silverlight and WindowsForms I've not tried anything yet. Some known issues for VSMonoTouch 2012 I have found VSMonoTouch2012 to be.very. slow when VS first loads a new solution/project - eg. It took.hours. to load MvvmCrossAll the first time. After this, however, it seems to work quite well.
The way MonoTouch references mscorlib is slightly different to the Microsoft way, so you may find you need to explicitly reference the MonoTouch mscorlib - see There are some arguments that VSMonoTouch and MonoDevelop/MonoTouch have over project files. These especially seem to concern the TargetFramework - the fact that VSMonoTouch is set to 1.0 does confuse things (I think). I have seen some projects where I have had to hack in a build step for 'The type or namespace name 'TargetFrameworkAttribute' does not exist' - see One very bizarre problem I've had is with one of my System.Windows surrogate DLLs - for some reason this refuses to pick up my MonoTouch references at compile time (it is OK in intellisense). This has only occurred in one place so far - see the HACKDONOTFORWARDICOMMAND in - background to this is in Using PCLs PCL v2 support is included with VS2012. This includes support for WindowsStore, WP, XBox, etc.
Microsoft Visual Studio 2012 Download
To add MonoDroid, and VSMonoTouch PCL support, you need to add some files (based on. Page borders for microsoft word free. Install a file called 'MonoAndroid,Version=v1.6+.xml' in 'C: Program Files (x86) Reference Assemblies Microsoft Framework.NETPortable v4.0 Profile Profile104 SupportedFrameworks' with content:. Install a similar file called 'VSMonoTouch,Version=v1.0+.xml' in the same directory and for its content use. Note: the VSMonoTouch file is slightly hackier than the MonoDroid one - it points the portable tools at Full.Net v1.0 exactly as the VSMonoTouch plugin does - but I think this can cause some tool confusion sometimes.
After creating these xml files, then you should be able to use PCL projects of profile 104 across all platforms. There are however some small additional problems you may need to solve at build time:. If you share solutions back to the Mac, then MonoDevelop currently only likes Profile1 at Build time. To work around this, you may find you need to force Profile104 across to Profile1 using a conditional statement in your csproj file. Jon Pepper found this solution - thanks - Note that this problem is marked as solved in bugzilla - see - so this fix might be available in an alpha, beta or full release soon. If you share solutions back to the Mac,and if you have an older MonoDevelop installation, then you may also find that it fails to open.sln files. This bug has been around since May, but is almost fully fixed now.
To workaround it you can manually change the.sln to say 11 rather than 12 - see. To make use of some of the namespaces included in PCL you may need to setup shim assemblies to redirect DLL references. When I was building the Wpf libraries, I had the problem that I didn't have System.Windows.Interactivity on my machine. When I installed the Blend SDK for Silverlight 4 which is supposed to the DLL, it didn't complain about the code but gave me an error along the lines of 'You must add a reference to assembly 'System.Windows, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes'.' In the end I followed another StackOverflow post and used the 4.5 DLL that was included in this download: Possibly downloading a different version of the Blend SDK could have worked as well.
I can comment on iFactr development. The premise of iFactr is cross-platform UI.
In other words, your 'views' contain all kinds of generic controls, menus, lists, etc. None of these are platform-specific UI elements, they're just abstract, represented using iFactr's API. These generic views (known as 'layers' in iFactr lexicon) are navigated to via NavigationMappings (analogous to routes in ASP.NET MVC or Rails) and rendered by proprietary platform-specific factories that spit out views using the APIs of target platform. So, for example, there's a Touch factory, and an Android factory, and a Windows Phone factory, and a WPF factory, and a Compact Framework factory, etc, etc, etc.
These platform-specific factories are part of iFactr's proprietary assemblies. So, iFactr gets you a long ways towards cross-platform UI. This of course presents certain constraints, however, in that the rendered UIs will closely resemble the UI guidelines of the target platform. In other words, UI customization is limited. IFactr also offers a cross-platform data stack for handling caching and queueing against RESTful endpoints. Beyond UI and data access, iFactr itself doesn't offer much to help the portability of the core abstract application; that's left to the developer.
However, this is exactly why MonoCross emerged: to provide a framework for cross-platforming the core application. And from MonoCross, MvvmCross was born. So, in a way, MvvmCross is the grandchild of iFactr.although by way of some twists and turns. To be fair, I once worked on iFactr and developed apps with it.
I am no longer using it, but it is still being actively developed and marketed.