{"id":260,"date":"2009-11-17T13:27:13","date_gmt":"2009-11-17T03:27:13","guid":{"rendered":"http:\/\/www.doolwind.com\/blog\/?p=260"},"modified":"2009-11-17T13:27:13","modified_gmt":"2009-11-17T03:27:13","slug":"using-csharp-for-a-commercial-game","status":"publish","type":"post","link":"https:\/\/www.doolwind.com\/blog\/using-csharp-for-a-commercial-game\/","title":{"rendered":"Using C# For a Commercial Game"},"content":{"rendered":"

\"\"<\/a>Does the title of this article make you cringe?\u00a0 People have mixed feelings when it comes to C# and the .NET framework.\u00a0 Just like many hardcore game developers 10 years ago swore that games should only be made in straight C, many developers today say that C++ is the only way to go.\u00a0 This article outlines my reasoning for using C# for a commercial game on PC.<\/p>\n

Rapid Application Development<\/strong><\/p>\n

The primary reason for using C# is because coding in it is more productive than any other language I’ve used.\u00a0 Language features like interfaces, generics and delegates make it a cleaner language than C++.\u00a0 Development practices such as unit testing and dependency injection are also easier to use in C#.\u00a0 This clarity translates to more readable code and less bugs, particularly when working with a larger or younger team of developers.<\/p>\n

The second productivity gain comes from having access to the .NET framework.\u00a0 From its XML handling for configuration, to built-in math libraries, many of the core functions you can think of are taken care of.\u00a0 This saves you writing the code yourself and lets a reliable, tested framework do the heavy lifting in areas you don’t want to spend your time.<\/p>\n

C# lets you focus on making a game rather than writing an engine, or learning someone else’s engine.<\/p>\n

Unified Code – Client, Server, Tools, Scripting<\/strong><\/p>\n