SAPIEN Technologies

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.

Forum rulesDO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.

Actually I did explicitly use the -Path parameter in our main library - just not in the example.
Figured some of it out on my own by now:
The reason I received no Primal Sense at all was due to an option that wasn't set after upgrade:
Editor > Primal Sense > "Enable word completion while typing"
This also returned the ability to receive primal sense for functions as I type them.

However!
For .NET types this doesn't work as it should. Specifically, even with this option set, I cannot navigate the namespaces for my custom libraries at all: When typing official libraries, I can type the first namespace segment (e.g.: "System.") and receive primal sense for all classes, enumerations, namespaces, etc. below it. For custom libraries it will only show me the class-names.
For a simple library with 2-3 classes that's ok, but in our case ... our main library alone has (currently) 344 classes in 28 nested namespaces. Going by name alone is very troublesome in this case - I need the namespace structure to navigate it properly.