Comments on: PowerShell Tutorials 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: Michel http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-1220 Michel Thu, 02 Feb 2012 13:17:01 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-1220 STEVE, CHECK THE RIGHT HAND SIDE NAVIGATION COLUMN WHERE YOU FIND: POWERSHELL TUTORALS (this page!!!!!) POWERSHELL CONSOLE (Tutorial 1 ????) POWERSHELL CMDLETS (Tutorial 2 ????) ... PICK ONE! PS I HAVE 40 YEARS EXPERIENCE IN IT, KEEP ON TRUCKING! STEVE,
CHECK THE RIGHT HAND SIDE NAVIGATION COLUMN WHERE YOU FIND:
POWERSHELL TUTORALS (this page!!!!!)
POWERSHELL CONSOLE (Tutorial 1 ????)
POWERSHELL CMDLETS (Tutorial 2 ????)
…
PICK ONE!
PS I HAVE 40 YEARS EXPERIENCE IN IT, KEEP ON TRUCKING!

]]> By: Steve http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-1129 Steve Sat, 21 Jan 2012 09:02:46 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-1129 I have worked 20 years in IT but I cannot find those tutorials. Man you need to something about that. Maybe your tutorials were exactly what I was looking for but I will leave your website now and google something else and never come back here. Utterly bad website design. Boo. I have worked 20 years in IT but I cannot find those tutorials. Man you need to something about that. Maybe your tutorials were exactly what I was looking for but I will leave your website now and google something else and never come back here. Utterly bad website design. Boo.

]]> By: Buzz http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-1003 Buzz Fri, 06 Jan 2012 19:59:36 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-1003 Got to Tutorial 1 but cannot find the rest of them. Got to Tutorial 1 but cannot find the rest of them.

]]> By: Dev http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-898 Dev Fri, 23 Dec 2011 03:34:18 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-898 How can someone miss the powershell tutorials. It is written in bold on the side of the screen. Don't tell me you can't find it. When you came to learn powershell programming I assume you do have intention to find something on your own, not to expect spoon feeding. That's all my 2Cents. How can someone miss the powershell tutorials. It is written in bold on the side of the screen. Don’t tell me you can’t find it. When you came to learn powershell programming I assume you do have intention to find something on your own, not to expect spoon feeding. That’s all my 2Cents.

]]> By: confused http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-757 confused Sun, 04 Dec 2011 07:29:56 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-757 confusing website. not very intuitive. took me a while to figure out where the tutorials are. had to read through the comments to figure it out. bad website design/layout. confusing website. not very intuitive.
took me a while to figure out where the tutorials are. had to read through the comments to figure it out.

bad website design/layout.

]]> By: Richard http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-745 Richard Wed, 30 Nov 2011 03:28:07 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-745 Thank you Larold, after banging on the Tutorial Link several times I thought something was wrong so jumped to bottom of comments and saw your comment. I thought the other links were in addition to the tutorial. Just a beginner. Thank you again, Thank you Larold, after banging on the Tutorial Link several times I thought something was wrong so jumped to bottom of comments and saw your comment. I thought the other links were in addition to the tutorial. Just a beginner. Thank you again,

]]> By: DeV http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-716 DeV Thu, 03 Nov 2011 08:51:16 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-716 You have to surf through the tutorials by clicking the links on the right hand side You have to surf through the tutorials by clicking the links on the right hand side

]]> By: DeV http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-715 DeV Thu, 03 Nov 2011 08:50:50 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-715 <b>You have to surf through the tutorials by clicking the links on the right hand side</b> You have to surf through the tutorials by clicking the links on the right hand side

]]> By: Larold http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-677 Larold Wed, 24 Aug 2011 19:12:59 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-677 The title of the first link under the section "Powershell Tutorials" should NOT be called 'Powershell Tutorials'. This is confusing to many. Instead, consider naming the link something like 'Introduction', or, 'About these Tutorials'. Also consider an auto-generated numbering system, with the first link starting at '1', the next starting at '2', etc. This way people will see right away the progression of links and not get confused. Dave W is spot on with his observations above. The current design and layout is potentially confusing to many. If I click a link that says 'Powershell Tutorials', I expect to be immediately taken to a list of every tutorial in the guide. Instead, I'm taken to a page with no tutorial content, and just an introduction. Most importantly, I'm left wondering, "So... I'm guessing all of the other links below the first one, 'Powershell Tutorials', are NOT tutorials, and either more advanced guides, or links to other sites." Change the text of that first link from 'Powershell Tutorials' to "Introduction" and I think you're golden. I highly suggest to SPNick that he learn to think about and view a situation as someone else might. You'll catch many more flaws in a system that way. Other than the subtle design flaw, great site! The title of the first link under the section “Powershell Tutorials” should NOT be called ‘Powershell Tutorials’. This is confusing to many. Instead, consider naming the link something like ‘Introduction’, or, ‘About these Tutorials’. Also consider an auto-generated numbering system, with the first link starting at ‘1′, the next starting at ‘2′, etc. This way people will see right away the progression of links and not get confused.

Dave W is spot on with his observations above. The current design and layout is potentially confusing to many. If I click a link that says ‘Powershell Tutorials’, I expect to be immediately taken to a list of every tutorial in the guide. Instead, I’m taken to a page with no tutorial content, and just an introduction. Most importantly, I’m left wondering, “So… I’m guessing all of the other links below the first one, ‘Powershell Tutorials’, are NOT tutorials, and either more advanced guides, or links to other sites.”

Change the text of that first link from ‘Powershell Tutorials’ to “Introduction” and I think you’re golden.

I highly suggest to SPNick that he learn to think about and view a situation as someone else might. You’ll catch many more flaws in a system that way.

Other than the subtle design flaw, great site!

]]> By: YKLA http://www.powershellpro.com/powershell-tutorial-introduction/comment-page-1/#comment-671 YKLA Thu, 18 Aug 2011 18:54:08 +0000 http://www.powershellpro.com/powershell-tutorial-introduction/#comment-671 Example above reads the content of filelist.dat which contains the path and filenames of all files where you need to make replacements, like this: d:\1\file1.dat d:\1\file2.dat d:\1\file3.dat Then it reads every file in the list and replaces "in" with "im". In my case I put the following inside each file?.dat file: Line 1 Line 2 Line 3 Line 4 And all these lines were replaced with Lime 1 Lime 2 Lime 3 Lime 4 in all the files. Example above reads the content of filelist.dat which contains the path and filenames of all files where you need to make replacements, like this:
d:\1\file1.dat
d:\1\file2.dat
d:\1\file3.dat
Then it reads every file in the list and replaces “in” with “im”. In my case I put the following inside each file?.dat file:
Line 1
Line 2
Line 3
Line 4
And all these lines were replaced with
Lime 1
Lime 2
Lime 3
Lime 4
in all the files.

]]>