Declaring types doesn't to trigger PrimalSense

Support for all customers who have purchased a PrimalScript product license. This forum does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE 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.
User avatar
greatbarrier86
Posts: 11
Joined: Mon Jan 11, 2010 1:57 am

Declaring types doesn't to trigger PrimalSense

Post by greatbarrier86 » Thu Dec 02, 2010 11:24 pm

Hello. I think i'm doing this correctly, but I want to create an object and have primalsense show the members of that object.

so i did,
[System.Data.SqlClient.SqlConnection] $connection = New-Object "System.Data.SqlClient.SqlConnection" $connectionString

But when i type $connection. nothing shows up. Shouldn't it expand the members of the SqlConnection class?

User avatar
Alexander Riedel
Posts: 6972
Joined: Tue May 29, 2007 4:43 pm

Declaring types doesn't to trigger PrimalSense

Post by Alexander Riedel » Fri Dec 03, 2010 4:15 am

Yes it should. What's the OS and what framework versions do you have installed?
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
Alexander Riedel
Posts: 6972
Joined: Tue May 29, 2007 4:43 pm

Declaring types doesn't to trigger PrimalSense

Post by Alexander Riedel » Fri Dec 03, 2010 7:46 am

Please look in your PrimalScript application folder and tell us what size and version PSInfo.dll is.
Please also include the complete PrimalScript version and build number.
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
Alexander Riedel
Posts: 6972
Joined: Tue May 29, 2007 4:43 pm

Declaring types doesn't to trigger PrimalSense

Post by Alexander Riedel » Sun Dec 05, 2010 9:47 am

We have found an issue that relates to an update to the .NET framework. One of the types prior to the System.Data assembly throws an exception and terminates loading. A fix is included in the next service build.



Explicit declaration of types should not be required if you use New-Object with the full type.

Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
greatbarrier86
Posts: 11
Joined: Mon Jan 11, 2010 1:57 am

Declaring types doesn't to trigger PrimalSense

Post by greatbarrier86 » Mon Dec 06, 2010 4:24 am

Sorry for the delay

Windows 7 Professional x32
All .NET Versions including 4.0 (Visual Studio is also installed)
PSInfo.dll version is 2.0.379.27495

Pre-upgrade, PrimalScript version was 5.0.637greatbarrier862010-12-06 11:26:17

User avatar
greatbarrier86
Posts: 11
Joined: Mon Jan 11, 2010 1:57 am

Declaring types doesn't to trigger PrimalSense

Post by greatbarrier86 » Mon Dec 06, 2010 4:38 am

Update: the new version fixed the issues i was describing.

Question though, should it expand this?

$oShell = New-Object -ComObject WScript.Shell

I only ask because $oShell. does not expand the primalsense box.

User avatar
Alexander Riedel
Posts: 6972
Joined: Tue May 29, 2007 4:43 pm

Declaring types doesn't to trigger PrimalSense

Post by Alexander Riedel » Mon Dec 06, 2010 6:55 am

Enclose ProgIds in quotes:


$oShell = New-Object -ComObject "WScript.Shell"

Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
greatbarrier86
Posts: 11
Joined: Mon Jan 11, 2010 1:57 am

Declaring types doesn't to trigger PrimalSense

Post by greatbarrier86 » Mon Dec 06, 2010 10:42 pm

Much appreciated Alex. That worked great! :)