Getting-IQFeed-fundamental-data-in-a-strategy

QUOTE:
What is the equivalent [using ...] directive I should use in WL7?

CODE:
using WealthLab.IQFeed; //* IQFeed IQFundamental class here *//

I struggled to figure this out too. I think I ended up using the VS Object Browser to see which WL7 DLL file contained the IQFundamental class I needed.

The IQFundamental class works just as it did in WL6. For example, in my WLTrading class (of Local.Components.dll)

CODE:
double sharesOutstanding = 0.0;
try
{
    sharesOutstanding = IQFundamental.ValueDouble(bars.Symbol, "Common shares outstanding") * 1000.0;
}
catch (Exception ex)
{
    WLHost.Instance.AddLogItem("WLTrading", "Couldn't fetch \"shares outstanding\" for " + bars.Symbol, Color.Yellow, ex);
}

Superticker, thanks very much for jumping in and providing the insight here. You're right on target with your advice.

But I'm wondering why neither of you located the informaton in the help, a query for IQFeed yields the info which we've documented. What can we do to make something like this more discoverable in the help?

Thanks for the help with WL7 Help. No, I didn't know IQFeed was documented there. I think the main problem is that users search the QuickRef then give up. Perhaps if a search of the QuickRef doesn't get a hit, then the search should automatically continue to search for a hit in the Help document as well. Let's call this a "metaseach" feature request.

In the IQFeed Help example, I would include the comment line ...

CODE:
using WealthLab.IQFeed; //* IQFeed IQFundamental class here *//

just to clarify where the IQFundamental class is located so users better understand why that using statement is included.

I would also state in the Help example that some of these fundamentals require an additional fundamental subscription from the DTN IQFeed vendor to return data. And to check DTN's website for subscription options.

Good point, extensions can also inject content into the QuickRef so it makes sense to document that class there as well.