Anyone interested in working on an OSS FIX Engine for .NET?

Imported from previous forum

Hi All,

I’m preparing to release the first alpha release of an open source FIX engine that we’ve been developing for the .NET platform (C#) and was curious if anyone is interested in jumping in and helping with some of the remaining development work.

We’ve put a lot of effort into developing a good architecture and object model for the system, and support for FIX 5.0+ was a foundation requirement when we started, so it’s in pretty good shape for handling all current and future versions of the protocol. Where we do need some help is in the resend/recovery logic, and in the code generation space where we are trying to think about a good object model for output from a code generator - creating typesafe classes from the dictionaries and so on. There are also a lot of fun tools that could be built around the system, so we’d like to get some people involved on that side of things as well.

This is a pretty good time to jump in as a contributor - we have most of the core code written and it’s well documented so there isn’t a bunch of grunt work that needs to be done. It’s mostly the high end work that needs to occur now - code generation, performance tuning, tweaks to the object model and so on…

If anyone is interested in helping out with the project, please shoot me an email and let me know!

I have sent a mail with my profile.

Thanks,
Raghavendra Masineni

Hi All,

I’m preparing to release the first alpha release of an open source FIX
engine that we’ve been developing for the .NET platform (C#) and was
curious if anyone is interested in jumping in and helping with some of
the remaining development work.

We’ve put a lot of effort into developing a good architecture and
object model for the system, and support for FIX 5.0+ was a foundation
requirement when we started, so it’s in pretty good shape for handling
all current and future versions of the protocol. Where we do need some
help is in the resend/recovery logic, and in the code generation space
where we are trying to think about a good object model for output from
a code generator - creating typesafe classes from the dictionaries and
so on. There are also a lot of fun tools that could be built around
the system, so we’d like to get some people involved on that side of
things as well.

This is a pretty good time to jump in as a contributor - we have most of
the core code written and it’s well documented so there isn’t a bunch of
grunt work that needs to be done. It’s mostly the high end work that
needs to occur now - code generation, performance tuning, tweaks to the
object model and so on…

If anyone is interested in helping out with the project, please shoot me
an email and let me know!

I will be interested in take a look at the product. Please send me the details. Should be able to provide the feedback to my best as working wiht FIX for few years. Thanks.

Regard,
Amit

I have sent a mail with my profile.

Thanks, Raghavendra Masineni

Hi All,

I’m preparing to release the first alpha release of an open source FIX
engine that we’ve been developing for the .NET platform (C#) and was
curious if anyone is interested in jumping in and helping with some of
the remaining development work.

We’ve put a lot of effort into developing a good architecture and
object model for the system, and support for FIX 5.0+ was a foundation
requirement when we started, so it’s in pretty good shape for handling
all current and future versions of the protocol. Where we do need some
help is in the resend/recovery logic, and in the code generation space
where we are trying to think about a good object model for output from
a code generator - creating typesafe classes from the dictionaries and
so on. There are also a lot of fun tools that could be built around
the system, so we’d like to get some people involved on that side of
things as well.

This is a pretty good time to jump in as a contributor - we have most
of the core code written and it’s well documented so there isn’t a
bunch of grunt work that needs to be done. It’s mostly the high end
work that needs to occur now - code generation, performance tuning,
tweaks to the object model and so on…

If anyone is interested in helping out with the project, please shoot
me an email and let me know!

Do you a webpage with the code?

Thanks,

Kenny Stone
Connamara Systems, LLC

Hi All,

I’m preparing to release the first alpha release of an open source FIX
engine that we’ve been developing for the .NET platform (C#) and was
curious if anyone is interested in jumping in and helping with some of
the remaining development work.

We’ve put a lot of effort into developing a good architecture and
object model for the system, and support for FIX 5.0+ was a foundation
requirement when we started, so it’s in pretty good shape for handling
all current and future versions of the protocol. Where we do need some
help is in the resend/recovery logic, and in the code generation space
where we are trying to think about a good object model for output from
a code generator - creating typesafe classes from the dictionaries and
so on. There are also a lot of fun tools that could be built around
the system, so we’d like to get some people involved on that side of
things as well.

This is a pretty good time to jump in as a contributor - we have most of
the core code written and it’s well documented so there isn’t a bunch of
grunt work that needs to be done. It’s mostly the high end work that
needs to occur now - code generation, performance tuning, tweaks to the
object model and so on…

If anyone is interested in helping out with the project, please shoot me
an email and let me know!

Do you a webpage with the code?

Thanks,

Kenny Stone Connamara Systems, LLC

Hi Kenny,

Sure - shoot me an email and I’ll get you set up with access to everything. We’re still getting the code structured for release so we’re not quite ready to publish the links to the world…

Cheers,

russ

Hi Russel,

I have about 2 years of experience in FIX - mostly 4.2 and am certified in C#.NET 2.0. I’m not sure how much I’ll be able to help, but am greatly interested in contributing whatever I can and learning as much as possible in the process. Count me in!

Kind Regards,

Prateek Jain

Hi All,

I’m preparing to release the first alpha release of an open source FIX
engine that we’ve been developing for the .NET platform (C#) and was
curious if anyone is interested in jumping in and helping with some of
the remaining development work.

We’ve put a lot of effort into developing a good architecture and
object model for the system, and support for FIX 5.0+ was a foundation
requirement when we started, so it’s in pretty good shape for handling
all current and future versions of the protocol. Where we do need some
help is in the resend/recovery logic, and in the code generation space
where we are trying to think about a good object model for output from
a code generator - creating typesafe classes from the dictionaries and
so on. There are also a lot of fun tools that could be built around
the system, so we’d like to get some people involved on that side of
things as well.

This is a pretty good time to jump in as a contributor - we have most of
the core code written and it’s well documented so there isn’t a bunch of
grunt work that needs to be done. It’s mostly the high end work that
needs to occur now - code generation, performance tuning, tweaks to the
object model and so on…

If anyone is interested in helping out with the project, please shoot me
an email and let me know!

Has this been uploaded anywhere yet? Interested in taking a look…

Hi All,

I’m preparing to release the first alpha release of an open source FIX
engine that we’ve been developing for the .NET platform (C#) and was
curious if anyone is interested in jumping in and helping with some of
the remaining development work.

We’ve put a lot of effort into developing a good architecture and
object model for the system, and support for FIX 5.0+ was a foundation
requirement when we started, so it’s in pretty good shape for handling
all current and future versions of the protocol. Where we do need some
help is in the resend/recovery logic, and in the code generation space
where we are trying to think about a good object model for output from
a code generator - creating typesafe classes from the dictionaries and
so on. There are also a lot of fun tools that could be built around
the system, so we’d like to get some people involved on that side of
things as well.

This is a pretty good time to jump in as a contributor - we have most of
the core code written and it’s well documented so there isn’t a bunch of
grunt work that needs to be done. It’s mostly the high end work that
needs to occur now - code generation, performance tuning, tweaks to the
object model and so on…

If anyone is interested in helping out with the project, please shoot me
an email and let me know!

Yes, I am interested as well. Please let me know the next steps.

thanks

Looking forward to it.

L. Singh

Hi All,

I’m preparing to release the first alpha release of an open source FIX
engine that we’ve been developing for the .NET platform (C#) and was
curious if anyone is interested in jumping in and helping with some of
the remaining development work.

We’ve put a lot of effort into developing a good architecture and
object model for the system, and support for FIX 5.0+ was a foundation
requirement when we started, so it’s in pretty good shape for handling
all current and future versions of the protocol. Where we do need some
help is in the resend/recovery logic, and in the code generation space
where we are trying to think about a good object model for output from
a code generator - creating typesafe classes from the dictionaries and
so on. There are also a lot of fun tools that could be built around
the system, so we’d like to get some people involved on that side of
things as well.

This is a pretty good time to jump in as a contributor - we have most of
the core code written and it’s well documented so there isn’t a bunch of
grunt work that needs to be done. It’s mostly the high end work that
needs to occur now - code generation, performance tuning, tweaks to the
object model and so on…

If anyone is interested in helping out with the project, please shoot me
an email and let me know!

please count me in…

Hi All,

I’m preparing to release the first alpha release of an open source FIX
engine that we’ve been developing for the .NET platform (C#) and was
curious if anyone is interested in jumping in and helping with some of
the remaining development work.

We’ve put a lot of effort into developing a good architecture and
object model for the system, and support for FIX 5.0+ was a foundation
requirement when we started, so it’s in pretty good shape for handling
all current and future versions of the protocol. Where we do need some
help is in the resend/recovery logic, and in the code generation space
where we are trying to think about a good object model for output from
a code generator - creating typesafe classes from the dictionaries and
so on. There are also a lot of fun tools that could be built around
the system, so we’d like to get some people involved on that side of
things as well.

This is a pretty good time to jump in as a contributor - we have most of
the core code written and it’s well documented so there isn’t a bunch of
grunt work that needs to be done. It’s mostly the high end work that
needs to occur now - code generation, performance tuning, tweaks to the
object model and so on…

If anyone is interested in helping out with the project, please shoot me
an email and let me know!

Hi!
I’m interested: I’m developing a FIX Engine with C#3.0 (.NET Fx 3.5) including FIX 5.0.

Let’s talk about it

Lanfranco

Hi All,

I’m preparing to release the first alpha release of an open source FIX
engine that we’ve been developing for the .NET platform (C#) and was
curious if anyone is interested in jumping in and helping with some of
the remaining development work.

We’ve put a lot of effort into developing a good architecture and
object model for the system, and support for FIX 5.0+ was a foundation
requirement when we started, so it’s in pretty good shape for handling
all current and future versions of the protocol. Where we do need some
help is in the resend/recovery logic, and in the code generation space
where we are trying to think about a good object model for output from
a code generator - creating typesafe classes from the dictionaries and
so on. There are also a lot of fun tools that could be built around
the system, so we’d like to get some people involved on that side of
things as well.

This is a pretty good time to jump in as a contributor - we have most of
the core code written and it’s well documented so there isn’t a bunch of
grunt work that needs to be done. It’s mostly the high end work that
needs to occur now - code generation, performance tuning, tweaks to the
object model and so on…

If anyone is interested in helping out with the project, please shoot me
an email and let me know!