I want to create an core data app with Xcode 9 that support iOS 9 as well. How to do that because default CoreData setup comes with method that are introduced in iOS 10.
You can remove default CoreData setup, then Maybe you must add setup method to create context,model, coordinator and so on.
Related
Starting a project in Xcode 10 doesn't present the checkbox found in previous versions of Xcode. How do I include CoreData in my project?
Nothing has changed in this regard. The Core Data option is present in exactly the same places as in previous versions of Xcode. You have to start your iOS app project with the Single View or Master-Detail app template.
If you're starting from a different app template, just copy the desired code from a project started with one of those templates.
I want start new app in Swift 3 Xcode 8 and support iOS 8.4/9.x
How to deal with Core Data ?
For anyone looking for it, I added the core data template generated by xcode 7 (swift 2) and its swift 3 conversion in this answer: https://stackoverflow.com/a/39814217/3034715
Yes, it is easily possible. Swift 3 is targeted to run on iOS v8+. You will only be able to use the subset of APIs supported on iOS v8.4 though. The best way to find out the answer to your question though is to create a test project that uses Core Data. You'll find that NSPersistentContainer creates an error. Why? It isn't available on the earlier OSes. Alternatively, create a test project with Xcode 7 and then migrate it to Swift 3, you'll see that it can easily work every where.
I am using VS2015 (RTM) and have a solution with two projects:
1) An MVC 6 ASP.NET Web Application
2) A Windows Split-View App (Universal Windows)
I would like to also add a class library to the solution that can be referenced by both of the projects, but can't find a way to do it.
If I add a Web Class Library (Package), I can reference it via the web application, but not by the Universal Windows App.
If I add a Windows Class Library (Universal Windows), I can reference it in the Universal Windows App, but when I try to add a reference to the MVC 6 Web Application I get a couple of thousand reference errors.
Is there an easy way to do this, i.e. share a class library between an MVC 6 app and a Universal Windows app, or is it a non-starter?
The MVC 6 can’t reference the UWP class library since they are based on the different .NET runtime. MVC 6 is based on the .NET Core or Full .NET, the UWP is based on the .NET for UWP.
I did not have the MVC 6 installed in my machine to test. The portable library should work in this case, but I also failed to compile in MVC 5.
As a workaround, you can considering using the code sharing between UWP project and MVC project.
Create a new folder named share_code in the solution folder, put the common code in this folder. In UWP project and MVC project, Add -> Existing Item, then you can re-use the code in both projects.
I have got an application developed with Monotouch 4.0.7. This app is running on iPads with iOS 4.3.
Now, I want to migrate to the latest Monotouch version is 5.0. Will I be able to deploy my app on iPads with iOS 4.3? Or Monotouch 5.0 only for iOS 5.0?
Yes, it is possible to develop for iOS 4.3 (or even earlier iOS versions) with MonoTouch 5.0.
To set the minimum iOS version your app needs, go to the project's options, and in the iPhone Application page set Deployment Target to the minimum version.
Have in mind that MonoTouch will not tell you if you use iOS 5.0 API in your app. You can add iOS 5.0 features to your app, but you must not try to use those features on a lower version (here you can see how to accomplish this).
You can upgrade to Monotouch 5.x without any problems. In Monodevelop, change your SDK to 5.x
Just make sure your deployment target remains 4.3, if you still want to target that platform.
You will have to pay attention to not calling any methods that don't exist in 4.3.
If you want to have different/extended behavior on iOS 5 devices, you can check the OS version and use a different code branch.
Another small thing to be prepared for: iOS5 behaves differently in some situations. For instance if you are having hierarchical UIViewControllers, iOS5 will automatically call all UI events like ViewWillAppear(), even if you don't use the new UIViewControllery hierachy API.
What I want to say: test your app thoroughly on both iOS versions.
To continue in my post-XCode 4 upgrade confusion, i came across this....
My Build Settings has Base SDK as iOS 4.3.
Now back in XCode 3.x days I remember 2 things:
The Base SDK was always set to iOS 4.0.
The target device was set to iphone 3.0 (to ensure greatest iphone audience).
What consequence is there for this Base SDK?
I mean, if SDK 4.0 provides support for features that only iOS4/iPhone4) provides, then why are these two separate build settings?
You can choose iOS 4.0 as your base SDK, but as long as you do not use APi's that are 4.0 and up your code should run on 3.x unless you used apis that were only in 3.2 and so on =)
Always a good thing to check the availability of methods when you look in the class reference.
I recommend using 4.x stuff.. because the people that use 3.0 are not worth supporting ( Only the really old devices are still running that, iPhone 1 -- most users have upgraded by now to an iPhone 3Gs or 4 ), the features you get in 4.x, including GCD are awesome.