and greater, but then it will just say '4.8 or later'. I have since creating the initial documentation also added support for: You can also import it in Excel, which there's a screenshot of below. The CSV can easily be parsed using PowerShell's usual mechanisms, some of which I demonstrate here. I'm not rewriting all of the documentation, so some of it could be partially outdated if you use the latest v2.x module - but I do recommend that. It emits/outputs objects instead of simply writing a CSV file by default, plus I added support for using PSRemoting instead of remote registry access, with the -PSRemoting parameter. It's a lot more standards-conforming as PowerShell goes. To be friendly to people used to the old script, I added the parameter -ExportToCSV to the 'DotNetVersionLister' module I've since then uploaded. Here is a PowerShell script that takes a list of computers (or you can use -LocalHost for the current computer), collects data via remote registry access - or PSRemoting as of v2.0 - and the original script creates a CSV file with the data. NET are installed on remote computers or the computer you're on.
List_installed_.NET_versions_on_remote_computersYou could find yourself wanting to know which versions of.
