{"id":15681,"date":"2011-02-05T16:01:00","date_gmt":"2011-02-05T16:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2011\/02\/05\/create-a-custom-file-extension-by-using-powershell\/"},"modified":"2011-02-05T16:01:00","modified_gmt":"2011-02-05T16:01:00","slug":"create-a-custom-file-extension-by-using-powershell","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/create-a-custom-file-extension-by-using-powershell\/","title":{"rendered":"Create a Custom File Extension by Using PowerShell"},"content":{"rendered":"

Summary<\/b>: Learn how to use Windows PowerShell to create a custom file extension to store code snippets. <\/p>\n

Weekend Scripter: Creating a .snip file type<\/h3>\n

Microsoft Scripting Guy, Ed Wilson, here. After I created the Get-CodeSnippet<\/b> function yesterday<\/a>, I decided that it might be useful to have my own file extension to keep track of code snippets. <\/p>\n

The reason is that to make using code snippets truly useful, the code needs to be designed specifically to be added to my script. It can take the form of reusable functions, or it can even take the form of script block skeletons. Rather than weeding through a bunch of .ps1 or .psm1 files, I thought I would make my own extension. <\/p>\n

The New-SnipType.ps1 script adds a couple of registry keys as shown here. <\/p>\n

New-SnipType.ps1<\/strong><\/p>\n

\n

New-PSDrive -Name HKCR -PSProvider registry -Root HKEY_CLASSES_ROOT | Out-Null<\/span><\/span><\/p>\n

Push-Location<\/span><\/span><\/p>\n

Set-Location -Path HKCR:<\/span><\/span><\/p>\n

New-Item -Name .snip -ItemType String -Value snip_file | Out-Null<\/span><\/span><\/p>\n

New-ItemProperty -Path HKCR:\\.snip -Name PerceivedType -Value Text `<\/span><\/span><\/p>\n

   <\/span><\/span>-PropertyType String | Out-Null<\/span><\/span><\/span><\/p>\n

New-Item -Name snip_file -ItemType string | Out-Null<\/span><\/span><\/p>\n

New-Item -Name shell -Path HKCR:\\snip_file -ItemType string | Out-Null<\/span><\/span><\/p>\n

New-Item -Name edit -Path HKCR:\\snip_file\\shell -ItemType string | Out-Null<\/span><\/span><\/p>\n

New-Item -Name command -Path HKCR:\\snip_file\\shell\\edit -ItemType ExpandString `<\/span><\/span><\/p>\n

   <\/span><\/span>-Value “%SystemRoot%\\system32\\NOTEPAD.EXE %1” | Out-Null<\/span><\/span><\/span><\/p>\n

New-Item -Name open -Path HKCR:\\snip_file\\shell -ItemType string | Out-Null<\/span><\/span><\/p>\n

New-Item -Name command -Path HKCR:\\snip_file\\shell\\open -ItemType ExpandString `<\/span><\/span><\/p>\n

   <\/span><\/span>-Value “%SystemRoot%\\system32\\NOTEPAD.EXE %1” | Out-Null<\/span><\/span><\/span> <\/span><\/span><\/p>\n

Set-Location -Path HKCU:<\/span><\/span><\/p>\n

$FEPath = “HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\FileExts”<\/span><\/span><\/p>\n

New-Item -Name .snip -Path $FEPath | Out-Null<\/span><\/span><\/p>\n

New-Item -Name OpenWithList -Path $FEPath\\.snip | Out-Null<\/span><\/span><\/p>\n

New-ItemProperty -Name a -Path $FEPath\\.snip\\OpenWithList `<\/span><\/span><\/p>\n

   <\/span><\/span>-value “Notepad.Exe” -PropertyType String | Out-Null<\/span><\/span><\/span><\/p>\n

New-ItemProperty -Name MRUList -Path $FEPath\\.snip\\OpenWithList `<\/span><\/span><\/p>\n

    <\/span><\/span>-value a -PropertyType String | Out-Null<\/span><\/span><\/span><\/p>\n

New-Item -Name OpenWithProgids -Path $FEPath\\.snip | Out-Null<\/span><\/span><\/p>\n

New-ItemProperty -Name snip_file -Path $FEPath\\.snip\\OpenWithProgids `<\/span><\/span><\/p>\n

    <\/span><\/span>-value “(zero-length binary value)” -PropertyType Unknown | Out-Null<\/span><\/span><\/span><\/p>\n

New-Item -Name UserChoice -Path $FEPath\\.snip | Out-Null<\/span><\/span><\/p>\n

New-ItemProperty -Name Progid -Path $FEPath\\.snip\\UserChoice `<\/span><\/span><\/p>\n

    <\/span><\/span>-value “Applications\\Notepad.Exe” -PropertyType String | Out-Null<\/span><\/span><\/span><\/p>\n

Pop-Location<\/span><\/span> <\/span><\/span><\/p>\n

Remove-PSDrive -Name HKCR<\/span><\/span><\/p>\n<\/blockquote>\n

The first thing I do in the New-SnipType.ps1 script is create a new Windows PowerShell drive, by using the New-PSDrive<\/b> cmdlet. I use the registry provider, and I specify the root as HKEY_CLASSES_ROOT. The reason for this is that, by default, the HKEY_CLASSES_ROOT registry hive is not exposed via a Windows PowerShell drive. Because the New-SnipType.ps1 script is working with the HKEY_CLASSES_ROOT hive, the script must be run with elevated rights. You might wish to add the Test-IsAdministrator<\/a> function to ensure that the script has the appropriate rights. <\/p>\n

Next, I store the current drive location by using the Push-Location<\/b> cmdlet, and I then change my working location to the HKCR:<\/b> drive. Now I create several new registry keys and registry key properties. When I am finished on the HKCR:<\/b> drive, I change to the HKCU (HKEY_CURRENT_USER) drive and create some more values. When I am finished on that drive, I change drives back to the original drive by using the Pop-Location<\/b> cmdlet. I then use the Remove-PSDrive<\/b> cmdlet to remove the newly created HKCR:<\/b> drive. <\/p>\n

The type for a new registry key must be an instance of the Microsoft.Win32.RegistryValueKind .NET Framework enumeration class. Using my Get-EnumValues<\/b> function that I have in my Windows PowerShell ISE startup profile, I obtain the following information about the RegistryValueKind<\/b> as shown here.<\/p>\n

\n

PS C:\\Users\\ed.NWTRADERS> get-enumValues Microsoft.Win32.RegistryValueKind<\/span><\/span><\/p>\n

 <\/span><\/span><\/p>\n

Name                           <\/span>Value<\/span>                                                                                                                        <\/span><\/span><\/span><\/span><\/p>\n

—-      <\/span>                       <\/span>—–<\/span>                                                                                                                        <\/span><\/span><\/span><\/span><\/p>\n

MultiString                     <\/span>7                                                                             <\/span><\/span>                                               <\/span><\/span><\/span><\/span><\/p>\n

QWord                          <\/span>11<\/span>                                                                                                                           <\/span><\/span><\/span><\/span><\/p>\n

DWord                          <\/span>4                   <\/span><\/span>                                                                                                         <\/span><\/span><\/span><\/span><\/p>\n

Binary                           <\/span>3                                                                                                                      <\/span><\/span>      <\/span><\/span><\/span><\/span><\/p>\n

ExpandString                  2<\/span>                                                                                                                            <\/span><\/span><\/span><\/span><\/p>\n

String                           <\/span>1<\/span>                                                                                                                            <\/span><\/span><\/span><\/span><\/p>\n

Unknown                       <\/span>0<\/span><\/span><\/p>\n<\/blockquote>\n

<\/blockquote>\n

It is perhaps a bit unfortunate that the EnumValues <\/b>do not match the data types (such as REG_SZ) that are displayed in the Registry Editor, but things such as REG_DWORD and REG_BINARY are close enough to DWord and Binary that one can figure them out. String values like MultiString (REG_MULTI_SZ) and ExpandString (REG_EXPAND_SZ) cause admins confusion.<\/p>\n

Because this is a special purpose, one-time use type of script, I did not add any error checking, or command line Help. After the script runs, the .snip file type will be recognized, and will open in Notepad when double-clicked. An If_Else.snip<\/b> appears as shown in the following image.<\/p>\n

\"WES-2-6-11-01\"<\/a><\/p>\n

If I add the .snip file extension to the Open file<\/b> dialog box filter that I created yesterday, I can easily pull up a list of all of my code snippets. <\/p>\n

One other thing—I consider it to be bad form to write code that makes a bunch of changes to the registry without also writing code to clean up after those changes. That is a great advantage about using a Windows PowerShell script to make the changes in the first place. Here is the Remove-SnipType.ps1 script.<\/p>\n

Remove-SnipType.ps1<\/strong><\/p>\n

\n

New-PSDrive -Name HKCR -PSProvider registry -Root HKEY_CLASSES_ROOT | Out-Null<\/span><\/span><\/p>\n

Push-Location<\/span><\/span><\/p>\n

Set-Location -Path HKCR:<\/span><\/span><\/p>\n

Remove-Item -Path HKCR:\\.snip -Recurse<\/span><\/span><\/p>\n

Remove-Item -Path HKCR:\\snip_file -Recurse<\/span><\/span> <\/span><\/span><\/p>\n

Set-Location -Path HKCU:<\/span><\/span><\/p>\n

Remove-Item -Path HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\FileExts\\.snip -Recurse <\/span><\/span> <\/span><\/span><\/p>\n

Pop-Location<\/span><\/span> <\/span><\/span><\/p>\n

Remove-PSDrive -Name HKCR<\/span><\/span><\/p>\n

<\/span><\/span><\/p>\n<\/blockquote>\n

Well, that is all there is to creating a custom file extension in the registry. <\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

 <\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Learn how to use Windows PowerShell to create a custom file extension to store code snippets. Weekend Scripter: Creating a .snip file type Microsoft Scripting Guy, Ed Wilson, here. After I created the Get-CodeSnippet function yesterday, I decided that it might be useful to have my own file extension to keep track of code […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[38,31,26,3,4,12,14,61,45],"class_list":["post-15681","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-files","tag-operating-system","tag-registry","tag-scripting-guy","tag-scripting-techniques","tag-storage","tag-text-files","tag-weekend-scripter","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Learn how to use Windows PowerShell to create a custom file extension to store code snippets. Weekend Scripter: Creating a .snip file type Microsoft Scripting Guy, Ed Wilson, here. After I created the Get-CodeSnippet function yesterday, I decided that it might be useful to have my own file extension to keep track of code […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/15681","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=15681"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/15681\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=15681"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=15681"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=15681"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}