Game Development Reference
In-Depth Information
chapter 45
Testing for the
Availability of
the .NET Framework
The only way to learn a new programming language is by writing programs
in it.
Dennis Ritchie
Managed applications on the .NET platform have access to a wealth of features
and prebuilt functionality, dramatically decreasing development time. Deploying
.NET applications is also extremely simple, provided the required runtime is pre-
sent. Managed applications have a dependency on the Common Language
Runtime and the class framework assemblies, and will not function without them.
Deploying these applications generally entails that you check to see if the operat-
ing system has the .NET runtime and, if not, install it. Some installation packagers
have bootstrapper utilities that can automate this process for you, but generally
you are on your own.
One solution is to take the manual approach by attempting to run the application.
If it does not load, you obviously require the .NET runtime. This approach is not
a clean way to handle deployment.
Another solution is to check the Win32 registry for entries, keys like:
HKEY_LOCAL_MACHINE\Microsoft\.NETFramework\policy\v1.1
HKEY_LOCAL_MACHINE\Microsoft\.NETFramework\policy\v2.0
While checking the registry will work in many situations, there are some cases
where the installation folder has been renamed or a service pack has been applied
that will not be reflected with these registry keys.
569
Search Nedrilad ::




Custom Search