Page 1 of 1

Declaring types doesn't to trigger PrimalSense

Posted: Thu Dec 02, 2010 11:24 pm
by greatbarrier86
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?

Declaring types doesn't to trigger PrimalSense

Posted: Fri Dec 03, 2010 4:15 am
by Alexander Riedel
Yes it should. What's the OS and what framework versions do you have installed?

Declaring types doesn't to trigger PrimalSense

Posted: Fri Dec 03, 2010 7:46 am
by Alexander Riedel
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.

Declaring types doesn't to trigger PrimalSense

Posted: Sun Dec 05, 2010 9:47 am
by Alexander Riedel
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.


Declaring types doesn't to trigger PrimalSense

Posted: Mon Dec 06, 2010 4:24 am
by greatbarrier86
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

Declaring types doesn't to trigger PrimalSense

Posted: Mon Dec 06, 2010 4:38 am
by greatbarrier86
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.

Declaring types doesn't to trigger PrimalSense

Posted: Mon Dec 06, 2010 6:55 am
by Alexander Riedel
Enclose ProgIds in quotes:


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


Declaring types doesn't to trigger PrimalSense

Posted: Mon Dec 06, 2010 10:42 pm
by greatbarrier86
Much appreciated Alex. That worked great! :)