Use this forum to ask questions after your subscription maintenance expires or 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.
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.
This topic is 6 years and 10 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
Product, version and build: PowerShell Studio 2017 / 5.4.140 32 or 64 bit version of product: x64 Operating system: Windows 2012 R2 32 or 64 bit OS: x64
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 ".".
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.
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.
This topic is 6 years and 10 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.