What is xamarin, how it useful in C# coders?

C# is the best language for mobile app development. With Xamarin, you write your apps entirely in C#, sharing the same code on iOS, Android, Windows, Mac and more. Anything you can do in Objective-C, Swift or Java, you can do in C#. Native UI, native API access & native performance. Xamarin apps are built with standard, native user interface controls. Apps not only look the way the end user expects, they behave that way too. This can’t be achieved with other solutions. read less

Xamarin.iOS allows us to create native iOS applications using the same UI controls we would in Objective-C and Xcode, except with the flexibility and elegance of a modern language (C#), the power of the .NET Base Class Library (BCL), and two first-class IDEs - Xamarin Studio and Visual Studio - at our fingertips read less

The major differences are : 1):Rendering Layouts – While ASP.NET Web Forms use Page controller pattern approach to render the layouts, ASP.NET MVC uses Front controller approach. In ASP.NET Web Forms, every page has its own controller. On the other hand, in ASP.NET MVC, there is a common controller for all the pages. 2)In terms of separation – There are separation concerns in ASP.Net Web Forms as each page has its own controller. However, in ASP.NET MVC, there is a clean separation as view and controller are totally separate. 3)Testing – Automated testing is tedious and difficult in ASP.NET Web Forms. ASP.NET MVC wins the battle here as test driven development is quite simple in this approach. 4)Development model – ASP.Net Web Forms follow a conventional even-driven development model, whereas ASP.Net MVC follows MVC pattern-based development model. 5)State management – While ASP.NET Web Forms have state management techniques like view state or sessions, ASP.NET MVC doesn’t have any such state management techniques. 6)If you go for Asp.NET Web forms, there is no need to have a detailed understanding of HTML, CSS or JavaScript as it abstracts all these details and provides automatic plumbing. However, if you’re using ASP.NET MVC, you will need a clear understanding of how HTML, CSS and JavaScript work. 7)Page life cycle is followed by the ASP.Net Web Form model, but there is nothing like page life cycle in ASP.Net MVC. Request cycle is quite simple in ASP.Net MVC. 8)With tons of control libraries and limited knowledge of other relevant technologies, ASP.NET Web Form is called a rapid application development approach. However, there is nothing like RAD in ASP.Net MVC. It reduces the productivity of the developers. 9)If you’re developing a small application with limited team members, ASP.NET Web Form is a best approach. ASP.NET MVC is more suitable for the large-scale applications. 10)Web Forms help you reduce the time to develop intranet and internet applications that requires a lot of controls. However, there is a lot of time required later on to code around the limitations. On the other hand, in ASP.Net MVC, the main goal is gaining control over the application. You don’t have to spend more time to code around the limitations. 11)ASP.Net Web Form is quite simple to learn and works best for the developers having issues with the HTTP/HTML model. ASP.NET MVC requires a learning curve to understand how it works. 12)In ASP.NET Web Forms, the amount of code require is very less as lots of components are integrated. On the other hand, in ASP.Net MVC, a lot of coding is required as application tasks are divided into different components. 13)You can use Visual Studio and Visual Web developer for creating ASP.NET Web Forms. The same tools can be used for the ASP.NET MVC. 14)While ASP.Net MVC is an open source, ASP.Net Web Form is not an open source. 15)ASP.NET Web Forms include user controls in order to enable code re-usability. On the other hand, ASP.Net MVC uses Partial views to enable code re-usability. read less