Most times, the DLL is named after the default namespace, which would suggest that a simple
using ServiceProvider; should
help, but that didn't work. When using closed-source SDKs that you purchase licenses for from some company, it is pretty common to
find that their namespaces are named after the company itself. In this case, the root of the namespace hierarchy was
after the company.
Object Browser When you double-click the reference in the Solution Explorer, the Object Browser opens up with the double-clicked referenced assembly pre-selected. All you have to do then is to expand the selected row to see all namespaces included in the dll file.