I spent a sleepless night trying to build QUICKFIX to have the 64-bit version of quickfix_net.dll and quickfix_net_messages.dll
My C# Framework is 64-bit and the regular offered QUICKFIX dll’s are 32-bit, so I have no other choice (Switching back my app to 32-bit is NOT an option)
I was expecting the VS_10 solution to build instantly (Poor little naive bunny…) but I have a bunch of unfound libraries errors (cannot open source file “xxxxxx.h”) for many #include “xxxxxx.h” statements. I have this behavior for the two project sources I have tried. I am puzzled as I am more of a .net guy and I did not manage to fix this on my own.
The original project source is downloadable here and the 64-bit fork which interest me most is here
If some of you could open quickfix_vs10.sln and have a clean compile I would be MORE than grateful as I could then get at least a couple of hours sleep in the company’s basement before getting back to work.
EDIT :
Detailed Errors :
- I have many unrecognized #include “quickfix/foo” > I have to remove all the “quickfix/” prefixes from the entires solution
- ‘FIX’ : is not a class or namespace name (especially in FieldMap.h)
- missing type specifier – int assumed. Note: C++ does not support default-int
-‘QuickFix::FieldNotFound __gc &’ : unable to throw or catch a managed object by value or reference
I have hundreds of each and many more… 🙁
EDIT : EFFICIENT ANSWER
If you want a REAL .Net FIX Engine, then you’d better go for VERSAFIX or QUICKFIX/N
Both are native .Net and Open Source, and hence compilable as x64 dlls (or x86if you like)
- QUICKFIX/N just came out and is very promising. Too bad it came out a few months after the post 🙁
- As of VERSAFIX, my company has used it for 6 Months and we are pretty satisfied so far.
(Russ Curry, the project initiator is technically rock solid and responsive.)
You should check out QuickFIX/n, a FIX library built specifically for .NET (without the unmanaged C++ wrapper). QuickFIX/n keeps all the good conventions of QuickFIX.