I'm using IQFeed 2.3.0.1 and the watchlist .NET examples, Level1 C Sharp COM and Level1 VB.NET COM, don't seem to work. Both will open and behave normally, producing no errors, but items added to the watchlist never generate any data in the watchlist window.

VB.NET code I've written also does not seem to respond to message events. But, the C++ watchlist example does work.

Any ideas on how I can get my .NET apps to respond to IQFeed events?

Can you elaborate on the issues with running the .NET example applications?

As far as getting your .NET app to respond to IQFeed events, you can reference the code of the .NET example applications.

---

Natalie Hannan DTN Market Access, LLC.

Let's focus on the vb.net example.

On installation of the latest version of IQFeed, a few .net examples are installed. vbdotnetlevel1com.exe is the example that shows up on my program menu as Level1 VB.NET COM.

When I run this example, the form captioned VbDotNetIQFeedY contains two List Boxes, lstAction and lstData. When the forms open, lstAction is blank, lstData contains this text "Click on RegisterClientApp to start the Feed"

I click on the button captioned "Register Client App"
A dialogue pops up and goes through the registration steps.
lstAction now says:
"Called IQFeedY::RegisterClient App"
lstData still says:
"Click on RegisterClientApp to start the Feed"

I click on the button captioned "Watch a Symbol"
A dialogue pops up and I enter the symbol "DELL" then press Okay.
lstAction now says:
"Called IQFeedY::RegisterClient App
Called IQFeedY::WatchSymbol ~ Dell"
lstData still says:
"Click on RegisterClientApp to start the Feed"

This remains the state of the a form. No data is ever presented in the lstAction window.

The same result occurs no matter what symbols I've tried.

When I open the example in Visual Studio .NET 2003, compile, and run the example, the result is the same. However, in the Solution Explorer window of visual studio it lists the vbDotNetLevel1Socket as unavailable and says the project file cannot be found.

I can duplicate the issue that you are having. Basically, you are getting logged in, and IQConnect.exe is dropping out. We are aware of this issue, and it is usually random.

What you should see is this:

After you click on the "Register Client App" button, a dialog pops up and goes through the log in process. (This part is working as expected for you). Then, you should see a blue icon in your systray. This is IQConnect. That icon should not disappear, and you should see the follwoing lines in lstData:

System Message: S,KEY,...
System Message: S,SERVER CONNECTED
System Message: S,IP,…..
System Message: S,CUST,…
System Message: S,KEYOK
IQFeed Started

These lines may not be in the same order, and the ... represents more data.

If you can try the test app a few times, you may be able to get IQConnect to stay in the sys tray, and then you should be able to run the test app just fine.

Please let me know what you find. Thanks!

---

Natalie Hannan DTN Market Access, LLC.

Bobby,

You wrote:
When I open the example in Visual Studio .NET 2003, compile, and run the example, the result is the same. However, in the Solution Explorer window of visual studio it lists the vbDotNetLevel1Socket as unavailable and says the project file cannot be found.


The vbDotNetLevel1Socket is a test app that we do not currently distribute. You should be able to build the Level1 VB.NET COM app and the Level1 C Sharp COM app. But, we will clean the project up, so you shouldn't be receiving that message in the future. Thanks!

---

Natalie Hannan DTN Market Access, LLC.

Natalie,

Is there a reason why you don't distribute the socket example? Because in the past it was recommanded to use the TCP interface for increased stability. Is the TCP interface still the best way to go?

thanks,

Jean-Francois
Edited by jfcantin on Jul 9, 2004 at 09:14 AM

Jean-Francois,

The socket example is not complete at this time. We are working towards providing both TCP and COM examples for C++, VB, Java, and .NET.

I can't really say which interface is more stable, as we have a fair amount of people on both. I'm not sure how long ago you were directed towards the TCP interface, but we may have made some improvements since then.

Thanks!

---

Natalie Hannan DTN Market Access, LLC.