Search found 289 matches

by Bosparan
Wed Sep 04, 2013 2:29 am
Forum: Wish List and Feature Requests
Topic: PowerShell Studio Wishlist
Replies: 8
Views: 9762

Re: PowerShell Studio Wishlist

Hello David, Disable Autocomplete selectively Just tested the "Exact Match" option, but really, I fail to notice the difference to disabling auto-complete. If I have to type it in full anyway, there's not much to complete, is there? The thing is: I really like autocomplete for most things, except wh...
by Bosparan
Tue Sep 03, 2013 5:55 am
Forum: Wish List and Feature Requests
Topic: PowerShell Studio Wishlist
Replies: 8
Views: 9762

PowerShell Studio Wishlist

Hello, I've now been using PowerShell Studio 2012 for some time and have compiled a list of features I'd appreciate to have (if some of them already exist and I simply haven't noticed them, please tell me). Disable autocomplete selectively I'd really like to be able to disable the auto-complete func...
by Bosparan
Mon Aug 26, 2013 7:30 am
Forum: PowerShell Studio
Topic: [PS 3.1.23] Default assemblies from path fails
Replies: 5
Views: 3824

Re: [PS 3.1.23] Default assemblies from path fails

hi David, either I am misunderstanding you or you are misunderstanding me (I really am not sure which way it is). I have no problem getting PrimalSense working. If I add the assembly manually it works just fine. My problem is that I can't get it to do so automatically , by adding it to the default a...
by Bosparan
Fri Aug 23, 2013 6:47 am
Forum: PowerShell Studio
Topic: Intellisense not supporting cmdlets of other modules/snapins
Replies: 2
Views: 2420

Re: Intellisense not supporting cmdlets of other modules/sna

you can load nonstandard assemblies, by selecting: Home > Edit > Assemblies > "+" Either the assembly is listed there and you can add it, or select browse and navigate to the assembly and add it. Once added this way, intellisense worked for me, even for less common .NET assemblies. I can access all ...
by Bosparan
Fri Aug 23, 2013 2:31 am
Forum: Productivity Pack Support
Topic: PrimalPad 2012 comments/suggestions
Replies: 5
Views: 9021

Re: PrimalPad 2012 comments/suggestions

Tried it out and liked it, some abilities I'd like to have though: - Support for parameter-coloring (like "-path") - Support for multiline-comment coloring (<# ... #>) - Detection of non-standard library functions and parameters in coloring (Active directory, Exchange Management Shell, etc.) - FakeI...
by Bosparan
Fri Aug 23, 2013 12:10 am
Forum: PowerShell Studio
Topic: [PS 3.1.23] Default assemblies from path fails
Replies: 5
Views: 3824

Re: [PS 3.1.23] Default assemblies from path fails

Hi david, actually, I am always manually loading all assemblies I use (it happens that autoloading fails on some machines). I tried adding a local non-GAC assembly for intellisense purposes only. Importing it into the script by code works just fine, but does not provide intellisense coding support. ...
by Bosparan
Thu Aug 22, 2013 1:16 am
Forum: PowerShell Studio
Topic: [PS 3.1.23] Default assemblies from path fails
Replies: 5
Views: 3824

[PS 3.1.23] Default assemblies from path fails

Hello, I would like to add another assembly to the default assemblies that are loaded for every new opened script to provide intellisense. However, the assembly in question is not stored and detected where all the others are, it is placed in a path in its "C:\Program Files\..." subfolder. When I add...
by Bosparan
Tue Jul 30, 2013 4:56 am
Forum: PowerShell
Topic: Packagging script into file problem
Replies: 6
Views: 4054

Re: Packagging script into file problem

Hello jvierra, thanks for the answers. I found the problem on the msdn Exchange forum and thus I thought I'd drop a note on what the problem was, why I didn't find it and how it all turned out. Final version: function Get-EWSAppointments { Param( [Microsoft.Exchange.WebServices.Data.CalendarFolder]$...
by Bosparan
Mon Jul 29, 2013 5:55 am
Forum: PowerShell
Topic: Packagging script into file problem
Replies: 6
Views: 4054

Packagging script into file problem

Hello fellow scripters, I am trying to create a calendar sync using EWS. This functionen is trying to mess with me though: It works just fine if run as script (and returns all the appointments in the calendar), but returns $null if run after packaging (PowerShell 2, standard manifest for elevation)....