在非托管C ++代码中使用C＃属性(Use C# properties in unmanaged C++ code)

 我们有一个主要用C＃编写的大型项目（服务，多线程等）。 但是，核心数字运算算法是用非托管C ++写成的（OpenMP等）。 
 
 不幸的是，目前我们不得不在这两个世界之间交换数据。 也就是说，我们必须为每个C ++类在C ++ / CLI中编写包装类。 对于（几乎）在C＃ - “world”中的任何必需设置（属性），C ++世界中存在一个副本（头文件），并在包装​​类中来回显式转换。 这种体系结构看起来非常低效且相当容易出错。 
 
 主要问题：有没有办法在非托管C ++中自动以某种方式自动共享C＃类？ （我们必须读写！） 
 
 第二个问题：您能否就上述情况提供如何改进架构的建议。 我们的一个考虑是完全切换到C ++，但必须找到合适的库并为我们在.NET中执行的所有（系统）事情编写干净的代码，这一点感觉不好。 
 
 非常感谢您的帮助和最诚挚的问候，Jakob 

We have a large project mainly written in C# (services, multithreading etc.). However, the core number crunching algorithms are written in unmanaged C++ to be fast (OpenMP etc.).
 
Unfortunately, at the moment we have to do a lot of effort to exchange data between these two worlds. I.e., we have to write wrapping classes in C++/CLI for each of the C++ classes. For (virtually) any required setting (Properties) in the C#-"world" there is a copy in the C++ world (a header file) and an explicit conversion back and forth in the wrapper class. This architecture seems very inefficient and quite error-prone.
 
Primary question: Is there a way to share a C#-class with properties somehow automatically in unmanaged C++? (we have to read and write!)
 
Secondary question: Could you give any advice of how to improve the architecture in a case as described above. One consideration of ours was to completely switch to C++, but having to find appropriate libraries and write clean code for all the (system-)things we do in .NET at the moment does not feel good.
 
Many thanks for your help and best regards, Jakob

原文：https://stackoverflow.com/questions/10011956