How to target multiple ASP.NET versions with AppCmd?
When administering an IIS web server you frequently have to use
AppCmd.exe to make configuration changes. Whether it is for a specific web site or server wide. Some think AppCmd is very limited: if you don’t know the options to use, you may think you can only address the x64 .NET Framework version, or only x86, or you can only target the current active .NET Framework version. Fortunately this is not true, you can address both x86 and x64 versions of .NET with AppCmd. Read how…
Most of us already know there are two versions of AppCmd available, one is located in
c:\windows\syswow64\inetsrv\appcmd.exe and the other in
c:\windows\system32\inetsrv\appcmd.exe These address either 64-bit and 32-bit.
But what for different Framework versions? There is a parameter available! Yes, you can target multiple ASP.NET versions with AppCmd!
AppCmd.exe recognizes the parameter
/clr. CLR stands for Common Language Runtime. By adding
/clr to your command, you can address different Framework versions. For example,
/clr:4 addresses the ASP.NET 4.0 and 4.5 configuration runtime, and
/clr:2 addresses ASP.NET 2.0 (3.5).
My name is Jan. I am not a hacker, coder, developer, programmer or guru. I am merely a system administrator, doing my daily thing at Vevida in the Netherlands. With over 15 years of experience, my specialties include Windows Server, IIS, Linux (CentOS, Debian), security, PHP, WordPress, websites & optimization. Want to support me and donate? Use this link: https://paypal.me/jreilink.
Install Windows Server Servicing Stack Updates (SSU) using PowerShell
Security baseline for Windows 10 v1903 and Windows Server v1903 – final release
Setting up Monit monitoring in Windows Subsystem for Linux WSL
How to verify SMBv1 is disabled in Windows and Windows Server
Silently import .reg file in your Windows registry
How to uninstall and remove Adobe Flash Player in Windows Server
How to set SVN_EDITOR environment variable in Windows Server
Manually fail-over all databases in an SQL Server Database Mirroring configuration