Indeed

Turned out to be a system file indexation problem. The files were actually present in the bin folder, but for some reason, oq didn't see them. Fix=use regedit to open HKEY_LOCAL_MACHINE then ctrl-f key combo to search for .dll in question (ex: SYSTEM.DLL) this will tell you which one win7 is using (not so obvious otherwise). Use windows explorer to copy it to oq bin folder (on my machine="C:\Program Files (x86)\SmartQuant Ltd\OpenQuant 2\Bin\System.dll". But mostly, one needs (that's how i solved this prob. anyway...) to grapple with file index options (configuration panel) to make sure it's indexing system files (which by default it doesn't...) which makes the dll visible to oq (is this just my machine or is this normal?). Was wondering, final detail on this, what effect does adding a dll to the build have on memory usage by oq. Especially the case where a dll is loaded, but in a given solution is not invoked by the 'using' c# keyword?
