Re: [Quickfix-users] Testing Quickfix .NET API with NUnit Framework

[Greg S. <gre...@ch...>]

Oren

=20

I just rebuilt with the latest QuickFIX release (1.12.4) and got the
same error.  Have you heard of other people having a similar problem
before?  It seems like it has happened before
(http://sourceforge.net/mailarchive/message.php?msg_id=3D10062941
<http://sourceforge.net/mailarchive/message.php?msg_id=3D10062941> ).  =
It
looks like some sort of issue with garbage collection and
managed/unmanaged code.  The strange this is that it only happens when
testing against NUnit.  Any other ideas?

=20

Thanks,

Greg

=20

________________________________

From: Oren Miller [mailto:or...@qu...]=20
Sent: Tuesday, October 17, 2006 10:24 AM
To: Greg Snow
Cc: qui...@li...;
qui...@li...
Subject: Re: [Quickfix-users] Testing Quickfix .NET API with NUnit
Framework

=20

Is it possible you can try this with the latest release?

=20

--oren

=20

On Oct 17, 2006, at 8:43 AM, Greg Snow wrote:





We have an application using the QuickFix .NET API (Quickfix version
1.10.2).  When trying to run unit tests using the NUnit framework, we
are getting exceptions of the type 'System.ArgumentException : Cannot
pass GCHandle across app domains.'  At first, it appeared to be a bug in
our code, but that doesn't seem to be the case.  This exception only
occurs when unit testing with NUnit.  We can compile to an executable
and the same code runs without errors.

 The exception is being thrown from mscorlib.dll (line 118 of the
gcroot.h header).  The function throwing the exception and the
debugger's stack trace are attached in a text file.

 I have also come across another develop with the exact same problem
(his initial post is here:
http://sourceforge.net/mailarchive/message.php?msg_id=3D10062941).  I
contacted him and he said that he never came up with a solution and was
forced to write his own FIX implementation.  Any help on this issue
would be appreciated.  Thanks.




This message is intended only for the personal and confidential use of =
the recipients named above. If the reader of this email is not the =
intended recipient, you have received this email in error and any =
review, dissemination, distribution or copying is strictly prohibited. =
If you have received this email in error, please notify the sender =
immediately by return email and permanently delete the copy you =
received.=20

This message is provided for informational purposes and should not be =
construed as a solicitation or offer to buy or sell any securities or =
related financial instruments. CTC Holdings nor any affiliates ("CTC") =
are responsible for any recommendation, solicitation, offer or agreement =
or any information about any transaction, customer account or account =
activity that may be attached to or contained in this communication. CTC =
accepts no liability for any content contained in the email, or any =
errors or omissions arising as a result of e-mail transmission. Any =
opinions contained in this email constitute the sender's best judgment =
at this time and are subject to change without notice.=20

=20