Other than this, there is nothing specifically designed that I know of, but it does look like each of the engines you mentioned does have a separate forum or mailing list you could try.
I can tell you that the way QuickFix is designed can be a real pain due to the way is uses identical classes in separate namespaces for each version of FIX.
I suggest using the MoMA tool provided by http://www.mono-project.com/MoMA. I took the first one you specified "QuickFix" and downloaded the Binary version and scanned it with MoMA. The result was 273 Method calls that are not implemented.
It may sound like a lot but just like compiler errors, you fix a couple of things and the number goes down fast, also you have good odds that the parts you need will be fine and with the source for QuickFix available you may be able modify the code as needed or just throw some try{...}catch wrappers around those problem functions that you do need to use.
Of course you can try the same thing on the other available products, I just tried the first one. I believe MoMA will also work on obfuscated code, so you could test it on trial versions too.
我正在研究 Quickfix/N，它声称是开源本机 . Quickfix 的网络端口，没有本机 C++ 绑定。事实上，该 API 看起来与 Quickfix/J（Java 端口）非常相似。如果我发现它不兼容 Mono，我会更新这篇文章。
I'm looking into Quickfix/N, which claims to be an open-source native .Net port of Quickfix, without native C++ bindings. In fact the API looks very similar to Quickfix/J (The java port). I will update this post if I find it not to be Mono-compatible.
发布评论
评论（4）
我尝试了 2 个开源解决方案：
I tried the 2 open sources solutions :
一种可能的解决方案： http://www.fixprotocol.org/discuss/read/adec4479
除此之外，据我所知，没有什么专门设计的，但看起来您提到的每个引擎确实都有一个单独的论坛或邮件列表，您可以尝试一下。
我可以告诉您，QuickFix 的设计方式可能非常痛苦，因为该方式在每个版本的 FIX 的单独命名空间中使用相同的类。
抱歉没有更好的答案，祝你好运。
One possible solution: http://www.fixprotocol.org/discuss/read/adec4479
Other than this, there is nothing specifically designed that I know of, but it does look like each of the engines you mentioned does have a separate forum or mailing list you could try.
I can tell you that the way QuickFix is designed can be a real pain due to the way is uses identical classes in separate namespaces for each version of FIX.
Sorry dont have a better answer, good luck.
我建议使用 http://www.mono-project.com/MoMA 提供的 MoMA 工具。我拿了你指定的第一个“QuickFix”并下载了二进制版本并用 MoMA 扫描了它。结果是 273 个方法调用未实现。
听起来可能很多，但就像编译器错误一样，你修复了一些东西，数量就会快速下降，而且你也很有可能你需要的部分会很好，并且有了 QuickFix 的源代码，你也许可以修改根据需要编写代码，或者只是在您确实需要使用的那些问题函数周围抛出一些 try{...}catch 包装器。
当然，您可以在其他可用产品上尝试相同的操作，我刚刚尝试了第一个。我相信 MoMA 也适用于混淆代码，因此您也可以在试用版上进行测试。
I suggest using the MoMA tool provided by http://www.mono-project.com/MoMA. I took the first one you specified "QuickFix" and downloaded the Binary version and scanned it with MoMA. The result was 273 Method calls that are not implemented.
It may sound like a lot but just like compiler errors, you fix a couple of things and the number goes down fast, also you have good odds that the parts you need will be fine and with the source for QuickFix available you may be able modify the code as needed or just throw some try{...}catch wrappers around those problem functions that you do need to use.
Of course you can try the same thing on the other available products, I just tried the first one. I believe MoMA will also work on obfuscated code, so you could test it on trial versions too.
我正在研究 Quickfix/N，它声称是开源本机 . Quickfix 的网络端口，没有本机 C++ 绑定。事实上，该 API 看起来与 Quickfix/J（Java 端口）非常相似。如果我发现它不兼容 Mono，我会更新这篇文章。
I'm looking into Quickfix/N, which claims to be an open-source native .Net port of Quickfix, without native C++ bindings. In fact the API looks very similar to Quickfix/J (The java port). I will update this post if I find it not to be Mono-compatible.