Comments on: PowerShell Providers http://www.powershellpro.com Sharing the Experience Fri, 03 Feb 2012 08:09:32 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Basavaraj http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-1205 Basavaraj Wed, 01 Feb 2012 10:49:23 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-1205 One of the best read explaining concepts very nice. One of the best read explaining concepts very nice.

]]> By: Will B. http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-702 Will B. Fri, 07 Oct 2011 15:04:03 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-702 First of all: Congrats on this great tutorial! Now the issue: In Brazilian Portuguese language set, CSV uses semicolon as delimiter as long the comma is used as decimal separator. Is there a way to replicate this behavoir in PowerShell? TIA First of all: Congrats on this great tutorial!

Now the issue: In Brazilian Portuguese language set, CSV uses semicolon as delimiter as long the comma is used as decimal separator.

Is there a way to replicate this behavoir in PowerShell?

TIA

]]> By: Perry http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-624 Perry Wed, 18 May 2011 21:02:35 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-624 In your tutorial, you mention: Get-Content $PSHOME\about_Provider.help.txt On my system, I actually found it with this: Get-Content $PSHOME\about_Providers.help.txt In your tutorial, you mention: Get-Content $PSHOME\about_Provider.help.txt

On my system, I actually found it with this:
Get-Content $PSHOME\about_Providers.help.txt

]]> By: Brent http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-601 Brent Wed, 13 Apr 2011 19:04:32 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-601 This tutorial is exactly what I was looking for. Thanks so much for making it available. Just finished Tutorial 5, after doing 1-4 the past week, and am moving onward and upward. This tutorial is exactly what I was looking for. Thanks so much for making it available. Just finished Tutorial 5, after doing 1-4 the past week, and am moving onward and upward.

]]> By: Kenny http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-555 Kenny Thu, 23 Dec 2010 23:23:32 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-555 Great series! Only one critique so far (and It's a minor one!) :) The file in the first instruction is named differently on my PC. It is about_providers.help.txt instead of about_provider.help.txt. Is this a typo or does this file name differ from system to system? Great series! Only one critique so far (and It’s a minor one!) :)

The file in the first instruction is named differently on my PC. It is about_providers.help.txt instead of about_provider.help.txt.

Is this a typo or does this file name differ from system to system?

]]> By: Jeff Greenlee http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-507 Jeff Greenlee Wed, 04 Aug 2010 18:13:13 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-507 Hey.. great tutorial... one small thing I discovered regarding your Registry section. I think possibly the "hotfixes" structure for Windows 7 has changed. I was not able to locate it based on the given instructions (using "find" in regedit) any path using Hotfixes (although I did find a few Key values named "hotfix".) Minor detail: and truthfully it doesn't really matter.. (I just looked at other registry settings!) Hey.. great tutorial… one small thing I discovered regarding your Registry section. I think possibly the “hotfixes” structure for Windows 7 has changed. I was not able to locate it based on the given instructions (using “find” in regedit) any path using Hotfixes (although I did find a few Key values named “hotfix”.) Minor detail: and truthfully it doesn’t really matter.. (I just looked at other registry settings!)

]]> By: M Prindle http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-493 M Prindle Tue, 15 Jun 2010 15:58:58 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-493 This is a great tutorial series! To the others that are having issues when running under Windows7, for some of the exercises you may need to be running PS escalated as administrator. Win7 has extra security in place to stop the editing of the registry. This is a great tutorial series! To the others that are having issues when running under Windows7, for some of the exercises you may need to be running PS escalated as administrator. Win7 has extra security in place to stop the editing of the registry.

]]> By: Vishwas Setty http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-481 Vishwas Setty Mon, 24 May 2010 16:27:29 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-481 i AM GETTING THIS ERROR WHEN TRYING TO CREATE A NEW REGISTRY KEY...PLZ HELP ME.... Set-Location : A parameter cannot be found that matches parameter name 'NAME'. At line:1 char:19 + SET-LOCATION -NAME <<<< TEST-VALUE "TEST STRING" + CategoryInfo : InvalidArgument: (:) [Set-Location], ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand i AM GETTING THIS ERROR WHEN TRYING TO CREATE A NEW REGISTRY KEY…PLZ HELP ME….

Set-Location : A parameter cannot be found that matches parameter name ‘NAME’.
At line:1 char:19
+ SET-LOCATION -NAME <<<< TEST-VALUE “TEST STRING”
+ CategoryInfo : InvalidArgument: (:) [Set-Location], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

]]> By: Zijo http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-458 Zijo Tue, 23 Mar 2010 02:53:16 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-458 Just a brief correction of my item 3. I shoud have said: 3. When I copy about_Providers.help.txt from C:\Windows\SysWOW64\WindowsPowerShell\v1.0\en-US folder to C:\Windows\SysWOW64\WindowsPowerShell\v1.0 , it works OK (note: the file name in my case is about_Providers.help.txt instead of about_Provider.help.txt.) Zijo Just a brief correction of my item 3. I shoud have said:
3. When I copy about_Providers.help.txt from C:\Windows\SysWOW64\WindowsPowerShell\v1.0\en-US folder to C:\Windows\SysWOW64\WindowsPowerShell\v1.0
, it works OK (note: the file name in my case is about_Providers.help.txt instead of about_Provider.help.txt.)

Zijo

]]> By: Zijo http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/comment-page-1/#comment-457 Zijo Tue, 23 Mar 2010 02:50:21 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/powershell-providers/#comment-457 Additional information: 1. I am running Powershell 2.0 2. about_...help.txt files are in different location: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\en-US folder, instead C:\Windows\SysWOW64\WindowsPowerShell\v1.0 3. When I copy about_Providers.help.txt, it works OK (note: the file name in my case is about_Providers.help.txt instead of about_Provider.help.txt. I think that may be the reason(s) for my issue. I don't know if these difference will affect any commands (cmdlets) in the future tutorials? Thank you. Zijo Additional information:
1. I am running Powershell 2.0
2. about_…help.txt files are in different location: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\en-US folder, instead C:\Windows\SysWOW64\WindowsPowerShell\v1.0
3. When I copy about_Providers.help.txt, it works OK (note: the file name in my case is about_Providers.help.txt instead of about_Provider.help.txt.

I think that may be the reason(s) for my issue. I don’t know if these difference will affect any commands (cmdlets) in the future tutorials?

Thank you.

Zijo

]]>