BaseName for FileInfo objects

re: BaseName for FileInfo objects

jvierra — Sun, 25 Jun 2006 00:30:07 GMT

I agree. If we can add it as a type that should be good for now. Perhaps the typing that may be included in future releases shouyld be mediated by the PS Team. A standard for adding types and documenting them so that when they are included in the release nothing will break.

I would much rather see an AD provider take shape. While we can use AD through NET Framework or COM it would be far better to have a full PS provider for ADSI.

How has Exchange managed to survive without an ADSI provider? Are they building all of it into the Exchange provider?

re: BaseName for FileInfo objects

Alex K. Angelopoulos — Sun, 25 Jun 2006 03:01:32 GMT

After some volleying with Jacques Barathon, there's a slightly improved version of the code block which correctly handles files which have no extension or names that begin with a period:
####

if ( ($this.extension.length -gt 0)
-and ($this.extension.length -lt this.Name.length) )
{
$this.Name.Remove($this.Name.Length - $this.Extension.Length)
}
else
{
$this.Name
}

re: BaseName for FileInfo objects

KeithH — Sun, 25 Jun 2006 05:44:56 GMT

Regarding a naming convention, you probably already know that I'm not a fan of "My." anything. Besides the customized types.ps1xml I use is located in the PSConfiguration folder. I think this is where all customization files should go. I don't think it is a good idea to have folks place customized files in PowerShell's install dir. On Vista, depending on how you try to write to the Program Files dir the modification may or may not get virtualized.

re: BaseName for FileInfo objects

Singee15 — Mon, 26 Jun 2006 17:19:03 GMT

I think that 'User' would be an appropriate prefix for all user-defined extensions.

This avoids the overused and inappropreate use of 'My' and replaces it with an accurate and descriptive prefix.

Using FFMPEG to squish lots of videos using PowerShell

ComputerZen.com - Scott Hanselman — Sun, 02 Jul 2006 12:26:46 GMT

re: BaseName for FileInfo objects

lb — Fri, 14 Jul 2006 06:34:37 GMT

this is nifty! love the user-extensibility of powerShell. Heck i love everything about it.

got any advice/ideas about handling for: "cascading file types".

say, your example file "MSH.xshd.orig" above --well under a 'cascading file types' scenario, this could be opened/viewed/(etc) by either:
1. the apps that handle the 'xshd' extension
or:
2. the apps that handle the 'orig' extension {pretending this is a genuine file type}

what sort of support could ps offer for this cascading file types model?

currently i'm thinking of just doing up a windows context menu enhancement for it... but now i see that powerShell could offer support too.

more about it here:
http://secretgeek.net/multiformats.asp

lb

re: BaseName for FileInfo objects

PowerShellTeam — Fri, 14 Jul 2006 07:21:56 GMT

RE: Cascading file types

What you could do in this case is to have a ScriptMethod that you call to examine the object and dynamically add properties to itself.
Add the following ScriptMethod to the FileInfo Type extension and you'll be able to do the example below. You just add your own logic:

<ScriptMethod> <Name>AddCascadingFileTypes</Name>
<Script>
$basename,$extensions = $this.Name.Split(".")
foreach ($e in $extensions)
{
$this |Add-Member -type NoteProperty -Name ("ADDEDPROPERTY"+$e) -value $e
}
</Script>
</ScriptMethod>

PS> dir a.b*

Directory: Microsoft.PowerShell.Core\FileSystem::C:\Temp

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 7/13/2006 9:17 PM 17432 a.b.c.d.e.f.g

PS> $x=(dir a.b*)
PS> $x.AddCascadingFileTypes()
PS> $x |fl a*

ADDEDPROPERTYb : b
ADDEDPROPERTYc : c
ADDEDPROPERTYd : d
ADDEDPROPERTYe : e
ADDEDPROPERTYf : f
ADDEDPROPERTYg : g
Attributes : Archive

Jeffrey Snover [MSFT]
Windows PowerShell/Aspen Architect
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

Suggestion: Add a Basename property to System.IO.FileInfo | keyongtech

Suggestion: Add a Basename property to System.IO.FileInfo | keyongtech — Thu, 22 Jan 2009 05:49:22 GMT

PingBack from http://www.keyongtech.com/2831366-suggestion-add-a-basename-property