PoshConsole Release Rss Feed

Reviewed: Community Preview (Alpha) (Feb 05, 2009)

rhencke — Thu, 05 Feb 2009 15:30:01 GMT

Rated 1 Stars (out of 5) - Instantly dies on XP SP2 with: Method not found: 'Void System.Management.Automation.Runspaces.Runspace.set_ApartmentState(System.Threading.ApartmentState)'. at PoshConsole.CommandRunner.StartRunspace() at PoshConsole.CommandRunner.ThreadRun() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, Co

Reviewed: Community Preview (Alpha) (Jan 29, 2009)

chuckmoore55 — Thu, 29 Jan 2009 16:20:17 GMT

Rated 2 Stars (out of 5) - Installed under WinXP SP2. At invocation, immediately blows up (i.e. encounters a bug) with debug message : "An unhandled exception ("System.MissingMethodException") occurred in PoshConsole.exe [5816]".

Updated Release: Community Preview (Alpha) (Jan 18, 2009)

Jaykul — Mon, 19 Jan 2009 21:35:30 GMT

You MUST

Try running the "QuakeMode" cmdlet (full name is Get-QuakeMode, but nevermind that) in the console.
Try pressing the focus hotkey: WINC by default (but if you're a quake junky, you can set it to WINOEMTILDE)

Warning

Remember, this is a preview :) There's a known bug with resizing the window if you turn off the Vista aero look on the window (or are not running Vista with aero) -- I wrote some custom window drawing, and broke the resizing for the custom "Expression" looking mode. If you're on XP, you won't really be able to resize the window larger than it starts up, if you're on Vista, just leave the "Native Methods" on (that is, leave it so it looks aero, instead of switching to the gray look).

Released: Community Preview (Alpha) (Jan 18, 2009)

Mon, 19 Jan 2009 21:35:30 GMT

You MUST

Try running the "QuakeMode" cmdlet (full name is Get-QuakeMode, but nevermind that) in the console.
Try pressing the focus hotkey: WINC by default (but if you're a quake junky, you can set it to WINOEMTILDE)

Warning

Updated Release: Community Preview (Alpha) (Jan 18, 2009)

Jaykul — Mon, 19 Jan 2009 05:28:24 GMT

Warning

Released: Community Preview (Alpha) (Jan 18, 2009)

Mon, 19 Jan 2009 05:28:24 GMT

Warning

Updated Release: Community Preview (Alpha) (Jan 18, 2009)

Jaykul — Mon, 19 Jan 2009 05:27:45 GMT

There's a ton of new stuff in this release ... and I'll write it all up later. (sorry) I needed to get a new release out so people could play with Out-WPF and New-BootsThread (they're in the PoshWpf.dll, add it as a module). This release (probably) only works with the PowerShell 2 CTP ...

http://huddledmasses.org/images/PoshConsole/PoshConsole.png

http://huddledmasses.org/images/PowerBoots/PoshConsole-PowerBootsInline.png

!!Warning

Remember, this is a preview :) There's a known bug with resizing the window if you turn off the Vista aero look on the window (or are not running Vista with aero) -- I wrote some custom window drawing, and broke the resizing for the custom "Expression" looking mode. If you're on XP, you won't really be able to resize the window larger than it starts up, if you're on Vista, just leave the "Native Methods" on (that is, leave it so it looks aero, instead of switching to the gray look).

Updated Release: Community Preview (Alpha) (Jan 18, 2009)

Jaykul — Mon, 19 Jan 2009 05:19:36 GMT

Created Release: Community Preview (Alpha) (Jan 18, 2009)

Jaykul — Mon, 19 Jan 2009 05:06:18 GMT

Released: Community Preview (Alpha) (Jan 18, 2009)

Mon, 19 Jan 2009 05:06:18 GMT

UPDATED RELEASE: Community Preview (Alpha) 2007.9030

Fri, 31 Aug 2007 17:43:02 GMT

This is our next scheduled preview. It should include fixes for the most pressing bugs, as well as the first release of {{Out-WPF}} or {{Write-Posh}} (whatever we decide to call it).

CREATED RELEASE: Community Preview (Alpha) 2007.9170

Fri, 31 Aug 2007 17:03:28 GMT

This is a release candidate for Beta 1.

It should be feature complete for Beta 1, and we'll do any bug fixes between this and the beta. See proposed features below.

CREATED RELEASE: Community Preview (Alpha) 2007.8200

Fri, 17 Aug 2007 13:43:18 GMT

This is a placeholder for the next preview release so I can assign bugs to it.

UPDATED RELEASE: Community Preview (Alpha) 2007.8170 (Aug 17, 2007)

Fri, 17 Aug 2007 04:55:03 GMT

Well, there's lots and lots of changes in this release, and some of them are even noticeable to end users! I finally got some motivation to clean up and do some refactoring after looking at what Jachymko's been doing, so I've made a start at that -- the impact on the end user is mostly limited to some improvements in the threading behavior. So, welcome to [url:jachymko|http://www.codeplex.com/UserAccount/UserProfile.aspx?UserName=jachymko], who's working on a .Net 3.5 fork (which you can get from our [url:source repository|http://www.codeplex.com/PoshConsole/Release/ProjectReleases.aspx]) and feeding in lots of ideas and code -- he's even got a working WCF remoting implementation (but it's not ready for release).

I added a separate "Colors" settings class in {{$Host.PrivateData}} and moved the color settings in there, and also added color settings for the debug, error, verbose, and warning messages, as well as _separate_ color settings for 'native' output and input.

* Created a XAML version of the startup splash logo which is almost perfect, and will scale nicely.
* Fixed the scrollbar visibility (it's now bound to the settings so it's set correctly at startup now)
* Modified Logo XAML to use Bitstream Mono instead of Consolas (which I can't distribute)
* Fixed the tab-complete double-tap (there's a setting for the number of miliseconds)
* Embedded the [url:Bitstream Vera Sans Mono|http://www.gnome.org/fonts/] font so that the console always has a fallback monospace font.
* Removed the embedded fonts into a resource-only assembly (FontLibrary.dll).
* Moved the [StartupBanner] into a standalone XAML file which is easily user editable.
* Added Scroll Lock function -- when Scroll Lock is on, it turns off the use of up/down and pg up/pg down to navigate the history, and allows you to freely navigate and select text in the buffer with your keyboard.

! ANSI Escape Sequences
The weirdest thing in this release is some ANSI escape sequence support: you can now put ANSI escape sequences into your strings and get formatted output! Just start with {{[char]27[}} or {{[char]0x1B[}} and continue with semi-colon delimited [url:standard ANSI codes for colors|http://www.termsys.demon.co.uk/vtansi.htm#colors]:
* 30-37 for foreground
* 40-47 for background
* a 1 will set it to the _bright_ version of colors that follow
* a 2 chooses the _dark_ version of colors that follow
* a 4 is underline
* a 5 is italic -- not blink, sorry ;-)
* a 7 is bold -- not reverse, you can do that yourself
* an 8 is .. uhm .. "thin" (which probably won't be noticeable in most fonts)

You can terminate the ANSI sequence with an _m_ like you're supposed to, or you can terminate with a closing square brace. As a bonus, if you enclose it with square braces you can use words like italic and bold and underline, and the names from the ConsoleColors enumeration (which are the plain color names in $Host.PrivateData.Colors): the first name sets the foreground, the second sets the background. You can even use custom colors by specifying a HEX color like HTML colors (with an optional alpha blending.

There is a problem, however: PowerShell miscalculates the text length because it doesn't know the escaped formatting codes will be removed. Using color names or hex string makes that worse because they are that much longer. Anyway, this is mostly just "for fun" ... we'll produce a Write-Posh cmdlet soon which will support all our formatting options.

RELEASED: Community Preview (Alpha) 2007.8170 (Aug 17, 2007)

Fri, 17 Aug 2007 04:55:03 GMT

UPDATED RELEASE: Community Preview (Alpha) 2007.8170

Fri, 17 Aug 2007 04:54:24 GMT

UPDATED RELEASE: Community Preview (Alpha) 2007.8170

Fri, 17 Aug 2007 04:53:37 GMT

UPDATED RELEASE: Community Preview (Alpha) 2007.8170

Fri, 17 Aug 2007 04:49:34 GMT

UPDATED RELEASE: Community Preview (Alpha) 2007.8150

Thu, 16 Aug 2007 15:15:26 GMT

Well, there's lots and lots of changes in this release, and some of them are even noticeable to end users! I finally got some motivation to clean up and do some refactoring after looking at what Jachymko's been doing, so I've made a start at that -- the impact on the end user is mostly limited to some improvements in the threading behavior. So, welcome to [url:jachymko|http://www.codeplex.com/UserAccount/UserProfile.aspx?UserName=jachymko], who's working on a .Net 3.5 fork (which you can get from our [url:source repository|http://www.codeplex.com/PoshConsole/Release/ProjectReleases.aspx]) and feeding in lots of ideas and code -- he's even got a working WCF remoting implementation (but it's not ready for release).

I added a separate "Colors" settings class in {{$Host.PrivateData}} and moved the color settings in there, and also added color settings for the debug, error, verbose, and warning messages, as well as _separate_ color settings for 'native' output and input.

* Created a XAML version of the startup splash logo which is almost perfect, and will scale nicely.
* Fixed the scrollbar visibility (it's now bound to the settings so it's set correctly at startup now)
* Modified Logo XAML to use Bitstream Mono instead of Consolas (which I can't distribute)
* Fixed the tab-complete double-tap (there's a setting for the number of miliseconds)
* Embedded the [url:Bitstream Vera Sans Mono|http://www.gnome.org/fonts/] font so that the console always has a fallback monospace font.
* Removed the embedded fonts into a resource-only assembly (FontLibrary.dll).
* Moved the [StartupBanner] into a standalone XAML file which is easily user editable.

! ANSI Escape Sequences
The weirdest thing in this release is some ANSI escape sequence support: you can now put ANSI escape sequences into your strings and get formatted output! Just start with {{[char]27[}} or {{[char]0x1B[}} and continue with semi-colon delimited [url:standard ANSI codes for colors|http://www.termsys.demon.co.uk/vtansi.htm#colors]:
* 30-37 for foreground
* 40-47 for background
* a 1 will set it to the _bright_ version of colors that follow
* a 2 chooses the _dark_ version of colors that follow
* a 4 is underline
* a 5 is italic -- not blink, sorry ;-)
* a 7 is bold -- not reverse, you can do that yourself
* an 8 is .. uhm .. "thin" (which probably won't be noticeable in most fonts)

You can terminate the ANSI sequence with an _m_ like you're supposed to, or you can terminate with a closing square brace. As a bonus, if you enclose it with square braces you can use words like italic and bold and underline, and the names from the ConsoleColors enumeration (which are the plain color names in $Host.PrivateData.Colors): the first name sets the foreground, the second sets the background. You can even use custom colors by specifying a HEX color like HTML colors (with an optional alpha blending.

There is a problem, however: PowerShell miscalculates the text length because it doesn't know the escaped formatting codes will be removed. Using color names or hex string makes that worse because they are that much longer. Anyway, this is mostly just "for fun" ... we'll produce a Write-Posh cmdlet soon which will support all our formatting options.

CREATED RELEASE: Community Preview (Alpha) 2007.8150

Wed, 15 Aug 2007 05:07:56 GMT

Well, there's lots and lots of changes in this release, and some of them are even noticeable to end users! I finally got some motivation to clean up and do some refactoring after looking at what Jachymko's been doing, so I've made a start at that -- the impact on the end user is mostly limited to some improvements in the threading behavior. So, welcome to [url:jachymko|http://www.codeplex.com/UserAccount/UserProfile.aspx?UserName=jachymko], who's working on a .Net 3.5 fork (which you can get from our [url:source repository|http://www.codeplex.com/PoshConsole/Release/ProjectReleases.aspx]) and feeding in lots of ideas and code -- he's even got a working WCF remoting implementation (but it's not ready for release).

I added a separate "Colors" settings class in {{$Host.PrivateData}} and moved the color settings in there, and also added color settings for the debug, error, verbose, and warning messages, as well as _separate_ color settings for 'native' output and input.

* Created a XAML version of the startup splash logo which is almost perfect, and will scale nicely.
* Fixed the scrollbar visibility (it's now bound to the settings so it's set correctly at startup now)
* Modified Logo XAML to use Bitstream Mono instead of Consolas (which I can't distribute)
* Fixed the tab-complete double-tap (there's a setting for the number of miliseconds)
* Embedded the [url:Bitstream Vera Sans Mono|http://www.gnome.org/fonts/] font so that the console always has a fallback monospace font.
* Removed the embedded fonts into a resource-only assembly (FontLibrary.dll).

! ANSI Escape Sequences
The weirdest thing in this release is some ANSI escape sequence support: you can now put ANSI escape sequences into your strings and get formatted output! Just start with {{[char]27[}} or {{[char]0x1B[}} and continue with semi-colon delimited [url:standard ANSI codes for colors|http://www.termsys.demon.co.uk/vtansi.htm#colors]:
* 30-37 for foreground
* 40-47 for background
* a 1 will set it to the _bright_ version of colors that follow
* a 2 chooses the _dark_ version of colors that follow
* a 4 is underline
* a 5 is italic -- not blink, sorry ;-)
* a 7 is bold -- not reverse, you can do that yourself
* an 8 is .. uhm .. "thin" (which probably won't be noticeable in most fonts)

You can terminate the ANSI sequence with an _m_ like you're supposed to, or you can terminate with a closing square brace. As a bonus, if you enclose it with square braces you can use words like italic and bold and underline, and the names from the ConsoleColors enumeration (which are the plain color names in $Host.PrivateData.Colors): the first name sets the foreground, the second sets the background. You can even use custom colors by specifying a HEX color like HTML colors (with an optional alpha blending.

There is a problem, however: PowerShell miscalculates the text length because it doesn't know the escaped formatting codes will be removed. Using color names or hex string makes that worse because they are that much longer. Anyway, this is mostly just "for fun" ... we'll produce a Write-Posh cmdlet soon which will support all our formatting options.