Book Image

Learning C# by Developing Games with Unity 2019. - Fourth Edition

By : Harrison Ferrone
Book Image

Learning C# by Developing Games with Unity 2019. - Fourth Edition

By: Harrison Ferrone

Overview of this book

Learning to program in today’s technical landscape can be a daunting task, especially when faced with the sheer number of languages you have to choose from. Luckily, Learning C# with Unity 2019 removes the guesswork and starts you off on the path to becoming a confident, and competent, programmer using game development with Unity. You’ll start off small by learning the building blocks of programming, from variables, methods, and conditional statements to classes and object-oriented systems. After you have the basics under your belt you’ll explore the Unity interface, creating C# scripts, and translating your newfound knowledge into simple game mechanics. Throughout this journey, you’ll get hands-on experience with programming best practices and macro-level topics such as manager classes and flexible application architecture. By the end of the book, you’ll be familiar with intermediate C# topics like generics, delegates, and events, setting you up to take on projects of your own.
Table of Contents (20 chapters)
Free Chapter
Section 1: Programming Foundations and C#
Section 2: Scripting Game Mechanics in Unity
Section 3: Leveling Up Your C# Code

Writing proper C#

Lines of code function like sentences, meaning they need to have some sort of separating, or ending, character. In C#, all lines of code, which are called statements, end with a semicolon to separate them for the code editor to process.

Unlike the written word in normal circumstances, a C# statement doesn't technically have to be on a single line; whitespace and new lines are ignored by the code editor. For example, a simple variable could be written in different ways. It could be written like this:

          public int firstName = "Bilbo";

Alternatively, it could also be written as follows:


These two code snippets are perfectly acceptable to Visual Studio, but the second option is highly discouraged as it makes code extremely hard to read. The idea is to write your programs as efficiently and clearly as possible...