I am working on a graphics product where I want to release versions for iPhone, desktop OS / X, Windows Tablets, Silveright browser, Windows Mobile and Windows in this order of priority.
For GUI portability, the classic answer is to keep the core in C ++ and use thin layers of Cocoa / Objective-C or WPF / C #.
However, Silverlight complicates the choice.
I would have no problem porting my code to C ++ / CLI and maintaining a double code base (with some macros to fake contextual C ++ / CLI keywords and some forensic searches and replacements for ^ and%).
From what I have been able to find so far , it is unlikely that C ++ / CLI will be supported in Silverlight. This leaves me with options:
- Disabling source v1.0 C ++ migration to C # and ongoing concurrent maintenance
- Live porting with a tool (recommendations, please!) From C ++ to C # or vice versa, which is smooth enough to be part of the build process.
- The architectural separation of the version of Silverlight, so the C ++ logic remains on the server. I am a little uncomfortable to influence performance.
Can anyone suggest alternatives, provide good C ++ / CLI news in Silverlight, or recommend porting tools? I am comfortable enough in any language to make C ++ or C # the main language for the backend, provided the port is reliable.
:
, ", , # ++ , . , , - , ++ -OO-.