PowerGUI Visual Studio Extension

Created Issue: "Show all files" in Project crashes extension [32267]

JesperRou — Thu, 16 Feb 2012 14:59:11 GMT

When one clicks the "Show all files" icon in the Solution Explorer, for the PS project, the Solution gets checked out, the solution file (.pssproj) gets added to the solution (circular reference?) and you get an exception window with "Object reference not set to an instance of an object."

A similar thing happens if you right-click the project and tries to Add->Existing File.

This error occurs in both 1.5.1 and the previous version I had installed (can't remember which that was).
Both versions with PowerGUI 3.1 installed.

Commented Issue: Automatic checkout from TFS [32095]

LennartJansson2 — Thu, 19 Jan 2012 11:07:07 GMT

When I open a powershellscript stored in TFS then it will check out the file automatically just by using the cursor keys to move around in the source code. Meaning that if I read a lot of source code files that way I will have a lot of pending checkins afterwards even if I didn't make any actual change.
Comments: ** Comment from web user: LennartJansson2 **

Maybe I should mention that my settings on checkout behaviour in TFS is the default settings = not get latest on checkout and checkout automatically when changes are made. I am using 1.5.1 Beta 2 together with PowerGui 3.1.0.2058

Created Issue: Automatic checkout from TFS [32095]

LennartJansson2 — Thu, 19 Jan 2012 11:03:29 GMT

Reviewed: PowerGUI VSX 1.5.1 - Beta 2 (Dec 29, 2011)

CraigMartin — Thu, 29 Dec 2011 16:36:05 GMT

Rated 5 Stars (out of 5) - Saves me from having two editors open (PowerGUI and VS) since I use TFS for Source Control. Very nice!

Closed Issue: Should work with PowerGUI Pro [30898]

AdamDriscoll — Tue, 13 Dec 2011 03:15:14 GMT

PowerGUI VSX requires PowerGUI even if PowerGUI Pro is installed.
Comments: Resolved with changeset 94719.

Source code checked in, #94719

AdamDriscoll — Tue, 13 Dec 2011 03:15:10 GMT

PowerGUI VSX now will work with PowerGUI Pro.

Created Issue: PowerGUI VSX 1.5.1 - Beta 2: Can not use F9 to set breakpoints [31893]

zenowolf — Tue, 06 Dec 2011 05:59:36 GMT

Environment :PowerGUI VSX 1.5.1 +PowerGUI 3.1
Issue : Can not set breakpoints through press F9

Created Issue: PowerGUI VSX 1.5.1 - Beta 2: Can not use F9 to set breakpoints [31892]

zenowolf — Tue, 06 Dec 2011 05:59:33 GMT

Environment :PowerGUI VSX 1.5.1 +PowerGUI 3.1
Issue : Can not set breakpoints through press F9

New Post: SharePoint

richfinn — Thu, 03 Nov 2011 15:54:28 GMT

Yes - this would be really nice to have, since there's so much powershell in SP2010...

Updated Wiki: Home

AdamDriscoll — Thu, 27 Oct 2011 14:00:30 GMT

The PowerGUI Visual Studio Extension adds PowerShell IntelliSense support to Visual Studio.

PowerGUI VSX is driven by PowerGUI. Please download the correct version:

PowerGUI VSX 1.4.1 Requires PowerGUI 3.0
PowerGUI VSX 1.5 Beta 2 Requires PowerGUI 3.1

New Features

PowerGUI Console Tool Window
PowerShell Project Type

Current Features

IntelliSense support through a custom PowerShell editor
Syntax highlighting and script analysis
Supports PowerGUI settings
Supports PowerGUI imported modules
Supports PowerGUI Snippets
PowerShell debugging
PowerGUI Console Tool Window
PowerShell Project Type

Debug binary modules using the PowerGUI VSX!

Check out my blog for updates! And if you don't want to wait that long follow me on Twitter!

Updated Wiki: Home

AdamDriscoll — Thu, 27 Oct 2011 13:59:56 GMT

The PowerGUI Visual Studio Extension adds PowerShell IntelliSense support to Visual Studio.

PowerGUI VSX is driven by PowerGUI. Please download the correct version:

PowerGUI VSX 1.4.1 Requires PowerGUI 3.0
PowerGUI VSX 1.5 Beta 2 Requires PowerGUI 3.1

New Features

PowerGUI Console Tool Window
PowerShell Project Type

Current Features

IntelliSense support through a custom PowerShell editor
Syntax highlighting and script analysis
Supports PowerGUI settings
Supports PowerGUI imported modules
Supports PowerGUI Snippets
PowerShell debugging
PowerGUI Console Tool Window
PowerShell Project Type

Debug binary modules using the PowerGUI VSX!

Check out my blog for updates! And if you don't want to wait that long follow me on Twitter!

Updated Wiki: Home

AdamDriscoll — Thu, 27 Oct 2011 13:58:30 GMT

Project Description

The PowerGUI Visual Studio Extension adds PowerShell IntelliSense support to Visual Studio.

PowerGUI VSX 1.4.1 Requires PowerGUI 3.0
PowerGUI VSX 1.5 Beta 2 Requires PowerGUI 3.1

New Features

PowerGUI Console Tool Window
PowerShell Project Type

Current Features

IntelliSense support through a custom PowerShell editor
Syntax highlighting and script analysis
Supports PowerGUI settings
Supports PowerGUI imported modules
Supports PowerGUI Snippets
PowerShell debugging
PowerGUI Console Tool Window
PowerShell Project Type

Debug binary modules using the PowerGUI VSX!

Check out my blog for updates! And if you don't want to wait that long follow me on Twitter!

Commented Issue: PowerGUI VSX does not work with latest Power GUI Update [31646]

AdamDriscoll — Thu, 27 Oct 2011 13:55:21 GMT

Updated PowerGUI to latest 3.1 release - now get error that VSX will not run. Unloaded and reloaded VSX after update - still no joy.
NOT GOOD!
Comments: ** Comment from web user: AdamDriscoll **

Give PowerGUI VSX 1.5 Beta 2 a shot. It adds support for PowerGUI 3.1.

Created Issue: PowerGUI VSX does not work with latest Power GUI Update [31646]

ehuggz — Thu, 27 Oct 2011 13:22:17 GMT

Updated PowerGUI to latest 3.1 release - now get error that VSX will not run. Unloaded and reloaded VSX after update - still no joy.
NOT GOOD!

New Post: Fails to load in Visual Studio 2010 Ultimate

sfeldman — Thu, 27 Oct 2011 02:56:04 GMT

I see the confusion now. PowerGUI is a product on it's own, that should be downloaded from http://www.powergui.org

PowerGUI VSX is VS.NET addin that utilizes PowerGUI. You can't run it w/o installing PowerGUI first.

This is what I was missing the whole time :)

New Post: Fails to load in Visual Studio 2010 Ultimate

adamdriscoll — Thu, 27 Oct 2011 02:03:50 GMT

PowerGUI 3.1 doesn't work with 1.5 Beta 1 only 1.5 Beta 2.

I know it's not obvious :\. It would be nice to update them both at the same time. It's very complicated and I think that is where many peoples problems arise. In the most reset version I think I finally have it working so that it will display a message box with the support version rather than showing this totally uninformative error message.

New Post: Fails to load in Visual Studio 2010 Ultimate

sfeldman — Thu, 27 Oct 2011 00:14:43 GMT

adamdriscoll wrote:

I'd suggest installing the latest beta version and PowerGUI 3.1.

And PowerGUI 3.1 is PowerGUI VSX 1.5 Beta 1???

Sorry, but it is not obvious.

New Post: Fails to load in Visual Studio 2010 Ultimate

adamdriscoll — Wed, 26 Oct 2011 21:24:49 GMT

I'd suggest installing the latest beta version and PowerGUI 3.1.

New Post: Fails to load in Visual Studio 2010 Ultimate

sfeldman — Wed, 26 Oct 2011 15:01:09 GMT

I have tried VS 2010 Universal with SP1 and get the errors listed above. Have R# installed and other addins as well.

Tried to uninstall and reinstall - didn't help. Using the latest 1.4.1 version from Gallery.

Any thoughts?

Commented Issue: Don't Know How to Debug Scripts [31638]

AdamDriscoll — Mon, 24 Oct 2011 20:00:21 GMT

I can't figure out how to debug PowerShell scripts. I'm running as an administrator. I can set a breakpoint. When I run my script in the PowerGUI console, none of my breakpoints are hit. What do I need to do to enable debugging?
Comments: ** Comment from web user: AdamDriscoll **

Are you working inside of a PowerShell project? I'm noticing that PowerShell scripts that are part of other projects (C#\VB) no longer are debuggable. I'll look at fixing this shortly. If you are using the PowerShell project, you can just press F5.