CSharp for Unity Day 3

C# FOR UNITY -
ADVANCED TECHNIQUE
PRESENTER: DUONG HOANG THANH

CONTENTS
• Property
• Indexer
• Regular Expression
• Reflection
• Attribute
• Garbage Collector

WHAT IS PROPERTY ?
• A property is a member that provides a flexible mechanism to read, write, or
compute the value of a private field.
• Properties can be used as if they are public data members, but they are
actually special methods called accessors.
• This enables data to be accessed easily and still helps promote the safety and
flexibility of methods.

PROPERTY EXAMPLE
class TimePeriod {
private double seconds;
public double Hours {
get { return seconds / 3600; }
set { seconds = value * 3600; }
}
}
…
TimePeriod t = new TimePeriod();
t.Hours = 24;
print("Time in hours: " + t.Hours);

PROPERTIES OVERVIEW
• Properties enable a class to expose a public way of getting and setting values, while
hiding implementation or verification code.
• A get property accessor is used to return the property value, and a set accessor is
used to assign a new value. These accessors can have different access levels.
• The value keyword is used to define the value being assigned by the set accessor.
• Properties that do not implement a set accessor are read only.
• For simple properties that require no custom accessor code, consider the option of
using auto-implemented properties.

AUTO-IMPLEMENTED PROPERTIES
• Make property-declaration more concise when no additional logic is required
in the property accessors.
// Auto-Impl Properties for trivial get and set
public double TotalPurchases { get; set; }
• Properties vs. Public Variables
• Reflection works differently on variables vs. properties, so if you rely on reflection, it's
easier to use all properties.
• You can't databind against a variable.
• Changing a variable to a property is a breaking change. For example:
TryGetTitle(out book.Title); // requires a variable

INTERFACE PROPERTIES
• Properties can be declared on an interface. The following is an example of an
interface indexer accessor:
public interface ISampleInterface {
// Property declaration
// (not an auto-implemented property)
string Name { get; set; }
}
• The accessor of an interface property does not have a body.
• Thus, the purpose of the accessors is to indicate whether the property is read-
write, read-only, or write-only.

WHAT IS INDEXER ?
• Indexers are a syntactic convenience that enable you to create a class, struct,
or interface that client applications can access just as an array.
• Indexers are most frequently implemented in types whose primary purpose is
to encapsulate an internal collection or array (Ex: List, Dictionary…)
• To declare an indexer on a class or struct, use this keyword:
// Indexer declaration
public int this[int index] {
// get and set accessors
}

INDEXER EXAMPLE (DECLARING)
class SampleCollection<T> {
private T[] arr = new T[100];
// Define the indexer, which will allow client code
// to use [] notation on the class instance itself.
public T this[int i] {
get { return arr[i]; }
set { arr[i] = value; }
}
}

INDEXER EXAMPLE (USING)
// Declare an instance of the SampleCollection type.
SampleCollection<string> stringCollection =
new SampleCollection<string>();
// Use [] notation on the type.
stringCollection[0] = "Hello, World";
print(stringCollection[0]);

INDEXER OVERVIEW
• Indexers enable objects to be indexed in a similar manner to arrays.
• A get accessor returns a value. A set accessor assigns a value.
• The this keyword is used to define the indexers.
• The value keyword is used to define the value being assigned by the set indexer.
• Indexers do not have to be indexed by an integer value; it is up to you how to define
the specific look-up mechanism.
• Indexers can be overloaded.
• Indexers can have more than one formal parameter, for example, when accessing a
two-dimensional array.

INDEXER REMARKS
• The type of an indexer and the type of its parameters must be at least as
accessible as the indexer itself.
• The signature of an indexer consists of the number and types of its formal
parameters. It does not include the indexer type or the names of the formal
parameters.
• If you declare more than one indexer in the same class, they must have
different signatures.
• An indexer value is not classified as a variable; therefore, you cannot pass an
indexer value as a ref or out parameter.

INDEXERS IN INTERFACES
• Indexers can be declared on an interface.
• Accessors of interface indexers differ from the accessors of class indexers in
the following ways:
• Interface accessors do not use modifiers.
• An interface accessor does not have a body.
• Thus, the purpose of the accessor is to indicate whether the indexer is read-
write, read-only, or write-only.
public interface ISomeInterface {
// Indexer declaration:
string this[int index] { get; set; }
}

PROPERTIES VS INDEXERS
Property Indexer
Allows methods to be called as if they were public
data members.
Allows elements of an internal collection of an
object to be accessed by using array notation on the
object itself.
Accessed through a simple name. Accessed through an index.
Can be a static or an instance member. Must be an instance member.
A get accessor of a property has no parameters. A get accessor of an indexer has the same formal
parameter list as the indexer.
A set accessor of a property contains the implicit
value parameter.
A set accessor of an indexer has the same formal
parameter list as the indexer, and also to the value
parameter.
Supports shortened syntax with Auto-Implemented
Properties.
Does not support shortened syntax.

EXPRESSION BODIED MEMBERS
• https://csharp.christiannagel.com/2017/01/25/expressionbodiedmembers/

WHAT IS REGULAR EXPRESSION?
• A regular expression is a pattern that could be matched against an input text.
• A pattern consists of one or more character literals, operators, or constructs.
There are various categories of characters, operators, and constructs that lets
you to define regular expressions:
• Character escapes
• Character classes
• Anchors
• Grouping constructs
• Quantifiers
• Backreference constructs
• Alternation constructs
• Substitutions
• Miscellaneous constructs

THE REGEX CLASS
• The Regex class is used for representing a regular expression.
Methods & Description
public bool IsMatch(string input)
Indicates whether the regular expression specified in the Regex constructor finds a match in a specified input
string.
public bool IsMatch(string input, int startat)
public static bool IsMatch(string input, string pattern)
Indicates whether the specified regular expression finds a match in the specified input string.
public MatchCollection Matches(string input)
Searches the specified input string for all occurrences of a regular expression.
public string Replace(string input, string replacement)
In a specified input string, replaces all strings that match a regular expression pattern with a specified
replacement string.
public string[] Split(string input)
Splits an input string into an array of substrings at the positions defined by a regular expression pattern specified
in the Regex constructor.

REGEX MATCHING EXAMPLE
private static void showMatch(string text, string expr) {
Console.WriteLine("The Expression: " + expr);
MatchCollection mc = Regex.Matches(text, expr);
foreach (Match m in mc) {
Console.WriteLine(m);
}
}
static void Main(string[] args) {
string str = "A Thousand Splendid Suns";
Console.WriteLine("Matching words that start with 'S': ");
showMatch(str, @"bSS*");
}

REGEX REPLACING EXAMPLE
static void Main(string[] args) {
string input = "Hello World ";
string pattern = "s+";
string replacement = " ";
Regex rgx = new Regex(pattern);
string result = rgx.Replace(input, replacement);
Console.WriteLine("Original String: {0}", input);
Console.WriteLine("Replacement String: {0}", result);
}

CHARACTER CLASSES — d w s AND .

CHARACTER CLASSES — d w s AND .
• d, w and s also present their negations with D, W and S respectively.
• In order to be taken literally, you must escape the characters ^.[$()|*+?{with
a backslash as they have special meaning.
• You can match also non-printable characters like tabs t, new-lines n, carriage
returns r

FLAGS
• A regex usually comes within this form /abc/, where the search pattern is
delimited by two slash characters /. At the end we can specify a flag with
these values (we can also combine them each other):
• g (global) does not return after the first match, restarting the subsequent searches from
the end of the previous match
• m (multi-line) when enabled ^ and $ will match the start and end of a line, instead of the
whole string
• i (insensitive) makes the whole expression case-insensitive (for instance /aBc/i would
match AbC)

WHAT IS REFLECTION ?
• The classes in the System.Reflection namespace, together with System.Type,
enable you to obtain information about loaded assemblies and the types
defined within them.
• You can also use reflection to create type instances at run time, and to invoke
and access them.

USE OF REFLECTION
Class Usage
Assembly Define and load assemblies, load modules that are listed in
the assembly manifest, and locate a type from this assembly
and create an instance of it.
Module Discover information such as the assembly that contains the
module and the classes in the module. You can also get all
global methods or other specific, nonglobal methods
defined on the module.
ConstructorInfo Discover information such as the name, parameters, access
modifiers, and implementation details of a constructor. Use
the GetConstructors or GetConstructor method of a Type to
invoke a specific constructor

USE OF REFLECTION
Class Usage
MethodInfo Discover information such as the name, return type,
parameters, access modifiers, and implementation details of
a method. Use the GetMethods or GetMethod method of a
Type to invoke a specific method.
FieldInfo Discover information such as the name, access modifiers and
implementation details of a field, and to get or set field
values.
EventInfo Discover information such as the name, event-handler data
type, custom attributes, declaring type, and reflected type of
an event, and to add or remove event handlers.

USE OF REFLECTION
Class Usage
PropertyInfo Discover information such as the name, data type,
declaring type, reflected type, and read-only or writable
status of a property, and to get or set property values.
ParameterInfo Discover information such as a parameter's name, data
type, whether a parameter is an input or output
parameter, and the position of the parameter in a
method signature.
CustomAttributeData Discover information about custom attributes when you
are working in the reflection-only context of an
application domain. It allows you to examine attributes
without creating instances of them.

REFLECTION EXAMPLE
public class MyClass {
public virtual int AddNumb(int numb1,int numb2) { … }
}
…
MyClass myClassObj = new MyClass(); // Create MyClass object
Type myTypeObj = myClassObj.GetType(); // Get the Type information.
// Get Method Information.
MethodInfo myMethodInfo = myTypeObj.GetMethod("AddNumb");
object[] mParam = new object[] {5, 10};
// Get and display the Invoke method.
print("nFirst method - " + myTypeObj.FullName + " returns " +
myMethodInfo.Invoke(myClassObj, mParam) + "n");

USE OF REFLECTION
• The classes of the System.Reflection.Emit namespace provide a specialized
form of reflection that enables you to build types at run time.
• Reflection can also be used to create applications called type browsers, which
enable users to select types and then view the information about those types.
• Compilers for languages use reflection to construct symbol tables.
• The classes in the System.Runtime.Serialization namespace use reflection to
access data and to determine which fields to persist.
• The classes in the System.Runtime.Remoting namespace use reflection
indirectly through serialization.

WHAT IS ATTRIBUTE
• “Attribute is nothing but a piece of information”.
• This information can be attached to your method, class,
namespace, assembly etc.
• Attributes are part of your code this makes developers life
easier as he can see the information right upfront in the code
while he is calling the method or accessing the class and take
actions accordingly.
• Attributes are defined by using the “[]“ symbol.

ATTRIBUTE EXAMPLE
• For instance below is a simple class where
“Method1” is decorated by the “Obsolete”
attribute.
public class Class1 {
[Obsolete]
public void Method1() {
}
public void NewMethod1() {
}
}
• If somebody is trying to create
object of “Class1” he gets an alert

ATTRIBUTE EXAMPLE
• If you want to be bit strict and do not want developers to use that method,
you can pass ‘true” to the “Obsolete” attribute
[Obsolete("Please use NewMethod1", true)]
public void Method1(){}
• Now in case developer tries to make a call to “Method1” they will get error
and not just a simple warning

WRITING CUSTOM ATTRIBUTES
• Custom attributes are essentially traditional classes that derive directly or
indirectly from System.Attribute.
• Just like traditional classes, custom attributes contain methods that store and
retrieve data.
• The primary steps to properly design custom attribute classes are as follows:
• Declaring the attribute class
• Applying the AttributeUsageAttribute
• Declaring constructors
• Declaring properties

DECLARING THE ATTRIBUTE CLASS
• Attribute classes should be declared as public classes.
• By convention, the name of the attribute class ends with the word Attribute.
While not required, this convention is recommended for readability.
• When the attribute is applied, the inclusion of the word Attribute is optional.
• All attribute classes must inherit directly or indirectly from System.Attribute.

DECLARING THE ATTRIBUTE CLASS
• To create a custom attributes
you need to inherit from the
attribute class.
class HelpAttribute :
Attribute
{
public string HelpText
{ get; set; }
}
• “HelpAttribute” is applied to the “Customer” as
shown in the code below.
[Help(HelpText="This is a class")]
class Customer {
[Help(HelpText = "This is a property")]
public string CustomerCode { get; set; }
[Help(HelpText = "This is a method")]
public void Add(){ }
}

APPLYING THE ATTRIBUTE USAGE
• A custom attribute declaration begins with the AttributeUsageAttribute,
which defines some of the key characteristics of your attribute class.
• For example, you can specify whether your attribute can be inherited by other
classes or specify which elements the attribute can be applied to.
• The System.AttributeUsageAttribute has three members that are important
for the creation of custom attributes:
• AttributeTargets
• Inherited
• AllowMultiple.

ATTRIBUTE TARGETS MEMBER
• By using the “AttributeUsage” and “AttributeTargets”
you can restrict the attribute to a particular section
like class , method , property etc.
[AttributeUsage(AttributeTargets.Method)]
class HelpAttribute : Attribute {
public string HelpText { get; set; }
}
• You can also pass multiple instances of
AttributeTargets.
[AttributeUsage(AttributeTargets.Class |
AttributeTargets.Method)]

INHERITED PROPERTY
• The AttributeUsageAttribute.Inherited property indicates whether your
attribute can be inherited by classes that are derived from the classes to
which your attribute is applied.
• This property takes either a true (the default) or false flag.

ALLOW MULTIPLE PROPERTY
• The AttributeUsageAttribute.AllowMultiple property indicates whether
multiple instances of your attribute can exist on an element.
• true: multiple instances are allowed;
• false (the default): only one instance is allowed.
• When multiple instances of these attributes are applied, it produces a
compiler error.

DECLARING CONSTRUCTORS & PROPERTIES
• Declaring MyAttribute constructor & properties:
public MyAttribute(bool myvalue) { }
public string MyProperty { get; set; }
• Overload the constructor to accommodate different combinations of values.
• Use a combination of named and positional parameters when initializing the
attribute.
// One required (positional) and one optional (named) parameter
[MyAttribute(false, MyProperty = "optional data")]
public class SomeClass { }
// One required (positional) parameter is applied.
[MyAttribute(false)] public class SomeOtherClass { }

RETRIEVING INFORMATION STORED IN ATTRIBUTES
• Below is a custom attribute which describes length of characters for a
property of a class.
[AttributeUsage(AttributeTargets.Property)]
class Check : Attribute {
public int MaxLength { get; set; }
}
• Below is a customer class over which that property is decorated providing
information that the maximum length of “CustomerCode” property cannot
exceed 10 character.
[Check(MaxLength = 10)]
public string CustomerCode { get; set; }

// Get the type of the object
Type typeCustomer = objCustomer.GetType();
// Loop through all properties
foreach (PropertyInfo p in objtype.GetProperties())
{
// for every property loop through all attributes
foreach (Attribute a in p.GetCustomAttributes(false))
// TODO: Your code here
}
}

• // Loop through all properties
• foreach (PropertyInfo p in objtype.GetProperties()) {
• // for every property loop through all attributes
• foreach (Attribute a in p.GetCustomAttributes(false)) {
• Check c = (Check)a;
• if (p.Name == "CustomerCode") {
• // Do the length check
• if (obj.CustomerCode.Length > c.MaxLength) {
• throw new Exception(" Max length issues "); }
• }
• }
• }

VALUE AND REFERENCE TYPES
• Value types: Types that are stored directly and copied during parameter
passing.
These include integers, floats, booleans and Unity’s struct types (eg, Color and
Vector3).
• Reference types: Types that are allocated on the heap and then accessed via a
pointer.
Examples of reference types include objects, strings and arrays.

STACK ALLOCATION AND DEALLOCATION
• The stack works like a stack data type:
• it is a simple collection of elements, in this case blocks of memory,
• where elements can only be added and removed in a strict order.
• When a variable is stored on the stack, memory for it is simply allocated from
the "end" of the stack.
• When a stack variable goes out of scope, the memory used to store that
variable is immediately returned to the stack for reuse.

HEAP ALLOCATION
• The memory manager keeps track of areas in the heap that it knows to be
unused.
• When a new block of memory is requested, the manager allocate the block
from an unused heap area until there is no free area.
• A reference item on the heap can only be accessed as long as there are still
reference variables that can locate it.
• If all references to a memory block are gone then the memory it occupies can
safely be reallocated.

GARBAGE COLLECTION
• To determine which heap blocks are no longer in use, the memory manager
searches through all currently active reference variables and marks the
blocks they refer to as “live”.
• At the end of the search, any space between the live blocks is considered
empty by the memory manager and can be used for subsequent allocations.
• Garbage collection is automatic and invisible to the programmer but the
collection process actually requires significant CPU time behind the scenes.

WHEN DOES GARBAGE COLLECTION HAPPEN?
Three things can cause the garbage collector to run:
• The garbage collector runs whenever a heap allocation is requested that
cannot be fulfilled using free memory from the heap.
• The garbage collector runs automatically from time to time (although the
frequency varies by platform).
• The garbage collector can be forced to run manually.

PROBLEMS WITH GARBAGE COLLECTION
• The most obvious problem is that the garbage collector can take a
considerable amount of time to run.
• Another problem is that the garbage collector may run at inconvenient times.
• Another problem that is less obvious is heap fragmentation. There are two
consequences to a fragmented heap.
• The first is that our game’s memory usage will be higher than it needs to be
• and the second is that the garbage collector will run more frequently.

GC OPTIMIZATION
• It is best to avoid allocations as far as possible.
• However, given that they can’t be completely eliminated, there are two main
strategies you can use to minimize their intrusion into gameplay:
• Small heap with fast and frequent garbage collection
• Large heap with slow but infrequent garbage collection

FAST AND FREQUENT GC
• This strategy is often best for games that have long periods of gameplay
where a smooth framerate is the main concern. A game like this will typically
allocate small blocks frequently but these blocks will be in use only briefly.
• It can therefore be advantageous sometimes to request a garbage collection
at a regular frame interval:
if (Time.frameCount % 30 == 0){
System.GC.Collect();
}
• However, you should use this technique with caution and check the profiler
statistics to make sure that it is really reducing collection time for your game.

SLOW BUT INFREQUENT GC
• This strategy works best for games where allocations are relatively infrequent
and can be handled during pauses in gameplay.
• It is useful for the heap to be as large as possible without being so large as to
get your app killed by the OS due to low system memory.
• You can expand the heap manually by pre-allocating some placeholder space
during startup
var tmp = new System.Object[1024];
// make allocations in smaller blocks to avoid them to be
treated in a special way, which is designed for large
blocks
for (int i = 0; i < 1024; i++)
tmp[i] = new byte[1024];
// release reference
tmp = null;

MANUALLY FORCING GARBAGE COLLECTION
• If we know that heap memory has been allocated but is no longer used (for
example, if our code has generated garbage when loading assets)
• and we know that a garbage collection freeze won’t affect the player (for
example, while the loading screen is still showing),
• we can request garbage collection using the following code:
System.GC.Collect();

REDUCING THE AMOUNT OF GARBAGE CREATED
• Caching
• Don’t allocate in frequently called functions
• Clearing collections
• Object pooling

CACHING
• If our code repeatedly calls functions that lead to heap allocations and then
discards the results, this creates unnecessary garbage.
• Instead, we should store references to these objects and reuse them. This
technique is known as caching.
private Renderer[] allRenderers;
void Start() {
allRenderers = FindObjectsOfType<Renderer>();
}
void OnTriggerEnter(Collider other) {
ExampleFunction(allRenderers);
}

DON’T ALLOCATE IN FREQUENTLY CALLED FUNCTIONS
• If we have to allocate heap memory in a MonoBehaviour, the worst place we
can do it is in functions that run frequently.
• Update() and LateUpdate(), for example, are called once per frame, so if our
code is generating garbage here it will quickly add up.
• We should consider caching references to objects in Start() or Awake() where
possible, or ensuring that code that causes allocations only runs when it
needs to.

CLEARING COLLECTIONS
• If we find that we’re creating new collections more than once in our code, we
should cache the reference to the collection and use Clear() to empty its
contents instead of calling new repeatedly.
void Update()
{
List myList = new List();
PopulateList(myList);
}
private List myList = new List();
void Update()
{
myList.Clear();
PopulateList(myList);
}

REUSABLE OBJECT POOLS
• There are many cases where you can avoid generating garbage simply by
reducing the number of objects that get created and destroyed.
• There are certain types of objects in games, such as projectiles, which may be
encountered over and over again even though only a small number will ever
be in play at once.
• In cases like this, it is often possible to reuse objects rather than destroy old
ones and replace them with new ones.

COMMON CAUSES OF UNNECESSARY HEAP
ALLOCATIONS
• Strings
• Unity function calls
• Boxing
• Coroutines
• foreach loops
• Function references
• LINQ and Regular Expressions

STRINGS
• We should cut down on unnecessary string creation. If we are using the same string
value more than once, we should create the string once and cache the value.
• We should cut down on unnecessary string manipulations. For example, if we have a
Text component that is updated frequently and contains a concatenated string we
could consider separating it into two Text components.
• If we have to build strings at runtime, we should use the StringBuilder class. The
StringBuilder class is designed for building strings without allocations and will save on
the amount of garbage we produce when concatenating complex strings.
• We should remove calls to Debug.Log() as soon as they are no longer needed for
debugging purposes. A call to Debug.Log() creates and disposes of at least one string,
so if our game contains many of these calls, the garbage can add up.

UNITY FUNCTION CALLS
• Some Unity function calls create heap allocations, and so should be used with
care to avoid generating unnecessary garbage.
for (int i = 0; i <
myMesh.normals.Length; i++)
{
Vector3 normal = myMesh.normals[i];
}
Vector3[] ns = myMesh.normals;
for (int i = 0; i < ns.Length; i++)
{
Vector3 normal = ns[i];
}

UNITY FUNCTION CALLS
• GameObject.name
• GameObject.tag  GameObject.CompareTag()
• Input.touches  Input.GetTouch() and Input.touchCount
• Physics.SphereCastAll()  Physics.SphereCastNonAlloc()

BOXING
• Boxing creates garbage because of what happens behind the scenes.
• When a value-typed variable is boxed, Unity creates a temporary
System.Object on the heap to wrap the value-typed variable.
• A System.Object is a reference-typed variable, so when this temporary object
is disposed of this creates garbage.

COROUTINES
• Calling StartCoroutine() creates a small amount of garbage, because of the classes
that Unity must create instances of to manage the coroutine.
• yield statements within coroutines do not create heap allocations in their own right;
however, the values we pass with our yield statement could create unnecessary heap
allocations.
• yield return 0;  yield return null;
while (!isComplete) {
yield return new WaitForSeconds(1f);
}
WaitForSeconds delay = new WaitForSeconds(1f);
while (!isComplete)
{
yield return delay;
}

FOREACH LOOPS
• In versions of Unity prior to 5.5, a foreach loop iterating over anything other
than an array generates garbage each time the loop terminates.
• This is due to boxing that happens behind the scenes.
• A System.Object is allocated on the heap when the loop begins and disposed
of when the loop terminates. This problem was fixed in Unity 5.5.

FUNCTION REFERENCES
• References to functions, whether they refer to anonymous methods or named
methods, are reference-typed variables in Unity.
• They will cause heap allocations. Converting an anonymous method to a
closure (where the anonymous method has access to the variables in scope at
the time of its creation) significantly increases the memory usage and the
number of heap allocations.

MINIMIZE THE IMPACT OF GARBAGE COLLECTION
public struct ItemData {
public string name;
public int cost;
public Vector3 position;
}
private ItemData[] itemData;
private string[] itemNames;
private int[] itemCosts;
private Vector3[]
itemPositions;
• Avoid to examine things that it should not have to examine.

MINIMIZE THE IMPACT OF GARBAGE COLLECTION
• Having fewer object references in our code means that it has less work to do,
even if we don’t reduce the total number of objects on the heap.
public class DialogData {
private DialogData nextDialog;
public DialogData GetNextDlg()
{
return nextDialog;
}
}
public class DialogData {
private int nextDialogID;
public int GetNextDlgID()
{
return nextDialogID;
}
}

RERERENCES
• Properties (C# Programming Guide), Microsoft Developer Network, July 20, 2015
(https://msdn.microsoft.com/en-us/library/x9fsa0sw.aspx)
• Auto-Implemented Properties (C# Programming Guide), Microsoft Developer Network, July 20, 2015
(https://msdn.microsoft.com/en-us/library/bb384054.aspx)
• Interface Properties (C# Programming Guide) , Microsoft Developer Network, July 20, 2015
(https://msdn.microsoft.com/en-us/library/64syzecx.aspx)

REFERENCES
• Indexers (C# Programming Guide), Microsoft Developer Network, July 20, 2015
(https://msdn.microsoft.com/en-us/library/6x16t2tx.aspx)
• Using Indexers (C# Programming Guide) , Microsoft Developer Network, July 20, 2015
(https://msdn.microsoft.com/en-us/library/2549tw02.aspx)
• Indexers in Interfaces (C# Programming Guide) , Microsoft Developer Network, July 20, 2015
(https://msdn.microsoft.com/en-us/library/tkyhsw31.aspx)
• Comparison Between Properties and Indexers (C# Programming Guide), Microsoft Developer Network, July 20,
2015 (https://msdn.microsoft.com/en-us/library/4bsztef7.aspx)
• C# Attributes in 5 minutes, Shivprasad Koirala, 19 Oct 2014
(https://www.codeproject.com/Articles/827091/Csharp-Attributes-in-minutes)
• Writing Custom Attributes, Microsoft Developer Network (https://msdn.microsoft.com/en-
us/library/84c42s56(v=vs.110).aspx)

REFERENCES
• Reflection in the .NET Framework, Microsoft Developer Network (https://msdn.microsoft.com/en-
us/library/f7ykdhsy(v=vs.110).aspx)
• Reflection in .NET, keesari_anjaiah, 9 Feb 2010 (https://www.codeproject.com/Articles/55710/Reflection-in-
NET)
• Reflection in C# Tutorial, Idemudia Sanni Esangbedo, 28 Aug 2007
(https://www.codeproject.com/Articles/17269/Reflection-in-C-Tutorial)
• Understanding Automatic Memory Management, Unity
(https://docs.unity3d.com/Manual/UnderstandingAutomaticMemoryManagement.html)
• Optimizing garbage collection in Unity games, Unity
(https://unity3d.com/learn/tutorials/temas/performance-optimization/optimizing-garbage-collection-unity-
games)

REFERENCES
• Regex tutorial — A quick cheatsheet by examples, Jonny Fox – 23 Jun 2017 (https://medium.com/factory-
mind/regex-tutorial-a-simple-cheatsheet-by-examples-649dc1c3f285)

CSharp for Unity Day 3

More Related Content

What's hot (20)

Similar to CSharp for Unity Day 3 (20)

Recently uploaded (20)

CSharp for Unity Day 3