Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/EliteLoser/DotNetVersionLister
Use Svendsen Tech's Get-STDotNetVersion function to get a list of installed .NET Framework versions on (remote) Windows computers. I also added a simple solution for .NET 5+
https://github.com/EliteLoser/DotNetVersionLister
dotnet dotnet-framework powershell script version
Last synced: about 2 months ago
JSON representation
Use Svendsen Tech's Get-STDotNetVersion function to get a list of installed .NET Framework versions on (remote) Windows computers. I also added a simple solution for .NET 5+
- Host: GitHub
- URL: https://github.com/EliteLoser/DotNetVersionLister
- Owner: EliteLoser
- License: mit
- Created: 2018-08-03T23:20:05.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2024-02-29T19:49:25.000Z (7 months ago)
- Last Synced: 2024-06-28T11:34:35.938Z (3 months ago)
- Topics: dotnet, dotnet-framework, powershell, script, version
- Language: PowerShell
- Homepage: https://www.powershelladmin.com/wiki/List_installed_.NET_versions_on_remote_computers
- Size: 103 KB
- Stars: 248
- Watchers: 13
- Forks: 50
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- jimsghstars - EliteLoser/DotNetVersionLister - Use Svendsen Tech's Get-STDotNetVersion function to get a list of installed .NET Framework versions on (remote) Windows computers. I also added a simple solution for .NET 5+ (PowerShell)
README
# DotNetVersionLister
Get a list of installed .NET Framework versions on (remote) Windows computers.
As of 2022-10-10 versions up to .NET 4.8.1 are supported/detected. It's based on the information in this article: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed
Blog documentation, parts outdated (duplicating (or fixing) it (t)here is tedious): https://www.powershelladmin.com/wiki/List_installed_.NET_versions_on_remote_computers
It's published to the PowerShell Gallery, so you can install/inspect/download with `Install-Module`, `Find-Module` and `Save-Module`. Link: https://www.powershellgallery.com/packages/DotNetVersionLister/
# New feature in October 2022
Obs. As of 2023-05-25, I have published the 3.1.4 module to the PowerShell Gallery. The latest version here on GitHub is now the same as the latest version in the PSGallery ( https://www.powershellgallery.com/packages/DotNetVersionLister/3.1.4 ).
Thought maybe I would wait to see if there is any feedback (doubtful).
In version 3.1.0 and up of the module, the build number is presented with a "+" trailing the version if it is not an exact match for a specific .NET Framework version. This increases the precision of the script as it formerly did not distinguish a higher build than the exact .NET Framework version.
# .NET 5 and up
See https://github.com/EliteLoser/DotNetVersionLister/tree/master/5AndUp for .NET 5 and up (SDK and Runtime).
# Installation and use
Example installation for your user only:
```
Install-Module -Name DotNetVersionLister -Scope CurrentUser #-Force
```
Example use:
`Get-STDotNetVersion`
and
`Get-STDotNetVersion -ComputerName server1, server2, server3`
or
`Get-STDotNetVersion -ComputerName server1, server2, server3 -PSRemoting`
Example output:
```
Get-STDotNetVersion -NoSummary
ComputerName : localhost
>=4.x : 4.8.1
v4\Client : Installed
v4\Full : Installed
v3.5 : Not installed (no key)
v3.0 : Not installed (no key)
v2.0.50727 : Not installed (no key)
v1.1.4322 : Not installed (no key)
Ping : True
Error :
```
# Notes
The command/function name used to be `Get-DotNetVersion` in versions before v3 of the module. This is aliased if the command does not currently exist in the PowerShell session, but you have to either run `Get-STDotNetVersion` first to load it, as auto-load for `Get-DotNetVersion` does not work - or you can simply `Import-Module -Name DotNetVersionLister` first, as we had to on PowerShell v2.