How To Add Existing Monotouch Project To Visual Studio 2017 For Mac

Posted on

I'm creating a hotel management service in C# on Visual Studio (Mac) and I can't seem to find a good explanation on how to add a local database file to my project. I created my database table in open office (.odb file) but there doesn't seem to be a way for me to implement this in my project.

Developers working with Xamarin MonoTouch have been stuck with developing on a Macintosh and working with MonoDevelop. This hasn't been a bad thing. The Apple iOS SDK only runs on the Mac, so this requirement hasn't been a major limiting factor in iOS development. Unfortunately,.NET and C# developers are used to using Visual Studio. Microsoft has spent a lot of time, effort and money to make Visual Studio the premier software development tool in existence. Has heard from those developers who want to integrate Visual Studio with iOS development.

This plug-in allows developers using Visual Studio to write iPhone and iPad applications for the iPhone using the Microsoft.NET Framework and C#. Configuration and Setup When I first discussed this product with some developers, their feedback was: 'Great! Now we don't need Macs for iPhone development!'

Unfortunately, that's not quite how the product works. Here are the basics: • Write code in Visual Studio. • When compiling code, contact a Mac build server for compilation. The build server handles the interaction with the Apple iOS SDK. • The Mac build server sends the program to the iOS simulator or device. • The Mac build server works as an intermediary between Visual Studio and the iOS simulator or device.

Xamarin has produced an for Xamarin.iOS. Figure 1 shows the communication at a high level.

[Click on image for larger view.] Figure 1. The Xamarin.iOS workflow.

Visual

I have a shared xamarin forms iphone project (not using the others right now) and am on the latest VS 2017. Everytime I add a new content page only one of the two files for the content page makes it into the project and I have to hand edit the projectitems file and correct the markup in there to associate the xaml.cs and xaml files correctly, then restart the project. That's an annoying workaround, but. Then InitializeComponent fails to be found during compile, but the project still builds and runs (most of the time), but. If I add content to the xmal file and assign it an x:Name, that object can't be accessed in the xml.cs file. It's not found, so I've found two sometimes workarounds for this.

Pro

1) Reload the project and sometimes that works. 2)Remove the object, do a debug and break point on InitializeComponents, step into it so the gs file is opened and then step out, then stop the debug, add my object back into the xaml and then I can reference it for the xaml.cs file. Quickbooks for mac 2015 free trial. One of those works for a while. A couple of hours, then even when not touching either of the new files but doing other work that isn't connected to those files, all of a sudden the object reference and InitializeComponents can't be found, then I have to restart the projects.