Monodroid For Visual Studio 2012

As of March 31, 2016, all of Xamarin is included with all editions of Visual Studio at no extra cost and does not need a separate license. Xamarin Studio Community for Mac is also free for students, OSS developers, and small teams. Note that for existing installations of Visual Studio that are configured with earlier. Visual Studio 2012; ALM. MonoDroid Tutorial Part 1: Introduction to MonoDroid. MonoDroid is a plug-in to Visual Studio 2010 that allows.NET developers to. September 12th is the big launch day for Visual Studio 2012 and we’re happy to announce that Xamarin is one of Microsoft’s sim-ship partners.

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. Evolution By Bergstrom And Dugatkin Pdf here. 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 MvvmCross_All 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. Download Tokyo City Nights Java Games. 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 HACK_DO_NOT_FORWARD_ICOMMAND in - background to this is in Using PCLs PCL v2 support is included with VS2012. This includes support for WindowsStore, WP, XBox, etc.

To add MonoDroid, and VSMonoTouch PCL support, you need to add some files (based on • 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.