Use this forum to ask questions before you buy. Need information on licensing or pricing? Questions about a trial version? This is the right place for you. No scripting questions, please.
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.
- Posts: 10
- Joined: Thu May 25, 2017 11:22 am
Product, version and build
: PowerShell Studio 2017 / 5.4.140
32 or 64 bit version of product
: Windows 2012 R2
32 or 64 bit OS
I am trialing PowerShell Studio for my company and I'm running into a small issue that I suspect is my fault. There is no autocomplete or intellisense when referring to a class object after pressing the ".".
File #1 (myClass.ps1)
File #2 (TestFile.ps1)
Code: Select all
$mySite = [SPWeb_Helper]::new();
First off, when I type "$mySite." it doesn't provide me with any properties or methods in the class. Second, when I type "$mySite.siteObject." it does not provide me with any intellisense for the SPWeb object. This works both in ISE and Visual Studio. I'm certain PowerShell Studio supports this functionality I'm just doing it wrong.
- Posts: 5913
- Joined: Thu Aug 18, 2011 4:56 am
Adding PrimalSense for classes is on our TODO list.
Note: The PowerShell runspace runs in a separate process from the UI and the runspace is reset after each run, so that information isn't readily available.
SAPIEN Technologies, Inc.