QuickFIX/n implements the FIX protocol on .NET.
C# Ruby Batchfile XSLT HTML Shell
#422 Compare This branch is 1001 commits ahead, 1 commit behind kennystone:master.
Latest commit 18f61e7 Oct 6, 2016 @mgatny mgatny committed on GitHub Merge pull request #418 from zherr/net4-5
Target .NET 4.5
Failed to load latest commit information.
AcceptanceTest target .net 4.5 Oct 4, 2016
Examples target .net 4.5 Oct 4, 2016
QuickFIXn target .net 4.5 Oct 4, 2016
UnitTests target .net 4.5 Oct 4, 2016
config WIP: release script Nov 9, 2011
generator (#175) correct some date fields to be generated/validated as DateOnly… Oct 3, 2013
resources/nunit updated solution to include nunit Jun 20, 2009
scripts uses latest aws sdk for release upload Jun 29, 2016
spec corrections/updates to FIX44 spec based on diff with QF/j version May 20, 2013
.gitattributes Update gitattributes to corrupt certificates Mar 31, 2013
.gitignore ignore a generated AT cfg Jun 9, 2015
.slugignore change all occurrences of "QuickFIX.net" to "QuickFIXn", including fi… Jun 27, 2012
CONTRIBUTING.md rm web, now hosted in gh-pages branch Apr 14, 2016
Gemfile removes more old web stuff, cleans up Gemfile Jun 29, 2016
Gemfile.lock removes more old web stuff, cleans up Gemfile Jun 29, 2016
LICENSE License file Nov 16, 2011
QuickFIXn.sln target .net 4.5 Oct 4, 2016
README.md removed xslt usage & dependency in readme Aug 10, 2016
RELEASE_NOTES.md version number for version v1.7.0 Jun 30, 2016
RELEASE_README.md reverts earlier deletion of RELEASE_README.md Jun 30, 2016
acceptance_test.bat (#80) AT: logon with reset after disconnect Jun 8, 2015
appveyor.yml appveyor yaml config file working Feb 4, 2016
build.bat target .net 4.5 Oct 4, 2016
build.sh target .net 4.5 Oct 4, 2016
generate.bat buildbot has trouble running this command. It will call this script i… Oct 25, 2011
package_release.bat removes generating of downloads page as part of release process Jun 28, 2016
unit_test.bat removed xslt usage & dependency in readme Aug 10, 2016
unit_test.sh removed xslt usage & dependency in readme Aug 10, 2016



Build status

For tutorials on how to use QuickFIX/n, visit the website.

This README is about setting up your system to do QuickFIX/n development.

System Setup

This project requires the following:

To build

  • Ruby (1.9.3 recommended) (used to generate message and field classes from the DataDictionary xml file)
  • Visual Studio 2010 or higher

To run tests

Code Generation

To regenerate the message and field class source from the Data Dictionaries, you need Ruby and the Nokogiri gem:

gem install nokogiri


To build the project, run:


You can also override the default target, configuration, and .NET framework version by giving command line arguments:

build.bat Rebuild Release v3.5

The build.bat script expects MSBuild.exe to be on your PATH. If you run it from a Visual Studio cmd shell, this should not be a problem. However, if you run it from some other shell (e.g. cygwin), you may need to append something like:


to your PATH environment variable. (Note, this build tools dir does not mean that the project will build for .NET 4.0; these are merely the build tools that come with VS 2010.)

Unit Tests

To run the NUnit tests, run:


(This script expects nunit-console.exe to be on your PATH. You may have to append something like C:\Program Files\NUnit 2.6.1\bin to your PATH environment variable.)

An HTML report of the test results will then be available here:


To run a Unit Test in the debugger (not sure if it works in VS Express):

  1. Right-click UnitTests project, click 'Properties'
  2. Go to Debug tab
  3. Change Start Action to 'Start external program: C:\Program Files\NUnit 2.6.1\bin\nunit.exe' (change the path to what is appropriate for your system)
  4. Set your 'Command line arguments' to 'C:\dev\quickfixn\UnitTests\bin\Debug\UnitTests.dll' (change the path to what is appropriate for your system)
  5. Set your 'Working directory' to 'C:\dev\quickfixn\UnitTests\bin\Debug\' (change the path to what is appropriate for your system)
  6. Open NUnit in debugger as follows: Right-click UnitTests, choose Debug->Start New Instance
  7. NUnit GUI will open and VS will be in debugger mode. You can choose and run tests. If you recompile, you may need to close and relaunch NUnit.

Acceptance Tests

To run the full suite of acceptance tests:


An HTML report of the test results will then be available here:


To run one particular acceptance test, e.g. fix42\14e_IncorrectEnumValue.def:

cd AcceptanceTest
runat.bat release 5003 definitions\server\fix42\14e_IncorrectEnumValue.def cfg\at_42.cfg

(See acceptance_test.bat for the proper port numbers and config files to use in the above command.)

The test results will then be available in AcceptanceTests\TestResults.xml and debug information will be available in the AcceptanceTests\log directory.

To run a test with the debugger,

  1. Open the solution file in Visual Studio
  2. Right click on "AcceptanceTest" project and choose "Properties" from the menu
  3. Click "Debug" on the left hand nav bar
  4. Set "Command line arguments" to the relevant "cfg\at_XX.cfg" for your test
  5. Set the working directory to "[yourpath]\quickfixn\AcceptanceTest"
  6. Save the properties
  7. Right click the "AcceptanceTest" project, go to Debug -> Start New Instance
  8. In command terminal, go into "AcceptanceTest" directory
  9. Run: ruby Runner.rb 5001 definitions\server\fix42\YourTestName.def


Connamara Systems

QuickFIXn is maintained and funded by Connamara Systems, llc.

The names and logos for Connamara Systems are trademarks of Connamara Systems, llc.


This software is available under the QuickFIX Software License. Please see the LICENSE for the terms specified by the QuickFIX Software License.