Chris Egerter
Newcomer
This week I have gone back to porting the Power Render engine to .NET. The port has been lying around for almost a year and I haven't finished it because of lack of interest.
However recently the demand for .NET support has increased. Porting 50-60 examples to VB and C# is a time consuming process, but rewarding to see them working in other languages.
There are lots of .NET languages popping up, Cobol, Fortan, Python, and Perl to name a few. When done right it is possible to expose nearly all of the API to languages I never thought would be supported.
Will commercial games be written in .NET? Probably not at this point, but the work I've done so far shows that this is entirely possible when using a managed wrapper over a C/C++ engine DLL.
However recently the demand for .NET support has increased. Porting 50-60 examples to VB and C# is a time consuming process, but rewarding to see them working in other languages.
There are lots of .NET languages popping up, Cobol, Fortan, Python, and Perl to name a few. When done right it is possible to expose nearly all of the API to languages I never thought would be supported.
Will commercial games be written in .NET? Probably not at this point, but the work I've done so far shows that this is entirely possible when using a managed wrapper over a C/C++ engine DLL.
