Donnerstag, 15. Januar 2009

PSCX Format-HEX not working

I hope PowerShell Community Extension adapt to PowerShell V2 CTP3 soon.


Currently I can't use Format-Hex and as Start-Process is part of CTP3 it should be removed.


I'm not testing in any systematic way, just stumbling into it, when I will try something.

If ISE could print, it could replace Notepad it behaves well with moderaztrate sized files. Only extending selections using the mouse is sometimes boaringly slow.

And when I have a number of files loaded, switching tabs fails. After closing one, I can continue my work.

No data lost till now.

Ein großes Dankeschön an das Powershell Team.

Bernd

Kommentare:

  1. Bernd, could you post a bug on Format-Hex on http://www.codeplex.com/powershellcx with steps to reproduct it? Format-Hex on CTP3 seems to be working fine for me. Thanks. Keith

    AntwortenLöschen
  2. Hello Keith,
    many thanks for your comment. It shows me, that there are people who read my blog.

    It seems rather a problem between ISE and PSCX. I'm still invastigating the problem.

    Trying to reduce my Profile. In the consol version I found no pronlem.

    In ISE I allways get:
    [5]C:\bin\Scripts (FileSystem)
    fromat-hex $profile
    The term 'fromat-hex' is not recognized as a cmdlet, function, operable program
    , or script file. Verify the term and try again.
    At line:1 char:11
    + fromat-hex <<<< $profile
    + CategoryInfo : ObjectNotFound: (fromat-hex:String) [], CommandN
    otFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Greetings

    Bernd

    Bernd

    AntwortenLöschen