{"id":74121,"date":"2015-08-07T00:01:00","date_gmt":"2015-08-07T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2015\/08\/07\/the-powershell-5-nonewline-parameter\/"},"modified":"2019-02-18T09:46:42","modified_gmt":"2019-02-18T16:46:42","slug":"the-powershell-5-nonewline-parameter","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/the-powershell-5-nonewline-parameter\/","title":{"rendered":"The PowerShell 5 NoNewLine Parameter"},"content":{"rendered":"

Summary<\/b>: Ed Wilson, Microsoft Scripting Guy, talks about the NoNewLine parameter in Windows PowerShell 5.0 in Windows 10.<\/span><\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. In addition to new cmdlets in Windows PowerShell 5.0, there are also improvements to existing cmdlets. These improvements are often really cool because it means I can use the old cmdlets in new ways, which is just about like having a new cmdlet.<\/p>\n

These add-ons (if you will) are not as easy to find as a whole brand new cmdlet. I mean, a brand new cmdlet is pretty easy to find with Get-Command<\/b> because all I need to do is type Get-Command<\/b>, and search for a verb or a noun, or page through all of the cmdlets and look for things that are not familiar. Or, if I want to be more scientific, I can use Get-Command<\/b> in Windows 8.1, then in Windows 10, and use Compare-Object<\/b> to compare the two lists of cmdlet names.<\/p>\n

Finding new parameters<\/h2>\n

But finding new parameters is more difficult. It is not impossible, but it is more difficult. In the beta of Windows PowerShell 2.0, for example, one of the Windows PowerShell MVPs wrote a really cool script that would compare drops for new cmdlets and for new parameters. It was a very useful script for keeping up with all the changes that were appearing like rabbits in an unmown field of clover.<\/p>\n

In the case of the NoNewLine<\/b> parameter, it is listed in the What's new in Windows PowerShell 5.0<\/a> article, and so that makes it easy to find. At other times, it means paying attention or actually searching by comparing commands from previous versions with commands from the latest version. That can be a rather slow and tedious process.<\/p>\n

The problem with new lines<\/h2>\n

The issue with new lines is not that we now have a solution in search of a problem. It was a problem, and it has been ever since Windows PowerShell 1.0. The reason is that there was inconsistent behavior. For example, if I create a new file and I have text in the file, I will not have a new line. If I add content to a file, I get new lines, and there was no good way to suppress this.<\/p>\n

So what is the big deal?<\/p>\n

Well, the big deal is that sometimes I want to control the new lines myself—maybe I am trying to build a CSV file or some other file, and I do not want invisible stuff entering my file (such as a carriage return or line feed).<\/p>\n

What are the commands that have the new NoNewLine<\/b> parameter? I can use the Get-Command<\/b> cmdlet (gcm<\/b> is an alias) and search for the parameter by using the –ParameterName<\/b> parameter. Of course, I am searching for the NoNewLine<\/b> parameter. The command and the associated output are shown in the following image:<\/p>\n

\"Image<\/a><\/p>\n

The four cmdlets with the new NoNewLine<\/b> parameter are:<\/p>\n