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 was able to capture variable value using $dte.debugger.GetExpression("variable).value. I can not successfully get the value for complex object or DataSet. How can i get a value from a DataSet or a custom object using GetExpression like this $dte.Debugger.GetExpression("byDataSet")?
This PowerShell tool is the best and keep up the good work!
I have the same issue. It appears to be loading a previous version of the script even though I have made changes and saved the file. Closing the file out and reopening does not fix the issue. The only thing that seems to work is closing VS and reopening it.
I have the same question/issue. I'd like to import the PowerCLI module so intellisense works for VMware cmdlets. I've tried adding 'Import-Module vmware.vimautomation.core' to the script itself, I've opened a PowerShell session and imported the module. I even added it to my user startup script. That last one finally allowed me to complete VMware cmdlets names by hitting tab. However, it won't autocomplete parameters ... so I'm stuck writing out the whole thing manually.
Is this something that's supported?
This situation started to appear after I updated PoSh tools to version 3.0.177.
I open Powershell script project with several scripts. When I make changes to script and trying to save (Ctrl + S or by pressing button on toolbar) VisualStudio crashes with standard message "Visual Studio stopped working..."
Tried to save C# file - its ok. So the problem is in this extension.
Please fix it.
After installing v3.0.163, I couldn't type capital 'E' character (Shift + E) in the C# editor. I think it's a very critical bug. Some people might be mad at Visual Studio 2015 if they would not know that actually it's your plugin causes that.
This also happened to me. Found the "Shift+E, F5" chord bound to the EditorContextMenus.CodeWindow.PowerShell.ExecuteAsScript command.
It makes typing things like "IEnumerable" unnecessarily difficult.
This was working just fine for me in VS 2013 but when I installed VS 2015 RC I get the following error:
Message: Failed to load Pester module. The specified module 'Pester' was not loaded because no valid module was found in any module directory.
I get this error in BOTH Visual Studio 2013 and Visual Studio 2015 now. I have uninstalled the Powershell Tools and reinstalled them in both IDEs. Pester tests work fine when invoked in a standard Powershell. I only get this message in Visual Studio.
I was getting this earlier today. For me the problem was that I had a custom nuget.config file which was placing downloaded packages out to a ../lib directory rather than the default ./packages. Removing this made everything work again.
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?
I've created Powershell script project in VS 2015, and started creating my script. Then i left VS window for some time and worked with other programs. And when i came back to VS, and wanted to type somethimg in script tab, VS hanged, and dialog about "Visual studio is waiting for the end of operation" was shown. Reopening VS does not help. I can no more work with powershell script.