The reason for this is because of the silly decision to include half of the module on the application market download, and the other half of the module in the Crestron Database itself. Whenever there is a #CRESTRON_SIMPLSHARP_LIBRARY directive in a SIMPL+ source file, rather than a #USER_SIMPLSHARP_LIBRARY directive, the search path for the library is intended to be the local Crestron Database itself rather than the user folders. Typically the Crestron-variant is found within a *.csp file rather than a *.usp too.
Presuming that this strange combination of a user-SIMPL+ extension and Crestron library directive still works, it means that you would need to have a compatible database anytime you want to use these modules because it points towards your Crestron Database by default. If you took the library out of the database and changed it to the user directive, that would probably work too.
I used to have no idea why they did this, then soon realized that the sandbox validation worked a bit differently between the two. :)
--
?
Crestron Service Provider - TBD Enterprises Inc.
Troy Garner