Converting C# code to C++ is a daunting task.
First, there is the lack of memory management (ie garbage collector) in C++. At least, nothing native to C++. Perhaps with some specialized library there could be something to be done.
Second, most of the Converting C# code to C++ is a daunting task.
First, there is the lack of memory management (ie garbage collector) in C++. At least, nothing native to C++. Perhaps with some specialized library there could be something to be done.
Second, the .Net framework contains an enormous number of different features which would need to be emulated or re-coded (independently of the .Net framework flavour, ie Mono or Microsoft).
Third, it would be easier to have a concise and useful answer if we knew the context. Because, porting C# code to C++ is not really useful in and out of itself.
Fourth, a lot of construct are C# specific. Some equivalence exist in C++ but not everything. For an example, I haven't seen a reflection utility in C++ except for the part in System.Reflection in .Net. Also, building a virtual machine for the scripts is in some way what the Mono project is about.
RunUO doesn't have unconsidered dependencies. Even if the choice of using .Net was made way back, other options sure were considered and rejected at that time. Also, except for computer with win9x-me, most computer can run RunUO to some extent using Mono or .Net Framework. For computer on windows, newer version of windows are already packaged with .Net...
In conclusion, more details on the why we would want to convert RunUO to C++ might be a good thing. That way, we could perhaps propose alternatives to your problem beside converting which would be less time consuming or just plain better.
ZixThree