{"id":17921,"date":"2010-06-28T00:01:00","date_gmt":"2010-06-28T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2010\/06\/28\/hey-scripting-guy-how-can-i-use-windows-powershell-to-create-a-text-file-with-fixed-length-lines\/"},"modified":"2010-06-28T00:01:00","modified_gmt":"2010-06-28T00:01:00","slug":"hey-scripting-guy-how-can-i-use-windows-powershell-to-create-a-text-file-with-fixed-length-lines","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/hey-scripting-guy-how-can-i-use-windows-powershell-to-create-a-text-file-with-fixed-length-lines\/","title":{"rendered":"Hey, Scripting Guy! How Can I Use Windows PowerShell to Create a Text File with Fixed-Length Lines?"},"content":{"rendered":"

 <\/p>\n

\"Bookmark<\/p>\n

 \n\"Hey,\nHey, Scripting Guy! I am trying to learn Windows PowerShell 2.0, but I am having some issues when it comes to string manipulation. I have been a faithful reader of the Scripting Guys for several years, and I have found many of the scripts to be critical in my business environment. I wish I could simply translate the VBScript scripts we use directly into Windows PowerShell and not have to fool with learning the “PowerShell way of doing things.” Why should I have to learn a whole new way of working with strings and files? I mean, if a Windows PowerShell script works, is that not the “PowerShell way?” It seems to me like you are letting a bunch of UNIX guys try to tell me how to administer my Windows servers.\n— RS\n \n\"Hey,\nHello RS,\nMicrosoft Scripting Guy Ed Wilson here. One of the great things about being a Microsoft Scripting Guy is the ability to talk and to interact with customers. I always learn from these interactions. Sometimes I learn that I have not been clear about a particular topic, or I learn that a feature I was not too impressed with has solved a particular need for someone. Many times I learn new techniques, tricks, or tips that make me a better scripter.\nI am the first to admit I do not know everything there is to know about VBScript, WMI, ADSI, the .NET Framework, or Windows PowerShell. The topics are too big, and I do not believe that anyone knows everything about scripting. The truly great thing about Windows PowerShell is that you do not need to know everything about Windows PowerShell to write a script that works. This is also both a cool thing and a frustrating thing.\nLet me explain a little bit. Many times I spend hours working on a script only to have someone pop up and say, “Why didn’t you do such and such?” Quite often, their suggestion takes my 30-line script and shortens it down to a single line of code. Does this mean my script is “wrong” and theirs is “right”? Not at all. If a script works, it works. If a script solves your problem, it has done its job.\nCan a script be made better? In nearly every case the answer is yes. What is the best script? Well, that depends on your criteria. Here are some common criteria for judging scripts:<\/p>\n