Hi, Great tool I downloaded, setup the tools and fired VS 2013 premium, created a script project but I am not getting the Intellisense I have WMF 5 Feb preview on win 8.1 box Should it work correctly or not because of WMF 5? Thanks in advance
Running VS 2015 Community edition on Win 7 Enterprise. The PoshTool add-on fails to initialize with following message.
"PowerShell host initializing has not yet completed, please try again later."
I experienced the same error on VS 2013 Community edition as well.
Could you please open an issue on GitHub? It'll get more attention from the Microsoft team.
We have seen issues where execution policy prevents the host from starting up properly. What is your x64\x86 policy set to?
Just trying this out... this is a great addition to VS. Thanks for it. Two things I noticed:
1) The Enter key seems to invoke some kind of autocomplete when it's not always appropriate, e.g. if I just type "d:" and hit enter, it adds the path of the first alphabetic folder on D. It's kind of awkward to just change drives, I have to use shift-enter followed by enter
2) What color profile properties are used? The colors are pretty unreadable -- I assume this has to do with my own Visual Studio scheme, but I'm not sure what I need to change to alter the colors used by the shell.
1. We've done some work around IntelliSense lately. Can you give the latest dev bits a try? https://ci.appveyor.com/project/PoshTools-MSFT/poshtools/branch/dev We should be releasing an update shortly.
2. If you go into Tools->Options->Fonts and Colors, you will see options for PowerShell.
When starting VS 2015 RC window with title "PowerShell Tools for Visual Studio Error", and a label with the text
"Failed to initialize PowerShell Tools for Visual Studio.System.Reflection.TargetINvocationException: Exception has been thrown by the target of an invocation. --->
Micarosoft.VisualStudio.COmposition.CompositionFailedException: Expected 1 export(1) with contract name "PowerShellTools.VisualStudioEvents" but found 0 after applying applicable constraints.
... (snip) ...
-- End of inner exception stack trace --
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
... (snip) ...
at Microsoft.VisualStudio.Shell.Package.GetDialogPage(Type dialogPageType)
is shown. VS starts after clicking OK on this dialog.
I get a similar error when starting VS2015RC on W10P10122.
"Failed to initialize PowerShell Tools for Visual StudioSystem.InvalidOperationException: Collection type must derive from ICollection<T>" ...
very excited to finally use a proper IDE for powershell, just downloaded ps tools and installed on windows 7 x64, with VS 2013 SP4 and now getting an error whenever I attempt to create a new PS project.
VS complains pssproj type is not supported by this version of the application. Any ideas what I'm doing wrong? I've selected all .net versions from the drop down box but that hasn't done me any good.
Furthermore, the version that was installed on my machine is 22.214.171.124 and even if i do an update from VS it tells me that "The extension is already installed to all applicable products.". (I haven't restarted the machine yet.)
I need the script files that are on the project to be copied to my build drop folder. I created a PowerShell Script Project and I see that it does not even have a 'Build' option, so I can't use something like post build scripts.
Is there a way to make the project "Buildable" and then put the script files in the output folder?