đ VSCELicense
Important notes
Details
PowerShell module to get and set the Visual Studio Community Edition license expiration date in the registry. Visual Studio 2013, 2015, 2017, and 2019 are supported.
Based on Dmitrii's answer to this Stack Overflow question: Visual Studio Community 2017 is a 30 day trial?
Usage
-
Download/clone this repository
-
Run
PowerShell.exe
orpwsh.exe
as the Administrator -
Import module:
Assuming that you cloned/downloaded this repo to
C:\VSCELicense
Import-Module -Name 'C:\VSCELicense\VSCELicense.psd1'
If you get
execution of scripts is disabled on this system
message, you can temporarily override PowerShell execution policy by runningSet-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
See PowerShell documentation for more details:
Examples
Get Visual Studio Community Edition license expiration date
All supported versions of Visual Studio.
Get-VSCELicenseExpirationDate
One specific version of Visual Studio.
Get-VSCELicenseExpirationDate -Version 2017
Multiple versions of Visual Studio.
Get-VSCELicenseExpirationDate -Version 2019, 2017
Set Visual Studio Community Edition license expiration date
Set a license expiration date to 31 days from now
All supported versions of Visual Studio.
Set-VSCELicenseExpirationDate
One specific version of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2017
Multiple versions of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2019, 2017
Set license expiration date to 10 days from now
All supported versions of Visual Studio.
Set-VSCELicenseExpirationDate -AddDays 10
One specific version of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2017 -AddDays 10
Multiple versions of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2019, 2017 -AddDays 10
Set a license expiration date to current date
All supported versions of Visual Studio.
Set-VSCELicenseExpirationDate -AddDays 0
One specific version of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2017 -AddDays 0
Multiple versions of Visual Studio.
Set-VSCELicenseExpirationDate -Version 2019, 2017 -AddDays 0
Changelog
- 0.0.9 - Added VS 2013 support (@andreburto)
- 0.0.8 - Make it easier to use by not requiring to specify the Visual Studio version
- 0.0.7 - Added VS 2015 support (@GDI123)
- 0.0.6 - Load
System.Security
assembly if the module was imported without manifest - 0.0.5 - Duh, actually set
PowerShellVersion = '3.0'
in manifest - 0.0.4 - Support downlevel PowerShell versions, starting from
3.0
- 0.0.3 - Fixed manifest to avoid execution errors under fresh PowerShell environments (@1Dimitri)
- 0.0.2 - Added VS 2019 support
- 0.0.1 - Initial commit, VS 2017 support