We went in great lengths to provide high quality documentation. However, in some cases listed below we had to make some compromises: 

1. Namespace resolution 

The following classes:

• FileSignal
• IIRFilters
• LInearSystems
• OptimalFir
• SignalProcessing
• SignalTools
• SignalUtils

are specified to exist within Dew.Signal namespace, but their actual namespace is Dew.Signal.Units. This is also why in the code examples there is always Dew.Signal.Units uses clause included. 

2. The out parameter 

Sometimes the "out" parameter is falsely indicated in the docs as "ref". Follow the instructions of the VS.NET IDE about what parameter is expected. 

3. Using HTML chm files 

When using HTML1 chm files, you might end up with the following error : Help file that comes up with all topics in the tree on the left, but a Page Not found or Operation Aborted error in the IE content window; an IE error. The CHM file obviously opened since the topic list is there, but IT refuses to display the content. 

There are two scenarios that can fail here:

• Open the CHM file from a network resource. If you open the CHM file from a network resource such as a mapped drive you will get this error. The fix is to copy the file to a local drive and then it should work.
• CHM File downloaded from the Internet. You’ve downloaded and directly opened a CHM file from the Internet in the Temporary Internet folder. This folder is isolated and treated specially as Internet Zone content. Most likely it will not allow running the ActiveX content that actually drives the CHM engine. Solution: Don’t ‘run’ the CHM file off the Web, but rather copy it to file first.

There’s more detailed information of the issue and links to Microsoft KB articles.