[This message was posted by Russell Curry of Assimilate Technology, Inc. <r...@assimilate.com> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/e38e70b0 - PLEASE DO NOT REPLY BY MAIL.]
> Dean, Thanks for the clarification - I understand what you are saying. > Since .NET uses neither Java or C++ which do you think is the better > choice? Also what about QuickFix no longer being developed. Are bug > fixes resolved faster with QuickFix/J? Is one community now much larger > than the other? Thanks for any info! Hi Erik, If you're talking native language integration, then from a .NET perspective it might be easier to use QuickFix/C++ since it comes with a set of C# wrappers that allow you to integrate it right into a .NET project. On the other hand, as Dean mentioned, the QuickFix/J project does support FIX 5.0. Not only that, but the QuickFix/J project seems to be more active in general. I guess it depends on your requirements, but there are plenty of ways you could integrate QuickFix/J with your C#/.NET applications. Regards, Russ [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to FIX-Protocol@googlegroups.com To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
