StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I came from a C# background as well and have been working with the iPhone SDK since beta 2. I totally agree with cranley about VS being a bit clunky compared to Xcode. Xcode is WAY different, and totally foreign when you start using it. So was VS though back in the day. Once you get by the learning curve it is a wonderful experience. The apps I am developing use C# server side (web service) and I absolutely hate having to switch to VS to write the web service code from Xcode. Obj-C is also quite fun to use once you learn how it works best: delegates (very different than .NET delegates), messages, Categories and all the other oddities present.</p> <p>I did some Java and Flex programming previous to .NET and I always hated the .NET docs compared to Java docs. They just don't cut it. I have personally found Xcodes docs and search system to be nothing short of amazing. There are countless PDF guides linked from the docs that have tons of sample code. Think about this: the iPhone SDK has been out of beta for about 2 months now. The docs show a maturity level of many years. And yes, it is because Obj-C has been around over a year and the frameworks are similar.</p> <p>Overall, the biggest issue I have found is that there are a LOT of .NET developers jumping on the iPhone bandwagon and trying to use Obj-C as if it were C# or VB. They fail to read the basic Obj-C docs let alone the iPhone docs and then they get very frustrated and eventually fail. The discussion forums are full of this scenario. iPhone programming is not easy. Learning a new language is not easy. It takes time and a lot of try.fail.try. It's not .NET so lose that mindset before you even begin and things will be wonderful.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload