Search found 55 matches
- Sat Feb 27, 2010 5:08 am
- Forum: PrimalScript
- Topic: Internal PowerShell debugger error
- Replies: 8
- Views: 3120
Internal PowerShell debugger error
I've narrowed it down using the latest service build. This code:$output = New-Object PSObject -Property @{ owner = "hello" priority1 = & { $count = 42 $count }}$outputWorks just fine using the internal debugger, but if I add another property assigned to the output of a scriptblock:$out...
- Thu Feb 11, 2010 3:36 am
- Forum: PrimalScript
- Topic: Internal PowerShell debugger error
- Replies: 8
- Views: 3120
Internal PowerShell debugger error
Bollocks is totally a technical term, right up there with 'hoojoo'. :)I tried reading the debugger chapters in the manual, but couldn't follow the bits about the Machine Debug Manager service and what not on my Windows 7 box. Maybe I just missed the service or something, but that's why I mentioned t...
- Mon Feb 08, 2010 7:22 am
- Forum: PrimalSQL
- Topic: Juuust about to go insane...
- Replies: 2
- Views: 3631
Juuust about to go insane...
Alright, I'll give that a shot the next time it bites me. Thanks for the quick reply
- Mon Feb 08, 2010 3:58 am
- Forum: PrimalScript
- Topic: Internal PowerShell debugger error
- Replies: 8
- Views: 3120
Internal PowerShell debugger error
Windows 7 Pro x64PrimalScript 2009 5.0.625 (Elevated)[edit]debugging vbScript files appears to function just fine, I tested breakpoints & variable inspection etc. That said:[/edit]When attempting to debug the following (indeed any PowerShell script I have attempted to debug), using the internal ...
- Mon Feb 08, 2010 2:33 am
- Forum: PrimalSQL
- Topic: Juuust about to go insane...
- Replies: 2
- Views: 3631
Juuust about to go insane...
So I've been using PrimalSQL for awhile now, and have noticed multiple things that are starting to drive me nuts. Here's the platform I'm working on:Windows 7 Pro x64PrimalSQL 1.1.0When attempting to design queries, often the table window resize/move/close/etc. will refuse to respond for a given tab...
- Fri Jan 29, 2010 8:16 am
- Forum: PrimalScript
- Topic: Parameter primalsense for PowerShell functions
- Replies: 17
- Views: 5395
Parameter primalsense for PowerShell functions
Added the import-module command to my primalscript profile and the completion works just like I would expect, I get the complete parameter list after typing the first hyphen.One thing that would be nice would be some type information in the dropdown menu like you get in the tooltip that appears when...
- Fri Jan 29, 2010 8:10 am
- Forum: PrimalScript
- Topic: Parameter primalsense for PowerShell functions
- Replies: 17
- Views: 5395
Parameter primalsense for PowerShell functions
No, not yet. I just finished the first module today. Haven't tried that part yet...I'll do it now and let you know.And of this language specification, what does one look like, and who specifically should I nag? (cause I will )
- Fri Jan 29, 2010 8:08 am
- Forum: PrimalScript
- Topic: Filter names not added to PrimalSense
- Replies: 1
- Views: 942
Filter names not added to PrimalSense
Windows 7 Pro 64-bitPowershell 2PrimalScript 2009 5.0.625While function names are added to the PrimalSense autocomplete list, filters do not seem to be:Sorry to be such a pest today, just posting as I come across stuff....
- Fri Jan 29, 2010 7:56 am
- Forum: PrimalScript
- Topic: Parameter primalsense for PowerShell functions
- Replies: 17
- Views: 5395
Parameter primalsense for PowerShell functions
Aha! Note-to-self: Evidently the tooltip will not appear until after the file is saved...I had been creating a new powershell file and testing it. Once I saved the file on a hunch, there's the tool tip after typing the opening parenthesis.That solved, did I understand you correctly that being able t...
- Fri Jan 29, 2010 7:46 am
- Forum: PrimalScript
- Topic: Parameter primalsense for PowerShell functions
- Replies: 17
- Views: 5395
Parameter primalsense for PowerShell functions
I've updated to the latest build already as I noted above: Just to make sure I wasn't behind in versions causing the problem, I updated to the latest build, 5.0.625.