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
I have a Script project created with the PowerShell Project Template.
I can create a folder, but i am unable to right click on the folder and add new items.
When i right click on a folder my Visual Studio just craches.
My current workaround is to unload the project and edit the .pssproj file. Am i the only one experiencing this problem? Anyway i can solve it?
I know others have seen this in the past and I thought it had been fixed. There was also an error when some other extension was installed (I can't remember which now). If you could get a crash dump, that would be very helpful.
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>" ...
On Windows 8.1 Host using Visual Studio 2013 Ultimate Update 4 to Windows Server 2012, unable to Enter-PSSession to VM target machines with the following error:
PS C:\WINDOWS\system32> Enter-PSSession -ComputerName <computer>
[ERROR] Enter-PSSession : Connecting to remote server <computer> failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while
[ERROR] using Kerberos authentication: There are currently no logon servers available to service the logon request.
[SNIP] Possible causes are:
Also fails from the target machine to the Host. Works fine between VM to other windows server 2012 VMs on the domain. Works fine to the VM machine from a physical Windows 8.0 machine on the domain. Have checked and re-checked trusted hosts, firewall, SPN configuration. VS hangs when using "Enter Powershell Sesson" using icon.
This sounds like it could be a networking issue. Does the same command work in PowerShell.exe? VS shouldn't hang though. That sounds like a bug. It'd be great if you could open an issue on GitHub so we can track it.
Thanks for getting back to me, Adam.
The problem is on my end. Noticed today that the command line prompt defaults to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE" instead of "..Visual Studio 12.0\Common7..." in the REPL window as on my other machines. Apparently this is a side-by-side issue from long ago when I removed VS 2012 and installed VS 2013. The VSIX is installing PowerShell Tools in the correct folder. Can you suggest a way to configure this properly by hand without uninstalling VS 2013?
Noticed from "Get-PSSessionConfiguration" that the working instances are running PSVersion 3.0 and the affected machine is running 4.0. In response to your earlier question, PowerShell ISE and Windows Powershell are both working fine(PSVersion 3.0 snd 4.0 respectively).
Ok. If there is a difference between the ISE, then we certainly have a problem. A couple things that I would suggest.
Turn on some logging for PoshTools: https://github.com/adamdriscoll/poshtools/wiki/Debugging-PowerShell-Tools-for-Visual-Studio
Open an issue on GitHub and provide the log contents around the time you when to try and connect to the remote machine.
The Microsoft guys should be able to help more with this one as they helped to implement all the remoting support.
Hit you on twitter, but the first time you launch in vs2015 RC, you must open the output window manually before you can see results from scripts: ctrl-alt-o. This was not the behavior in vs2013. I just tested on a clean vs2013 and installed both at the same time from the installer.
Visual Studio 2013 Update 4 with this installed, I cannot turn off Automatic brace completion.
Tools -> Options -> Text Editor -> All Languages (or PowerShell) -> General
Clear the checkbox, restart, the option is selected.
Uninstall this extension; the option works as expected.
Reinstall latest extension; problem returns.
Is there anyway to use this with scripts requiring a lower version of the .net frameworks like v2.0/v3.5?
Specifically, if you are using this to develop scripts for SharePoint 2010 ( Microsoft.Sharepoint.PowerShell), .NET 4 can't be used.
That's an interesting issue. We'd have to see if we could compile the PowerShell host EXE as 3.5. Not sure if that is possible. Could you open a GitHub issue so we can track it?
I would like to use this adding. Unfortunately, the project I am working on is complex and we can't just rewrite everything to use VS projects.
Need support for invoking the debugger from the interactive PS debugger window. When I put breakpoints into sources of modules that are currently loaded, I need the break points to stop execution that is initiated in the interactive debugger window. Powershell_ise supports this scenario. Need the same from VS for it to be useful.
I've just installed this extension, and now I get this error message when starting up VS 2013 Update 4. I first got a warning I needed 'Management Tools' (or similar) for Windows 7, which I duly installed and restarted, now I get the error. Anyone else?