Game Development Reference
.NET application can catch every error in the system, allowing for graceful error
handling and termination. The only time when additional work must be done to
ensure proper error handling is when an exception is thrown from a legacy appli-
cation wrapped into a managed assembly. In addition to excellent error handling,
.NET applications allocate and release memory through a reference counting
garbage collector by default, ensuring that the application does not leak memory
and the lifetimes of all objects are managed.
There are numerous other benefits when using .NET for tools, many of which will
be covered in greater detail later in the topic.
In reality, a game engine tool can be developed in many different languages: Perl,
Python, C\C++, Java, and Visual Basic, to name a few. So why use .NET? Tools
enhance workflow and manage game content, so it is desirable to build these tools
as quickly as possible. The faster a tool is developed, the sooner the end user can
begin using it, improving productivity or producing game content earlier, most
likely saving money or man hours in the process.
The .NET platform promotes robust design with a rapid application development
nature, which is a perfect match for tools development. Many times a lot of utility
functionality must be developed before the actual logic for the tool is addressed.
The .NET framework provides countless functionality for technologies like XML,
encryption, file system access, security, and data manipulation, to name a few.
Development time for a tool can be better spent on logic and usability, rather than,
on utility functionality that the tool is dependent on.